[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Documentation issues with xorriso
From: |
Thomas Schmitt |
Subject: |
Re: Documentation issues with xorriso |
Date: |
Mon, 13 Sep 2021 19:59:02 +0200 |
Hi,
it turned out that checking the ISO paths with the -not_paths strings
would cause an ambiguity with relative paths, because they get converted
to absulote paths when the command -not_paths is performed.
At that moment it is not defined whether the given path shall be used with
ISO names or with local disk names. So i do not know whether to prepend
the ISO working directory (-cd) or the hard disk working directory (-cdx).
Another reason is that excluding disk paths does not overlap with the
capability to exclude ISO names by -rm_r.
Finally: The man page currently says "disk path" and implementing
exclusions now is mainly motivated as bug fix so that the program matches
the promises in the man page.
Code and documentation changes:
"Bug fix: -not_leaf and -not_paths were not applied to -extract and alike"
https://dev.lovelyhq.com/libburnia/libisoburn/commit/b5a33c3
So man xorriso now says:
-not_mgt code[:code[...]]
Control the behavior of the exclusion lists.
Exclusion processing happens before disk_paths get mapped to the
ISO image, before disk files get compared with image files, and
before image files get extracted to disk files.
...
-not_paths disk_path [***]
Add the given paths to the list of excluded absolute disk paths.
...
Keep in mind that there may be alternative paths to the same
disk file. The exclusion tests are done literally, so that they
do not keep files from getting into the ISO filesystem by other
paths. Accordingly an exclusion does not prevent a disk file
from being overwritten by file extraction via an alternative not
excluded path. So the exlusions need to be coordinated with the
actual disk_path parameters given with commands.
...
osirrox ISO-to-disk restore commands:
...
Disk file exclusions by -not_mgt, -not_leaf, -not_paths apply. The
exclusion tests are made with the paths and names for the disk files.
If exclusion of paths or names in the ISO image is desired, then use
image manipulation commands like -rm or -find ... -exec rm before
extraction, and end the program by -rollback_end .
Excluded disk_path parameters of extraction commands cause SORRY
events. Implicitely given paths in trees under disk_path parameters
are excluded silently.
-----------------------------------------------------------------------
If you want to test:
I uploaded a new GNU xorriso-1.5.5 tarball
http://www.gnu.org/software/xorriso/xorriso-1.5.5.tar.gz
MD5 61e20ce5aff403b32fa7d0d22bb707a7
After building with
tar xzf xorriso-1.5.5.tar.gz
cd xorriso-1.5.5
./configure --prefix=/usr
make
the not yet installed binary is already usable like
$ xorriso/xorriso -version
GNU xorriso 1.5.5 : RockRidge filesystem manipulator, libburnia project.
...
Version timestamp : 2021.09.13.151337
...
$
It does not use the installed libburn.so, libisofs.so, libisoburn.so but
rather brought its own code copy of their current development state.
(Compare the size of xorriso/xorriso and /usr/bin/xorriso :))
You may replace you local /usr/bin/xorriso by it or you may run it
by its absolute path inside the xorriso-1.5.5 tree.
Have a nice day :)
Thomas