Hi,
The explanation for why
volname returned CDROM is that is apparently the default volume
label when none is specified (which wasn't in the first session). I
specified volly on a later session but volname and vol_id (which
someone else suggested) appear to not be multi-session aware and
xorriso does not rely on ECMA-168 but on ECMA-119
plus some SUSP based extensions like Rock Ridge.
Afaik the mkisofs runs of growisofs do not refer
to ECMA-168 either.
Yes, today I perused ECMA-168 and realized it specifies a form of
layout different than what my burnt discs conform to (i.e.
Hi,
growisofs's CD001
That's actually mkisofs's CD001.
growisofs -M examines media TOC resp. the
ECMA-119 PVD in order to get the parameters
for a run of mkisofs -C . growisofs then
starts mkisofs and writes its output to the
media. In case of overwriteable media it
finally copies the Volume
Hi,
libisofs does already provide all PVD components
which you requested. So it was easy to implement
a sketch of -pvd_info.
See some examples from my test runs.
Comments and change wishes are appreciated.
-
Drive current: -indev '/dev/sr1'
PVD
These look good.
Note the subtle differences between -toc line
Volume id: '...'
and -pvd_info line
Volume Id: ...
Would you prefer quoted output in -pvd_info ?
For the sake of programmatic use, the known delimiters of colon-space
and newline (or whatever) serves as implicit
Hi,
i uploaded
http://scdbackup.webframe.org/xorriso-0.4.3.tar.gz
which performs the new option -pvd_info.
xorriso -version should report Version timestamp
2009.10.05.190215 or newer.
Try
xorriso -indev ...device... -pvd_info 2/dev/null
-
Hi,
$ growisofs -Z /dev/dvdrw1 -R -J -V volly tmp/
but although it seems absurd I can't find any way to read this volume
label back once written.
$ volname /dev/dvdrw1
CDROM
CDROM is the default volume id of mkisofs.
-V volly should have overridden that.
volname works for me.
Own
Hello,
On Sunday October 04 2009, m wrote to cdwrite@other.debian.org:
m There's various places that discuss burning with growisofs and
m specifying a volume ID, like
m $ growisofs -Z /dev/dvdrw1 -R -J -V volly tmp/
m but although it seems absurd I can't find any way to read this
m
m mag...@gmail.com wrote:
There's various places that discuss burning with growisofs and
specifying a volume ID, like
$ growisofs -Z /dev/dvdrw1 -R -J -V volly tmp/
but although it seems absurd I can't find any way to read this volume
label back once written.
volname is discussed but is
CDROM is the default volume id of mkisofs.
-V volly should have overridden that.
volname works for me.
Own backup formatted by xorriso:
$ volname /dev/sr2
UPDATE_HOME_2008_12_09_115802
My apologies, my example indicated a first (-Z) session but should
have been of a subsequent (-M)
There's various places that discuss burning with growisofs and
specifying a volume ID, like
$ growisofs -Z /dev/dvdrw1 -R -J -V volly tmp/
but although it seems absurd I can't find any way to read this volume
label back once written.
volname is discussed but is worthless here:
$ volname
11 matches
Mail list logo
