[Debburn-changes] r640 - in cdrkit/trunk: . doc doc/READMEs
doc/genisoimage
Eduard Bloch
blade at alioth.debian.org
Wed Dec 27 18:05:29 CET 2006
Author: blade
Date: 2006-12-27 18:05:27 +0100 (Wed, 27 Dec 2006)
New Revision: 640
Modified:
cdrkit/trunk/Changelog
cdrkit/trunk/doc/DOC-OVERVIEW
cdrkit/trunk/doc/READMEs/README.multi
cdrkit/trunk/doc/genisoimage/README
cdrkit/trunk/doc/genisoimage/README.alphaboot
cdrkit/trunk/doc/genisoimage/README.eltorito
cdrkit/trunk/doc/genisoimage/README.graft_dirs
cdrkit/trunk/doc/genisoimage/README.hfs_boot
cdrkit/trunk/doc/genisoimage/README.hide
cdrkit/trunk/doc/genisoimage/README.hppaboot
cdrkit/trunk/doc/genisoimage/README.macosx
cdrkit/trunk/doc/genisoimage/README.mipsboot
cdrkit/trunk/doc/genisoimage/README.mipselboot
cdrkit/trunk/doc/genisoimage/README.mkhybrid
cdrkit/trunk/doc/genisoimage/README.session
cdrkit/trunk/doc/genisoimage/README.sort
cdrkit/trunk/doc/genisoimage/README.sparcboot
cdrkit/trunk/doc/genisoimage/README.sunx86boot
Log:
A lot of rebranding and readme updates of genisoimage docs
Modified: cdrkit/trunk/Changelog
===================================================================
--- cdrkit/trunk/Changelog 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/Changelog 2006-12-27 17:05:27 UTC (rev 640)
@@ -7,12 +7,14 @@
command (#369677)
* Added more DVD related fixes from SuSE's wodim-1.0pre5cvs-6.src.rpm
* --devices option for wodim (modeled after cdrskin's output)
+ * -msifile=... option to store -msinfo output reliably in a dedicated file
* clear profile names printing (using code from libburnia)
* cleanup with unused embedded CVS revision strings from Schilling and
more gcc -Wall correctness
* reenabled -format functionality (bug in program function control flow)
* get maximum DMA buffer size from sysfs on Linux, where possible
* enable BURN-Free by default where possible
+ * genisoimage documentation updates, mkisofs name changes
[ Thomas Schmidt ]
* workaround for older libmagic API
Modified: cdrkit/trunk/doc/DOC-OVERVIEW
===================================================================
--- cdrkit/trunk/doc/DOC-OVERVIEW 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/DOC-OVERVIEW 2006-12-27 17:05:27 UTC (rev 640)
@@ -21,9 +21,9 @@
wodim application (writting data) and details specific
to its usage
-mkisofs : documentation for work with the mkisofs, a
- ISO9660 filesystem creator. See mkisofs/README for
- details.
+genisoimage : documentation for work with genisoimage program, a
+ ISO9660 filesystem creator. See genisoimage/README for
+ details.
icedax : contains documentation for the CD audio
extraction utility icedax. See icedax/README for
Modified: cdrkit/trunk/doc/READMEs/README.multi
===================================================================
--- cdrkit/trunk/doc/READMEs/README.multi 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/READMEs/README.multi 2006-12-27 17:05:27 UTC (rev 640)
@@ -6,10 +6,9 @@
To test (with Linux):
-Create a iso-9660 filesystem image with mkisofs-1.10 or later.
-mkisofs is included in the wodim release (including
-SunOS/Solaris multi-session support)
-Use the -R flag to add Rock Ridge extensions (this is important).
+ - create a iso-9660 filesystem image with genisoimage.
+ - genisoimage is included in the cdrkit release.
+ - use the -R flag to add Rock Ridge extensions (this is important).
Assuming that the CD-R drive is connected to target 2 on the SCSI bus.
@@ -51,9 +50,6 @@
The first number is (1), the second number is (2).
-Create the image for the next session with mkisofs-1.12 or later.
-It is included in the wodim distribution.
-
2nd session:
You should create a directory that contains a second directory with data in it
for this purpose.
@@ -68,17 +64,17 @@
call:
On Linux:
-mkisofs -o isoimage_2.raw -R -C xx,yy -M /dev/cdwriter_blk_dev first_dir
+genisoimage -o isoimage_2.raw -R -C xx,yy -M /dev/cdwriter_blk_dev first_dir
On SunOS:
-mkisofs -o isoimage_2.raw -R -C xx,yy -M target,lun first_dir
+genisoimage -o isoimage_2.raw -R -C xx,yy -M target,lun first_dir
Note that the name "first_dir" is not important.
If you still keep the old raw image of the first session and there is only
one previous session on the CD you may also call:
-mkisofs -o isoimage_2.raw -R -C xx,yy -M isoimage.raw first_dir
+genisoimage -o isoimage_2.raw -R -C xx,yy -M isoimage.raw first_dir
The argument of -C is the output of wodim -msinfo
@@ -87,15 +83,17 @@
- On SunOS, target and lun refer to the SCSI target and lun of the
CD-R device with the same notation as for wodim dev=xxx,yyy .
+Note that you can also use the -msifile=... option of wodim to store this data
+in a reliable way. This is usefull for scripting.
-If you want to check, whether mkisofs make everything right, you should create
+If you want to check, whether genisoimage make everything right, you should create
another image by using the following command line.
On Linux:
-mkisofs -o isoimage_2.raw -R -C xx,0 -M /dev/cdwriter_blk_dev first_dir
+genisoimage -o isoimage_2.raw -R -C xx,0 -M /dev/cdwriter_blk_dev first_dir
On SunOS:
-mkisofs -o isoimage_2.raw -R -C xx,0 -M target,lun first_dir
+genisoimage -o isoimage_2.raw -R -C xx,0 -M target,lun first_dir
Where xx is the first number of the pair returned by wodim -msinfo
@@ -171,26 +169,27 @@
All notes above prevent you from doing reliable multi-session if the CD does
only contain Joliet but des not contain Rock Ridge attributes.
-In addition, please read README.joliet in the mkisofs directory.
+In addition, please read README.joliet in the genisoimage directory.
This is the answer to a commonly asked question is why can't I continue a
-multisession CD that has been started on a Microsoft system using mkisofs.
+multisession CD that has been started on a Microsoft system using genisoimage.
Note: It is not possible to create a multi-session HFS CD. If you create
a multi-session CD using any of the HFS options, then each new HFS
session will ignore HFS files from any previous sessions. A warning will
be printed if you attempt this. However, if you use the '-part' option to
-mkisofs for each session you create, then each session will appear as
+genisoimage for each session you create, then each session will appear as
separate volumes when mounted on a Mac. In this case, it is worth using the
'-V' or '-hfs-volid' option to give each session a unique volume name,
otherwise each "volume" will appear on the Desktop with the same name.
Joerg Schilling
-Edited for cdrkit by Christian Fromme <kaner at strace.org>
+Edited for cdrkit by Christian Fromme <kaner at strace.org> and Eduard Bloch
+
This describes the programs as shipped with cdrkit, a spinoff from the
cdrtools project. However, the cdrtools developers are no longer
involved in the development of this spinoff and therefore shall not
Modified: cdrkit/trunk/doc/genisoimage/README
===================================================================
--- cdrkit/trunk/doc/genisoimage/README 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/genisoimage/README 2006-12-27 17:05:27 UTC (rev 640)
@@ -1,8 +1,7 @@
-Cdrkit carries a version of mkisofs.
+Cdrkit carries a fork of the mkisofs program called genisoimage.
-The acompanying documentation of mkisofs consists of the
-manual page mkisofs.8 and README files found in the
-following locations (shell globing used):
+The acompanying documentation consists of the manual page genisoimage.8 and
+README files found in the following locations (shell globing used):
doc/:
@@ -12,9 +11,9 @@
README.cdplus: documentation and examples for creating
CD-plus (aka CD-extra) disks
-doc/mkisofs:
+doc/genisoimage:
-README: release notes for older mkisofs releases
+README.releasenotes: release notes for old mkisofs releases
README.*boot: documentation for various boot loader related
extensions for different architectures
@@ -23,12 +22,5 @@
README.*: additional docs for special features
-
Eduard Bloch -- Mon, 11 Sep 2006 23:05:29 +0200
-This describes the program as shipped with cdrkit, a spinoff from the
-cdrtools project. However, the cdrtools developers are no longer
-involved in the development of this spinoff and therefore shall not
-be made responsible for any problem caused by it. Do not try to get
-support for this program by contacting the original authors.
-
Modified: cdrkit/trunk/doc/genisoimage/README.alphaboot
===================================================================
--- cdrkit/trunk/doc/genisoimage/README.alphaboot 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/genisoimage/README.alphaboot 2006-12-27 17:05:27 UTC (rev 640)
@@ -19,10 +19,10 @@
point the system should be able to find the normal OS kernel and start
up fully.
-To use the Alpha boot support code in mkisofs, simply specify the
+To use the Alpha boot support code in genisoimage, simply specify the
location of the first stage boot loader (relative to the CD root)
using the -alpha-boot command line switch:
-mkisofs ... -alpha-boot boot/bootlx -o alpha.iso files
+genisoimage ... -alpha-boot boot/bootlx -o alpha.iso files
Modified: cdrkit/trunk/doc/genisoimage/README.eltorito
===================================================================
--- cdrkit/trunk/doc/genisoimage/README.eltorito 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/genisoimage/README.eltorito 2006-12-27 17:05:27 UTC (rev 640)
@@ -1,4 +1,3 @@
-/* @(#)README.eltorito 1.2 00/03/18 eric */
What is El Torito?
------------------
@@ -16,7 +15,7 @@
------------------------
For the x86 platform, many BIOS's have begun to support bootable CDs.
-The standard my patches for mkisofs is based on is called "El Torito".
+The standard my patches for genisoimage is based on is called "El Torito".
The "El Torito" standard works by making the CD drive appear, through BIOS
calls, to be a normal floppy drive. This way you simply put an floppy
@@ -49,7 +48,7 @@
The "El Torito" specification requires a "boot catalog" to be created as
ll.
This is a 2048 byte file which is of no interest except it is required.
-My patches to mkisofs will cause it to automatically create the
+My patches to genisoimage will cause it to automatically create the
boot catalog. You must specify where the boot catalog will go in the
iso9660 filesystem. Usually it is a good idea to put it the same place
as the boot image, and a name like "boot.catalog" seems appropriate.
@@ -61,7 +60,7 @@
"boot.catalog". The command to create the iso9660 fs in the file
bootcd.iso is then
-mkisofs -b boot/boot.img -c boot/boot.catalog -o bootcd.iso .
+genisoimage -b boot/boot.img -c boot/boot.catalog -o bootcd.iso .
The -b option specifies the boot image to be used (note the path is
relative to the root of the iso9660 disc), and the -c option is
@@ -92,7 +91,11 @@
machines. The El Torito spec uses parts of the iso9660 filesystem which
were reserved for future use, so no existing code should care what it does.
-Mkisofs currently stores identification records in the iso9660 filesystem
+Genisoimage currently stores identification records in the iso9660 filesystem
saying that the system is a x86 system. The El Torito spec also allows
one to write PowerPC or Mac id's instead. If you look at the code in write.c
you could figure out how to change what is written.
+
+/* @(#)README.eltorito 1.2 00/03/18 eric */
+/* Edited for name change by Eduard Bloch, mkisofs -> genisoimage */
+
Modified: cdrkit/trunk/doc/genisoimage/README.graft_dirs
===================================================================
--- cdrkit/trunk/doc/genisoimage/README.graft_dirs 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/genisoimage/README.graft_dirs 2006-12-27 17:05:27 UTC (rev 640)
@@ -1,5 +1,3 @@
-# @(#)README.graft_dirs 1.1 00/01/12 joerg
-#
This is from "Eduardo M. A. M. Mendes" <mendes at mgconecta.com.br>
Creating multi-session CD's with dir=/ feature Micro Howto
@@ -37,12 +35,12 @@
First image - RedHat 6.1 - /mnt/redhat/root
-mkisofs -D -l -r -f -m core -L -o image1.raw redhat/=/mnt/redhat/root
+genisoimage -D -l -r -f -m core -L -o image1.raw redhat/=/mnt/redhat/root
This will create a redhat directory on the cd. The option -D should be
used with care. The other options used in the above command are just
-to demonstrate the use of mkisofs. Please
-refer to man mkisofs if you want to know more.
+to demonstrate the use of genisoimage. Please
+refer to man genisoimage if you want to know more.
To see if the image is created as expected, we need to mount image1.raw using
@@ -81,14 +79,14 @@
This number is the format XX,YY discussed on README.multi. XX would be used
for testing the images as well as burning the new track.
-mkisofs -D -l -r -f -m core -L -C 0,135563 -M /dev/scd0 -o image2.raw caldera/=/root
+genisoimage -D -l -r -f -m core -L -C 0,135563 -M /dev/scd0 -o image2.raw caldera/=/root
Now we need to check of image2.raw is ok. The following command creates exactly what we
need. Plese note that -C option. Only the first number changes in this case. The second one
is always zero. In our case the first number is zero due to wodim -msinfo. When
more tracks are added to the cd this number will change.
-mkisofs -D -l -r -f -m core -L -C 0,0 -M /dev/scd0 -o image2_test.raw caldera/=/root
+genisoimage -D -l -r -f -m core -L -C 0,0 -M /dev/scd0 -o image2_test.raw caldera/=/root
mount -t iso9660 image2_test.raw /mnt/image -o loop
@@ -110,7 +108,7 @@
Using the procedure described above we would do as follows:
-mkisofs -D -l -r -f -m core -L -o image1.raw etc/redhat/=/mnt/redhat/etc
+genisoimage -D -l -r -f -m core -L -o image1.raw etc/redhat/=/mnt/redhat/etc
wodim -v -dev=0,3,0 -multi -eject image1.raw
@@ -126,11 +124,11 @@
The second image can be created using
-mkisofs -l -r -f -m core -L -C 0,14391 -M /dev/scd0 -o image2.raw etc/caldera/=/etc
+genisoimage -l -r -f -m core -L -C 0,14391 -M /dev/scd0 -o image2.raw etc/caldera/=/etc
Creating a test image2
-mkisofs -l -r -f -m core -L -C 0,0 -M /dev/scd0 -o image2_test.raw etc/caldera/=/etc
+genisoimage -l -r -f -m core -L -C 0,0 -M /dev/scd0 -o image2_test.raw etc/caldera/=/etc
mount -t iso9660 image2_test.raw /mnt/image1 -o loop
@@ -149,5 +147,5 @@
Eduardo Mendes - 11/23/99
Source: README.graft_dirs from cdrtools package
-Edited for cdrkit by Christian Fromme <kaner at strace.org>
+Edited for cdrkit by Christian Fromme <kaner at strace.org> and Eduard Bloch
Modified: cdrkit/trunk/doc/genisoimage/README.hfs_boot
===================================================================
--- cdrkit/trunk/doc/genisoimage/README.hfs_boot 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/genisoimage/README.hfs_boot 2006-12-27 17:05:27 UTC (rev 640)
@@ -1,7 +1,7 @@
Making HFS bootable CDs
*******
-The HFS boot code in mkisofs/mkhybrid is now very out of date ...
+The HFS boot code in genisoimage/mkhybrid is now very out of date ...
it does not support booting from IDE CDROMS, and probably won't work on
"newer" Macs.
@@ -72,3 +72,5 @@
James Pearson (j.pearson at ge.ucl.ac.uk)
19-Jul-2000
+
+Edited for program name change by Eduard Bloch, 2006
Modified: cdrkit/trunk/doc/genisoimage/README.hide
===================================================================
--- cdrkit/trunk/doc/genisoimage/README.hide 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/genisoimage/README.hide 2006-12-27 17:05:27 UTC (rev 640)
@@ -27,7 +27,7 @@
etc.
If you don't want a file or directory to appear on the CD at all, then use the
--exclude options, not the -hide options (mkisofs completely ignores any
+-exclude options, not the -hide options (genisoimage completely ignores any
file/directory excluded with the -exclude options).
@@ -52,21 +52,21 @@
The arguments to the -hide options are either the 'basename' or the 'whole
path name' of a file. That is, if you use the option:
-% mkisofs -hide ABC [-other-options] CD_directory
+% genisoimage -hide ABC [-other-options] CD_directory
then any file with the name ABC will be hidden. If you want to be more
-specific, then use the whole name - as seen by mkisofs e.g.:
+specific, then use the whole name - as seen by genisoimage e.g.:
-% mkisofs -hide CD_directory/XYZ/ABC [-other-options] CD_directory
+% genisoimage -hide CD_directory/XYZ/ABC [-other-options] CD_directory
will hide just the file 'CD_directory/XYZ/ABC' - not any other file called
'ABC' that might exist under 'CD_directory'. However, if your command line
is like:
-% mkisofs -hide CD_directory/XYZ/ABC [-other-options] ./CD_directory
+% genisoimage -hide CD_directory/XYZ/ABC [-other-options] ./CD_directory
Then the file 'CD_directory/XYZ/ABC' will not be hidden because as far as
-mkisofs is concerned. Its whole path is actually './CD_directory/XYZ/ABC'.
+genisoimage is concerned. Its whole path is actually './CD_directory/XYZ/ABC'.
You can use wild cards in the -hide arguments.
@@ -98,7 +98,7 @@
We could use the command line:
-% mkisofs -r -J -hfs -hide MAC -hide PC -hide-joliet MAC \
+% genisoimage -r -J -hfs -hide MAC -hide PC -hide-joliet MAC \
-hide-joliet UNIX -hide-hfs PC -hide-hfs UNIX -o cd.iso cd_dir
This will give a CD that when mounted as a Rock Ridge CD, you will only
@@ -110,7 +110,7 @@
files appear as just 'README' when mounted, then you could use the above
command line with the following:
-% mkisofs -r -J -hfs -graft-points -hide MAC -hide PC -hide-joliet MAC \
+% genisoimage -r -J -hfs -graft-points -hide MAC -hide PC -hide-joliet MAC \
-hide-joliet UNIX -hide-hfs PC -hide-hfs UNIX \
-hide README.hfs -hide README.joliet -hide-joliet README.hfs \
-hide-joliet README.uni -hide-hfs README.joliet -hide-hfs README.unix \
@@ -143,35 +143,35 @@
each of the MAC, UNIX and PC directories contain the correct README, We'll
also change to the 'cd_dir' directory and use the command:
-mkisofs -r -J -hfs -hide MAC -hide PC -hide-joliet MAC \
+genisoimage -r -J -hfs -hide MAC -hide PC -hide-joliet MAC \
-hide-joliet UNIX -hide-hfs PC -hide-hfs UNIX \
-o cd.iso MAC PC UNIX COMMON
You will get errors like:
-mkisofs: Error: UNIX/README and MAC/README have the same Rock Ridge name
+genisoimage: Error: UNIX/README and MAC/README have the same Rock Ridge name
...
-mkisofs: Unable to sort directory
+genisoimage: Unable to sort directory
This is because you can not hide "pathspecs" that are directories ("pathspecs"
are file names given on the command line, or in a path-list file). This a
-"feature" of mkisofs. In this case nothing is actually hidden at all.
+"feature" of genisoimage. In this case nothing is actually hidden at all.
So you might think that the following may work:
-mkisofs -r -J -hfs -hide "MAC/*" -hide "PC/*" -hide-joliet "MAC/*" \
+genisoimage -r -J -hfs -hide "MAC/*" -hide "PC/*" -hide-joliet "MAC/*" \
-hide-joliet "UNIX/*" -hide-hfs "PC/*" -hide-hfs "UNIX/*" \
-o cd.iso MAC PC UNIX COMMON
which may appear to work - but when the CD is mounted as an ISO9660/Rock Ridge
or Joliet CD, then the directory "data" is missing.
-Again this is a feature of mkisofs - the directories PC/data and UNIX/data
-are mapped by mkisofs to the same output directory called "/data" - the
+Again this is a feature of genisoimage - the directories PC/data and UNIX/data
+are mapped by genisoimage to the same output directory called "/data" - the
various "hide" flags are stored with this directory info - in this case as
the output directory "/data" is first hidden from the ISO9660/Rock Ridge and
then the Joliet directory, the net result is that "/data" gets hidden from
-both directories ... the way mkisofs hides HFS directories is slightly
+both directories ... the way genisoimage hides HFS directories is slightly
different, so in this case the directory "data" exists on the HFS volume
and contains the correct contents.
@@ -187,12 +187,12 @@
find UNIX -type f -print > unix.list
find MAC -type f -print > mac.list
-mkisofs -r -J -hfs -hide-list pc.list -hide-list mac.list \
+genisoimage -r -J -hfs -hide-list pc.list -hide-list mac.list \
-hide-joliet-list unix.list -hide-joliet-list mac.list \
-hide-hfs-list pc.list -hide-hfs-list unix.list \
-o cd.iso MAC PC UNIX COMMON
-i.e. instead of trying to hide a directory and letting mkisofs hide its
+i.e. instead of trying to hide a directory and letting genisoimage hide its
contents, we explicitly hide all the files in the directory, but not the
directory and any of its sub-directories.
@@ -204,3 +204,5 @@
James Pearson 22-Nov-2001
Any comments/problems to j.pearson at ge.ucl.ac.uk
+
+Modified for cdrkit/genisoimage by Eduard Bloch, Wed, 27 Dec 2006
Modified: cdrkit/trunk/doc/genisoimage/README.hppaboot
===================================================================
--- cdrkit/trunk/doc/genisoimage/README.hppaboot 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/genisoimage/README.hppaboot 2006-12-27 17:05:27 UTC (rev 640)
@@ -26,10 +26,10 @@
normally. Whether you need a 32- or 64-bit kernel depends on your
hardware; some will even support both.
-To use the hppa boot support code in mkisofs, simply specify the boot
+To use the hppa boot support code in genisoimage, simply specify the boot
command line and file locations (relative to the CD root) as follows:
-mkisofs ... -hppa-cmdline <cmdline, elements separated by spaces or commas> \
+genisoimage ... -hppa-cmdline <cmdline, parts separated by spaces or commas> \
-hppa-kernel-32 <32-bit kernel> \
-hppa-kernel-64 <64-bit kernel> \
-hppa-bootloader <bootloader> \
Modified: cdrkit/trunk/doc/genisoimage/README.macosx
===================================================================
--- cdrkit/trunk/doc/genisoimage/README.macosx 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/genisoimage/README.macosx 2006-12-27 17:05:27 UTC (rev 640)
@@ -1,8 +1,8 @@
-Notes on using the --osx-hfs option when running mkisofs on MacOS X
+Notes on using the --osx-hfs option when running genisoimage on MacOS X
-mkisofs does not use any of the MacOS APIs to access files - it uses
+genisoimage does not use any of the MacOS APIs to access files - it uses
standard (POSIX style) library calls. Under normal circumstances, all
-mkisofs will 'see' is the data fork of files on an HFS (or HFS+) file system.
+genisoimage will 'see' is the data fork of files on an HFS (or HFS+) file system.
However, Apple have provided a way for POSIX style applications to
access the resource fork - using the following syntax:
@@ -24,18 +24,20 @@
example, the TYPE of a file may be based on its file name extension and the
TYPE field in the finder info empty.
-mkisofs knows nothing about these file name extension mappings, so if the
+genisoimage knows nothing about these file name extension mappings, so if the
--osx-hfs option is used and the source files are on MacOS X HFS(+) volumes,
by the fact that they are HFS files, they will get identified as 'MacOS X HFS'
and the resulting file on the output CD image will have empty TYPE and CREATOR
fields.
Therefore, if the input finderinfo is blank and the the resource fork is
-empty, mkisofs will assume the input file is not a 'real' HFS file - which
+empty, genisoimage will assume the input file is not a 'real' HFS file - which
means the TYPE and CREATOR may then be set using the file's magic number or
-mkisofs' file name extension mapping.
+genisoimage' file name extension mapping.
The only real benefit of using the --osx-hfs option is when the source files
are on an OS9 or earlier HFS or HFS+ volume e.g. an existing HFS CD.
James Pearson 3-Jul-2002
+Edited for program name change by Eduard Bloch, 2006
+
Modified: cdrkit/trunk/doc/genisoimage/README.mipsboot
===================================================================
--- cdrkit/trunk/doc/genisoimage/README.mipsboot 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/genisoimage/README.mipsboot 2006-12-27 17:05:27 UTC (rev 640)
@@ -16,10 +16,10 @@
it will do if more than one kernel is listed - it may display a boot
menu).
-To use the SGI boot support code in mkisofs, simply specify the kernel
+To use the SGI boot support code in genisoimage, simply specify the kernel
file locations (relative to the CD root) as follows:
-mkisofs ... -mips-boot <kernel file #1> \
+genisoimage ... -mips-boot <kernel file #1> \
...
-mips-boot <kernel file #n> \
-o mips.iso mips-files
Modified: cdrkit/trunk/doc/genisoimage/README.mipselboot
===================================================================
--- cdrkit/trunk/doc/genisoimage/README.mipselboot 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/genisoimage/README.mipselboot 2006-12-27 17:05:27 UTC (rev 640)
@@ -22,8 +22,8 @@
from that point the system should be able to find the normal OS kernel
and start up fully.
-To use the DEC boot support code in mkisofs, simply specify the kernel
+To use the DEC boot support code in genisoimage, simply specify the kernel
file location (relative to the CD root) as follows:
-mkisofs ... -mipsel-boot <kernel file> -o mipsel.iso mipsel-files
+genisoimage ... -mipsel-boot <kernel file> -o mipsel.iso mipsel-files
Modified: cdrkit/trunk/doc/genisoimage/README.mkhybrid
===================================================================
--- cdrkit/trunk/doc/genisoimage/README.mkhybrid 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/genisoimage/README.mkhybrid 2006-12-27 17:05:27 UTC (rev 640)
@@ -1,5 +1,5 @@
-mkhybrid v1.13 has now merged with, and is a part of mkisofs v1.13
+mkhybrid v1.13 has merged with mkisofs which was forked to genisoimage later
HFS hybrid code Copyright (C) James Pearson 1997, 1998, 1999, 2000
libhfs code Copyright (C) 1996, 1997 Robert Leslie
@@ -16,11 +16,11 @@
*** IMPORTANT ***
The meaning of some of the HFS command line options has changed since
-version 1.12b5.2. This change is to make the way mkisofs decodes the
+version 1.12b5.2. This change is to make the way genisoimage decodes the
various Apple/Unix file formats (CAP, AppleDouble, MacBinary etc.) less
confusing and more logical. To decode one or more of the Apple/Unix files,
then the corresponding "double dash" option must be given (i.e. --cap,
---double, --macbin etc.) mkisofs can search for all known Apple/Unix files
+--double, --macbin etc.) genisoimage can search for all known Apple/Unix files
by using the -probe option.
The options that have changed are:
@@ -68,25 +68,25 @@
To create a HFS hybrid CD with the Joliet and Rock Ridge extensions of
the source directory cd_dir:
-% mkisofs -o cd.iso -r -J -hfs cd_dir
+% genisoimage -o cd.iso -r -J -hfs cd_dir
To create a HFS hybrid CD from the source directory cd_dir that contains
Netatalk Apple/Unix files:
-% mkisofs -o cd.iso --netatalk cd_dir
+% genisoimage -o cd.iso --netatalk cd_dir
To create a HFS hybrid CD from the source directory cd_dir, giving all files
CREATOR and TYPES based on just their filename extensions listed in the file
"mapping".:
-% mkisofs -o cd.iso -map mapping cd_dir
+% genisoimage -o cd.iso -map mapping cd_dir
To create a CD with the 'Apple Extensions to ISO9660', from the source
direcories cd_dir and another_dir. Files in all the known Apple/Unix format
are decoded and any other files are given CREATOR and TYPE based on their
magic number given in the file "magic":
-% mkisofs -o cd.iso -apple -magic magic -probe cd_dir another_dir
+% genisoimage -o cd.iso -apple -magic magic -probe cd_dir another_dir
The following example puts different files on the CD that all have
the name README, but have different contents when seen as a
@@ -101,7 +101,7 @@
CD along with the three README files - but only one will be seen from
each of the three filesystems:
-% mkisofs -o cd.iso -hfs -J -r \
+% genisoimage -o cd.iso -hfs -J -r \
-hide README.hfs -hide README.joliet \
-hide-joliet README.hfs -hide-joliet README.unix \
-hide-hfs README.joliet -hide-hfs README.unix \
@@ -116,7 +116,7 @@
combinations of the hide options ...
-Any comments, bug reports/fixes about the HFS parts of mkisofs to the
+Any comments, bug reports/fixes about the HFS parts of genisoimage to the
address below.
Please state the version, platform and command line used when submitting
@@ -141,5 +141,5 @@
writing at least a short description into the Subject and "Package: cdrkit"
Source: README.mkhybrid from cdrtools package
-Edited for cdrkit by Christian Fromme <kaner at strace.org>
+Edited for cdrkit by Christian Fromme <kaner at strace.org> and Eduard Bloch
Modified: cdrkit/trunk/doc/genisoimage/README.session
===================================================================
--- cdrkit/trunk/doc/genisoimage/README.session 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/genisoimage/README.session 2006-12-27 17:05:27 UTC (rev 640)
@@ -1,24 +1,24 @@
/* @(#)README.session 1.3 99/03/02 eric */
- This release of mkisofs has basic support completed for
+ This release of genisoimage has basic support completed for
multiple sessions. However, we still need some interaction
-between wodim and mkisofs for this to work correctly. This is needed as
+between wodim and genisoimage for this to work correctly. This is needed as
only wodim knows the different ways to gather these numbers for all
-different drives. It may be that future versions of mkisofs will include
+different drives. It may be that future versions of genisoimage will include
the needed support for MMC compliant drives.
- There are a few new options to mkisofs to allow for this.
-The first one is "-M /dev/scd0", and is used so that mkisofs can examine
+ There are a few new options to genisoimage to allow for this.
+The first one is "-M /dev/scd0", and is used so that genisoimage can examine
the entirety of the previous image so that it can figure out what additional
files need to be written in the new session. Note that there are operating
systems that don't allow to read from CD drives with a sector size
-of 2048 bytes per sector. To use mkisofs on such an operating system, you
-will need a version of mkisofs that includes the SCSI transport library
+of 2048 bytes per sector. To use genisoimage on such an operating system, you
+will need a version of genisoimage that includes the SCSI transport library
from wodim. Simply use the dev= syntax from wodim with -M in
-such a case. It will tell mkisofs to use the SCSI transport library to
+such a case. It will tell genisoimage to use the SCSI transport library to
read from the CD instead of using the standard read() OS interface.
- There is also a temporary hack in mkisofs in the form of a '-C' option.
+ There is also a temporary hack in genisoimage in the form of a '-C' option.
The -C option takes two numbers as input, which are delimited by commas.
For example, you could specify "-C 1000,1020", but you should never just
make up numbers to use here. These numbers are determined from wodim.
@@ -31,7 +31,7 @@
In practice you should be able to do something like:
-mkisofs [other options] -C `wodim dev=b,t,l -msinfo` \
+genisoimage [other options] -C `wodim dev=b,t,l -msinfo` \
-M /dev/cdblkdev
Replace 'b,t,l' by the aproriate numbers for SCSIbus, target and lun
@@ -48,5 +48,6 @@
Source: README.session from cdrtools package
-Edited for cdrkit by Christian Fromme <kaner at strace.org>
+Edited for cdrkit by Christian Fromme <kaner at strace.org> and
+Eduard Bloch <blade at debian.org>
Modified: cdrkit/trunk/doc/genisoimage/README.sort
===================================================================
--- cdrkit/trunk/doc/genisoimage/README.sort 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/genisoimage/README.sort 2006-12-27 17:05:27 UTC (rev 640)
@@ -9,13 +9,13 @@
To use, type something like:
-mkisofs -o cdimage.iso -sort sort_file [other_options] cd_dir
+genisoimage -o cdimage.iso -sort sort_file [other_options] cd_dir
The file 'sort_file' contains two columns of:
filename weight
-where filename is the whole name of a file/directory as mkisofs will see it
+where filename is the whole name of a file/directory as genisoimage will see it
and weight is a whole number between +/- 2147483647
The files will be sorted with the highest weights first and lowest last.
@@ -44,7 +44,7 @@
The command:
-mkisofs -o cdimage.iso -sort sort_file cd_dir
+genisoimage -o cdimage.iso -sort sort_file cd_dir
will sort the above file data as:
@@ -61,9 +61,9 @@
File C will have the default weight of 0
Warning: the filenames in the sort list MUST match the whole path as seen by
-mkisofs. i.e. in the above case, if the command line was:
+genisoimage. i.e. in the above case, if the command line was:
-mkisofs -o cdimage.iso -sort sort_file ./cd_dir
+genisoimage -o cdimage.iso -sort sort_file ./cd_dir
then the sort_file filename will have to changed as accordingly.
Modified: cdrkit/trunk/doc/genisoimage/README.sparcboot
===================================================================
--- cdrkit/trunk/doc/genisoimage/README.sparcboot 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/genisoimage/README.sparcboot 2006-12-27 17:05:27 UTC (rev 640)
@@ -1,5 +1,6 @@
# @(#)README.sparcboot 1.1 99/12/12 joerg
-#
+# Edited for program name change by Eduard Bloch, 2006
+
The sparc boot feature does allow you to create your own Sun sparc boot disk.
This will allow you to create modified Solaris install disks or to create
installation CD's for other OS that run on sparc systems.
@@ -35,7 +36,7 @@
dd if=/vol/dev/dsk/c0t6/sol_7_sparc_sun_srvr/s5 of=sun4e
-mkisofs -R -sparc-boot sun4,sun4c,sun4m,sun4d,sun4e -o boot.img /mnt/install
+genisoimage -R -sparc-boot sun4,sun4c,sun4m,sun4d,sun4e -o boot.img /mnt/install
Will create the bootable image in boot.img.
Modified: cdrkit/trunk/doc/genisoimage/README.sunx86boot
===================================================================
--- cdrkit/trunk/doc/genisoimage/README.sunx86boot 2006-12-27 16:30:11 UTC (rev 639)
+++ cdrkit/trunk/doc/genisoimage/README.sunx86boot 2006-12-27 17:05:27 UTC (rev 640)
@@ -1,4 +1,5 @@
# @(#)README.sunx86boot 1.3 05/02/25 Copyright 2003 J. Schilling
+# Edited for program name change by Eduard Bloch, 2006
A Solaris x86 Boot CD looks the like this:
@@ -31,7 +32,7 @@
The El-Torito map for this CD defines a "no-emulation" boot sitting at CD sector 0
and being 4 512 byte sectors in size. This covers the 1024 bytes of above
-boot code. Note that mkisofs will not put the no-emulation boot at sector 0
+boot code. Note that genisoimage will not put the no-emulation boot at sector 0
as it keeps the boot inside the area used for other file content data.
At CD sector 1..15, there is a secondary boot code that understands UFS and tries
@@ -71,6 +72,6 @@
star -cPM -C /vol/dev/dsk/c1t1d0/multi_icd_sol_10_x86/s2 . | star -xp -xdot -C isodir
cp eltoritoboot isodir/.bootimage
-mkisofs -G genboot -no-emul-boot -b .bootimage -c .catalog -R -o bootcd.iso -sunx86-boot /vol/dev/dsk/c1t1d0/multi_icd_sol_10_x86/s0 isodir/
+genisoimage -G genboot -no-emul-boot -b .bootimage -c .catalog -R -o bootcd.iso -sunx86-boot /vol/dev/dsk/c1t1d0/multi_icd_sol_10_x86/s0 isodir/
More information about the Debburn-changes
mailing list