[Pkg-libburnia-devel] Bug#688527: manual xorriso.1: Please document how to set a name for the medium
pm.debian at googlemail.com
Mon Nov 5 08:38:09 UTC 2012
I am sorry for the late reply.
Am Sonntag, den 23.09.2012, 18:02 +0200 schrieb Thomas Schmitt:
> > I could not
> > find a way to set the name for the medium. That name is later used by
> > programs like `udisks` to name the mount point.
> > The current default seems to ISOIMAGE.
> The property which has content "ISOIMAGE" by default is called
> Volume Id. To be set by xorriso command -volid.
> man xorriso has:
> -volid text
> Specify the volume ID. xorriso accepts any text up to 32
1. Specify the volume ID, which can be considered to be the name of the
2. Other burning applications use the volume ID to set the volume name.
> characters, but according to rarely obeyed specs stricter rules
> ECMA-119 demands ASCII characters out of [A-Z0-9_]. Like:
> Joliet allows 16 UCS-2 characters. Like: "Windows name"
Maybe indent both entries.
> Be aware that the volume id might get used automatically as name
I think, an article is missing. »as the name«
> of the mount point when the medium is inserted into a playful
> computer system.
If that is a metaphor(?) for Microsoft Windows, note that on GNU/Linux
udisks does the same.
> If an ISO image gets loaded while the volume ID is set to
> default "ISOIMAGE" or to "", then the volume ID of the loaded
> image will become the effective volume id for the next write
> run. But as soon as command -volid is performed afterwards, this
> pending id is overridden by the new setting.
> Consider this when setting -volid "ISOIMAGE" before executing
> -dev, -indev, or -rollback. If you insist in -volid "ISOIMAGE",
> set it again after those commands.
Please note how ID is spelled differently in the document. Maybe it
could be made consistent too.
> Within the mkisofs emulation it is option -V. (See man xorrisofs)
> The boot loader GRUB uses a different property, the Volume Creation
> Date And Time, which it interprets as UUID.
> (See xorriso command -volume_date.)
As always thank you very much for the detailed explanation.
If the manual should stay as is, this is fine too. From my side, the
report can be closed nevertheless.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: This is a digitally signed message part
More information about the Pkg-libburnia-devel