Bug#688527: manual xorriso.1: Please document how to set a name for the medium

2012-11-05 Thread Paul Menzel
Dear Thomas,


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

Some proposals.

1. Specify the volume ID, which can be considered to be the name of the
image.

2. Other burning applications use the volume ID to set the volume name.

  characters, but according to rarely obeyed specs stricter  rules
  apply:
  ECMA-119  demands  ASCII  characters  out  of  [A-Z0-9_].  Like:
  IMAGE_23
  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.


Thanks,

Paul


signature.asc
Description: This is a digitally signed message part


Bug#688527: manual xorriso.1: Please document how to set a name for the medium

2012-11-05 Thread Thomas Schmitt
Hi,

 1. Specify the volume ID, which can be considered to be the name of the
 image.

Ok.


 2. Other burning applications use the volume ID to set the volume name.

What would be the difference between volume id and volume name ?


   Like:
   IMAGE_23
   Joliet allows 16 UCS-2 characters. Like: Windows name
 Maybe indent both entries.

I can do this for the man page. Do you know how to get .texi into
making a moderate indentation ?


 I think, an article is missing. »as the name«

I have no own opinion on that. So: Ok.


   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.

It is an euphemism for clicki-colorful desktops on any base OS.
(I used playful rather than childish in order to stay polite.)


 Please note how ID is spelled differently in the document. Maybe it
 could be made consistent too.

Six years of evolution in small steps. :))
There are a few problems with generally using id or ID.
But it should be ok to at least consistently using ID with
the various ID strings in the Primary Volume Descriptor.

(Do not expect me to clarify the meaning of -volset_id.
 It is absolutely obscure what a volume set shall be at all.)


See
  http://libburnia-project.org/changeset/4856 
for the impact of your proposals.


Have a nice day :)

Thomas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#688527: manual xorriso.1: Please document how to set a name for the medium

2012-11-05 Thread Thomas Schmitt
Hi,

i made further changes in
  http://libburnia-project.org/changeset/4857
in order to get the search string volume name into the text.
(Further i forgot to update the change date of them nam page.)


Have a nice day :)

Thomas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#688527: manual xorriso.1: Please document how to set a name for the medium

2012-11-05 Thread Paul Menzel
Control: tags 688527 fixed-upstream


Dear Thomas,


Am Montag, den 05.11.2012, 10:43 +0100 schrieb Thomas Schmitt:

[…]

  2. Other burning applications use the volume ID to set the volume name.
 
 What would be the difference between volume id and volume name ?

just for people knowing this label as name and not ID.

Like:
IMAGE_23
Joliet allows 16 UCS-2 characters. Like: Windows name
  Maybe indent both entries.
 
 I can do this for the man page. Do you know how to get .texi into
 making a moderate indentation ?

Unfortunately I do not and I could not find it. I think itemization is a
good way to achieve that, though with the bullet.

[…]

 See
   http://libburnia-project.org/changeset/4856 
 for the impact of your proposals.

Thanks a lot for you quick acting!


Thanks,

Paul


signature.asc
Description: This is a digitally signed message part


Bug#688527: manual xorriso.1: Please document how to set a name for the medium

2012-09-23 Thread Paul Menzel
Package: xorriso
Version: 1.2.2-2
Severity: normal
Tags: upstream

Dear Debian folks,


reading the manual (more like skimming over and searching) 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«.

Maybe I just do not know the terms I need to search for. Then I am sorry
for bothering you.


Thanks,

Paul

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xorriso depends on:
ii  libacl1   2.2.51-8
ii  libburn4  1.2.2-2
ii  libc6 2.13-35
ii  libisoburn1   1.2.2-2
ii  libisofs6 1.2.2-1
ii  libjte1   1.19-1
ii  libreadline6  6.2-9
ii  zlib1g1:1.2.7.dfsg-13

xorriso recommends no packages.

Versions of packages xorriso suggests:
pn  cdck   none
pn  jigit  none

-- no debconf information


signature.asc
Description: This is a digitally signed message part


Bug#688527: manual xorriso.1: Please document how to set a name for the medium

2012-09-23 Thread Thomas Schmitt
Hi,

 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
 characters, but according to rarely obeyed specs stricter  rules
 apply:
 ECMA-119  demands  ASCII  characters  out  of  [A-Z0-9_].  Like:
 IMAGE_23
 Joliet allows 16 UCS-2 characters. Like: Windows name
 Be aware that the volume id might get used automatically as name
 of  the  mount  point when the medium is inserted into a playful
 computer system.
 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.

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.)


Have a nice day :)

Thomas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org