libburnia/libburn
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Introduced LIBDAX_MSGS_SEV_MISHAP

Browse Source
This commit is contained in:
Thomas Schmitt
2008-02-11 19:15:21 +00:00
parent 6e74c8bc2e
commit 4cb6706307
3 changed files with 23 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
libburn/libdax_msgs.h
View File

@ -144,10 +144,12 @@ struct libdax_msgs_item;
/** Non-fatal error messages indicating that parts of an action failed but
processing may go on if one accepts deviations from the desired result.
SORRY shall also be the severity for incidents which are severe enough
SORRY may also be the severity for incidents which are severe enough
for FAILURE but happen within already started irrevocable actions,
like ISO image generation. A precondition for such a severity ease is
that the action can be continued after the incident.
See below MISHAP for what xorriso would need instead of this kind of SORRY
an generates for itself in case of libisofs image generation.
E.g.: A pattern yields no result.
A speed setting cannot be made.
@ -161,6 +163,20 @@ struct libdax_msgs_item;
#define LIBDAX_MSGS_SEV_SORRY 0x60000000
/** A FAILURE (see below) which can be tolerated during long lasting
operations just because they cannot simply be stopped or revoked.
xorriso converts libisofs SORRY messages issued during image generation
into MISHAP messages in order to allow its evaluators to distinguish
image generation problems from minor image composition problems.
E.g.:
A libisofs input file is inaccessible during image generation.
After a MISHAP a function should behave like after SORRY.
*/
#define LIBDAX_MSGS_SEV_MISHAP 0x64000000
/** Non-fatal error indicating that an important part of an action failed and
that only a new setup of preconditions will give hope for sufficient
success.