Hello,
very clear, thanks a lot. I can understand the iso9660 burnning process more different with MS Windows.
and understand the Joliet was specified and endorsed by Microsoft, may not well supported on Linux.
But if not used Joliet on Xorriso, some special words are invisible.
e.g: I burn "test_????_1110.txt" and "test_????_????.txt" without Joliet on Xorriso demo, and can visible on Debian:
'test_????_1110.txt'
'test_????_????.txt'
but on MS Windows10 file manager, those files shows as below:
TEST____1110.txt
TEST______.txt
So, if possible, can find a way to support Linux and Windows burining files?
BR,
thanks a lot.
------------------ ???????? ------------------
??????: "Thomas Schmitt" <scdbackup@gmx.net>;
????????: 2020??11??20??(??????) ????4:59
??????: "bug-xorriso"<bug-xorriso@gnu.org>;
????: "????/wx????"<mfreesky@qq.com>;
????: Re: [report] [bug] libisofs cant omit ";1" with "omit_version_off" set, and windows marked ";1" as "_1" with file name.
Hi,
i see i have to give some background info:
A xorriso-made ISO with Joliet attributes three different names to each
file:
- ISO 9660 iaka ECMA-119 names consist of file parts with characters
{0-9,A-Z,_} and of separator chracters {.,;}:
NAME . SFX ; V
Where "NAME" is the file name, "SFX" is the suffix, "V" is the version
number.
In your example, xorriso wrote:
STEP1_1.TEXT;1
- Rock Ridge names consist of up to 255 bytes with no restriction on the
character set and no artificial version add-on. Rock Ridge is used to
record names from X/Open compliant filesystems.
In your example, xorriso wrote:
step1_1.text
- Joliet names partly follow the rules for ISO 9660 names, but use a
16-bit character set. It is not officially prescribed but seems to be
usual not to append ";1" to them.
In your example, xorriso wrote:
step1_1.text
Linux and other Unix-like operating systems prefer to show Rock Ridge names
because they are nearest to their X/Open compliant disk filesystems.
MS-Windows does not show and use Rock Ridge but rather Joliet.
xorriso normally suppresses the display of ';1" at the name end.
To get them shown use for ISO 9660 names:
xorriso -ecma119_map unmapped -read_fs ecma119 -indev /dev/sr0 -ls --
and for Joliet names:
xorriso -ecma119_map unmapped -read_fs norock -indev /dev/sr0 -ls --
> after step1, use "xorriso -dev /dev/sr0 lsl" can get file list :
> 'step1_1.txt'
This displays the Rock Ridge names.
(Rock Ridge is the reason for the "rr" in "xorriso".)
> view on Win10 file manager as below:
> step1_1.txt
Here you probably see the Joliet name of the file
> before step3, use "xorriso -dev /dev/sr0 lsl" can get all files changed to
'step1_1.txt;1'
The file names which you see are entirely made by the MS-Windows program.
Each burn session has to create a new directory tree, because the ISO 9660
filesystem is read-only and about half of the optical media types are
read-only too.
I assume that the ISO directory tree before step 3 has no Rock Ridge names.
So the shown names stem from Joliet.
If xorriso shows the name with ";1" despite no command
-ecma119_map unmapped
was given before the -lsl, then there must be another ";1" at the end of
the name. Like:
step1_1.txt;1;1
> after step3, use "xorriso -dev /dev/sr0 lsl" can get all files as below:
> 'Step2_1.txt;1'
> 'Step2_2.txt;1'
> 'step1_1.txt;1'
> 'step1_2.txt;1'
xorriso probably got these names from the Joliet tree produced in step 2.
'step3_1.txt'
'step3_2.txt'
These are the names which it got from the local disk filesystem.
What do you get from
xorriso -ecma119_map unmapped -read_fs ecma119 -indev /dev/sr0 -ls --
and
xorriso -ecma119_map unmapped -read_fs norock -indev /dev/sr0 -ls --
> i want to set " -compliance omit_version_off " to avoid the
> differnt pamamter set on Xorriso demo.
Well, xorriso adds ";1" to ISO 9660 names by default, but not to Joliet
names. So if you want ";1" on both, use
xorriso -compliance only_iso_version_off ...other.commands...
-------------------------------------------------------------------------
If this still stays riddling, please send me the ISO filesystem as image
file.
xorriso -indev /dev/sr0 -check_media data_to="$HOME"/image_file.iso --
gzip "$HOME"/image_file.iso
Send the resulting file
"$HOME"/image_file.iso.gz
to
scdbackup@gmx.net
(bug-xorriso will probably reject such a mail. It seems to have rejected
the mail, too, to which i answer here.)
Have a nice day :)
Thomas