3834 lines
101 KiB
HTML
3834 lines
101 KiB
HTML
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<HTML><HEAD><TITLE>Man page of GENISOIMAGE</TITLE>
|
|
</HEAD><BODY>
|
|
<H1>GENISOIMAGE</H1>
|
|
Section: User Commands (1)<BR>Updated: 13 Dec 2006<BR><A HREF="#index">Index</A>
|
|
<A HREF="/cgi-bin/man/man2html">Return to Main Contents</A><HR>
|
|
|
|
|
|
<A NAME="lbAB"> </A>
|
|
<H2>NAME</H2>
|
|
|
|
genisoimage - create ISO9660/Joliet/HFS filesystem with optional Rock Ridge attributes
|
|
|
|
<A NAME="lbAC"> </A>
|
|
<H2>SYNOPSIS</H2>
|
|
|
|
<B>genisoimage</B>
|
|
|
|
[<I>options</I>]
|
|
|
|
[<B>-o</B>
|
|
|
|
<I>filename</I>]
|
|
|
|
<I>pathspec</I> [<I>pathspec ...</I>]
|
|
|
|
|
|
<A NAME="lbAD"> </A>
|
|
<H2>DESCRIPTION</H2>
|
|
|
|
<B>genisoimage</B>
|
|
|
|
is a pre-mastering program to generate ISO9660/Joliet/HFS hybrid
|
|
filesystems.
|
|
<P>
|
|
|
|
<B>genisoimage</B>
|
|
|
|
is capable of generating the
|
|
<B>System Use Sharing Protocol records (SUSP)</B>
|
|
|
|
specified by the
|
|
<B>Rock Ridge Interchange Protocol</B>.
|
|
|
|
This is used to further describe the
|
|
files in the ISO9660 filesystem to a Unix host, and provides information such
|
|
as long filenames, UID/GID, POSIX permissions, symbolic links, and
|
|
block and character device files.
|
|
<P>
|
|
|
|
If Joliet or HFS hybrid command line options are specified,
|
|
<B>genisoimage</B>
|
|
|
|
will create the additional filesystem metadata needed for Joliet or HFS.
|
|
Otherwise
|
|
<B>genisoimage</B>
|
|
|
|
will generate a pure ISO9660 filesystem.
|
|
<P>
|
|
|
|
<B>genisoimage</B>
|
|
|
|
can generate a
|
|
<I>true</I>
|
|
|
|
(or
|
|
<I>shared</I>)
|
|
|
|
HFS hybrid filesystem. The same files are seen as HFS files when
|
|
accessed from a Macintosh and as ISO9660 files when accessed from other
|
|
machines. HFS stands for
|
|
<I>Hierarchical File System</I>
|
|
|
|
and is the native filesystem used on Macintosh computers.
|
|
<P>
|
|
|
|
As an alternative,
|
|
<B>genisoimage</B>
|
|
|
|
can generate the
|
|
<I>Apple Extensions to ISO9660</I>
|
|
|
|
for each file. These extensions provide each file with CREATOR, TYPE and
|
|
certain Finder flags when accessed from a Macintosh. See the
|
|
<B>HFS MACINTOSH FILE FORMATS</B>
|
|
|
|
section below.
|
|
<P>
|
|
|
|
<B>genisoimage</B>
|
|
|
|
takes a snapshot of a given directory tree, and generates a
|
|
binary image which will correspond to an ISO9660 and/or HFS filesystem when
|
|
written to a block device.
|
|
<P>
|
|
|
|
Each file written to the ISO9660 filesystem must have a filename in the 8.3
|
|
format (up to 8 characters, period, up to 3 characters, all uppercase), even
|
|
if Rock Ridge is in use. This filename is used on systems that are not able
|
|
to make use of the Rock Ridge extensions (such as MS-DOS), and each filename
|
|
in each directory must be different from the other filenames in the same
|
|
directory.
|
|
<B>genisoimage</B>
|
|
|
|
generally tries to form correct names by forcing the Unix filename to
|
|
uppercase and truncating as required, but often this yields unsatisfactory
|
|
results when the truncated names are not all unique.
|
|
<B>genisoimage</B>
|
|
|
|
assigns weightings to each filename, and if two names that are otherwise the
|
|
same are found, the name with the lower priority is renamed to include a
|
|
3-digit number (guaranteed to be unique). For example, the two files
|
|
<I>foo.bar</I>
|
|
|
|
and
|
|
<I>foo.bar.~1~</I>
|
|
|
|
could be rendered as
|
|
<I>FOO.BAR;1</I>
|
|
|
|
and
|
|
<I>FOO000.BAR;1</I>.
|
|
|
|
<P>
|
|
|
|
When used with various HFS options,
|
|
<B>genisoimage</B>
|
|
|
|
will attempt to recognise files stored in a number of Apple/Unix file formats
|
|
and will copy the data and resource forks as well as any
|
|
relevant Finder information. See the
|
|
<B>HFS MACINTOSH FILE FORMATS</B>
|
|
|
|
section below for more about formats
|
|
<B>genisoimage</B>
|
|
|
|
supports.
|
|
<P>
|
|
|
|
Note that
|
|
<B>genisoimage</B>
|
|
|
|
is not designed to communicate with the writer directly. Most writers
|
|
have proprietary command sets which vary from one manufacturer to
|
|
another, and you need a specialized tool to actually burn the disc.
|
|
<B>wodim</B>
|
|
|
|
is one such tool. The latest version of
|
|
<B>wodim</B>
|
|
|
|
is available from
|
|
<I><A HREF="http://www.cdrkit.org/">http://www.cdrkit.org/</A></I>.
|
|
|
|
<P>
|
|
|
|
<B>pathspec</B>
|
|
|
|
is the path of the directory tree to be copied into the ISO9660 filesystem.
|
|
Multiple paths can be specified, and
|
|
<B>genisoimage</B>
|
|
|
|
will merge the files found in all of the specified path components to
|
|
form the filesystem image.
|
|
<P>
|
|
|
|
If the option
|
|
<B>-graft-points</B>
|
|
|
|
has been specified, it is possible to graft the paths at points other
|
|
than the root directory, and it is possible to graft files or
|
|
directories onto the cdrom image with names different than what they
|
|
have in the source filesystem. This is easiest to illustrate with a
|
|
couple of examples. Let's start by assuming that a local file
|
|
<I>../old.lis</I>
|
|
|
|
exists, and you wish to include it in the cdrom image.
|
|
<DL COMPACT>
|
|
<DT id="1"><DD>
|
|
foo/bar/=../old.lis
|
|
</DL>
|
|
<P>
|
|
|
|
will include
|
|
<I>old.lis</I>
|
|
|
|
in the cdrom image at
|
|
<I>/foo/bar/old.lis</I>,
|
|
|
|
while
|
|
<DL COMPACT>
|
|
<DT id="2"><DD>
|
|
foo/bar/xxx=../old.lis
|
|
</DL>
|
|
<P>
|
|
|
|
will include
|
|
<I>old.lis</I>
|
|
|
|
in the cdrom image at
|
|
<I>/foo/bar/xxx</I>.
|
|
|
|
The same sort of syntax can be used with directories as well.
|
|
<B>genisoimage</B>
|
|
|
|
will create any directories required such that the graft
|
|
points exist on the cdrom image --- the directories do not need to
|
|
appear in one of the paths. By default, any directories that are created on
|
|
the fly like this will have permissions 0555 and appear to be owned by the
|
|
person running
|
|
<B>genisoimage</B>.
|
|
|
|
If you wish other permissions or owners of
|
|
the intermediate directories, see
|
|
<B>-uid</B>, <B>-gid</B>, <B>-dir-mode</B>, <B>-file-mode</B> and <B>-new-dir-mode</B>.
|
|
|
|
<P>
|
|
|
|
<B>genisoimage</B>
|
|
|
|
will also run on Windows machines when compiled with Cygnus' cygwin
|
|
(available from
|
|
<I><A HREF="http://www.cygwin.com/">http://www.cygwin.com/</A></I>).
|
|
|
|
Therefore most references in this man page to
|
|
<I>Unix</I>
|
|
|
|
can be replaced with
|
|
<I>Win32</I>.
|
|
|
|
|
|
<A NAME="lbAE"> </A>
|
|
<H2>OPTIONS</H2>
|
|
|
|
<P>
|
|
|
|
Several options can be specified as defaults in a
|
|
<I>.genisoimagerc</I>
|
|
|
|
configuration file, as well as on the command line. If a parameter is
|
|
specified in both places, the setting from the command line is used.
|
|
For details on the format and possible locations of this file, see
|
|
<B><A HREF="/cgi-bin/man/man2html?5+genisoimagerc">genisoimagerc</A></B>(5).
|
|
|
|
<DL COMPACT>
|
|
<DT id="3"><B>-abstract</B><I> file</I>
|
|
|
|
<DD>
|
|
Specifies the abstract filename. There is space for 37 characters.
|
|
Equivalent to
|
|
<B>ABST</B>
|
|
|
|
in the
|
|
<I>.genisoimagerc</I>
|
|
|
|
file.
|
|
<DT id="4"><B>-A</B><I> application_id</I>
|
|
|
|
<DD>
|
|
Specifies a text string that will be written into the volume header.
|
|
This should describe the application that will be on the disc. There
|
|
is space for 128 characters. Equivalent to
|
|
<B>APPI</B>
|
|
|
|
in the
|
|
<I>.genisoimagerc</I>
|
|
|
|
file.
|
|
<DT id="5"><B>-allow-limited-size</B>
|
|
|
|
<DD>
|
|
When processing files larger than 2GiB which cannot be easily represented in
|
|
ISO9660, add them with a shrunk visible file size to ISO9660 and with the
|
|
correct visible file size to the UDF system. The result is an inconsistent
|
|
filesystem and users need to make sure that they really use UDF rather than
|
|
ISO9660 driver to read a such disk. Implies enabling
|
|
<B>-udf.</B>
|
|
|
|
<DT id="6"><B>-allow-leading-dots</B>
|
|
|
|
<DD>
|
|
<DT id="7"><B>-ldots</B>
|
|
|
|
<DD>
|
|
Allow ISO9660 filenames to begin with a period. Usually, a leading dot is
|
|
replaced with an underscore in order to maintain MS-DOS compatibility.
|
|
<BR>
|
|
|
|
This violates the ISO9660 standard, but it happens to work on many systems.
|
|
Use with caution.
|
|
<DT id="8"><B>-allow-lowercase</B>
|
|
|
|
<DD>
|
|
This options allows lowercase characters to appear in ISO9660 filenames.
|
|
<BR>
|
|
|
|
This violates the ISO9660 standard, but it happens to work on some systems.
|
|
Use with caution.
|
|
<DT id="9"><B>-allow-multidot</B>
|
|
|
|
<DD>
|
|
This options allows more than one dot to appear in ISO9660 filenames.
|
|
A leading dot is not affected by this option, it
|
|
may be allowed separately using
|
|
<B>-allow-leading-dots</B>.
|
|
|
|
<BR>
|
|
|
|
This violates the ISO9660 standard, but it happens to work on many systems.
|
|
Use with caution.
|
|
<DT id="10"><B>-biblio</B><I> file</I>
|
|
|
|
<DD>
|
|
Specifies the bibliographic filename. There is space for 37 characters.
|
|
Equivalent to
|
|
<B>BIBL</B>
|
|
|
|
in the
|
|
<I>.genisoimagerc</I>
|
|
|
|
file.
|
|
<DT id="11"><B>-cache-inodes</B>
|
|
|
|
<DD>
|
|
<DT id="12"><B>-no-cache-inodes</B>
|
|
|
|
<DD>
|
|
Enable or disable caching inode and device numbers to find hard links
|
|
to files. If
|
|
<B>genisoimage</B>
|
|
|
|
finds a hard link (a file with multiple names), the file will also be
|
|
hard-linked on the CD, so the file contents only appear once. This
|
|
helps to save space.
|
|
<B>-cache-inodes</B>
|
|
|
|
is default on Unix-like operating systems, but
|
|
<B>-no-cache-inodes</B>
|
|
|
|
is default on some other systems such as Cygwin, because it is not safe
|
|
to assume that inode numbers are unique on those systems. (Some
|
|
versions of Cygwin create fake inode numbers using a weak hashing
|
|
algorithm, which may produce duplicates.) If two files have the same
|
|
inode number but are not hard links to the same file,
|
|
<B>genisoimage -cache-inodes</B>
|
|
|
|
will not behave correctly.
|
|
<B>-no-cache-inodes</B>
|
|
|
|
is safe in all situations, but in that case
|
|
<B>genisoimage</B>
|
|
|
|
cannot detect hard links, so the resulting CD image may be larger
|
|
than necessary.
|
|
<DT id="13"><B>-alpha-boot</B><I> alpha_boot_image</I>
|
|
|
|
<DD>
|
|
Specifies the path and filename of the boot image to be used when
|
|
making an Alpha/SRM bootable CD. The pathname must be relative to the
|
|
source path specified to
|
|
<B>genisoimage</B>.
|
|
|
|
<DT id="14"><B>-hppa-bootloader</B><I> hppa_bootloader_image</I>
|
|
|
|
<DD>
|
|
Specifies the path and filename of the boot image to be used when
|
|
making an HPPA bootable CD. The pathname must be relative to the
|
|
source path specified to
|
|
<B>genisoimage</B>.
|
|
|
|
Other options are required, at the very least a kernel filename and
|
|
a boot command line. See the
|
|
<B>HPPA NOTES</B>
|
|
|
|
section below for more information.
|
|
<DT id="15"><B>-hppa-cmdline</B><I> hppa_boot_command_line</I>
|
|
|
|
<DD>
|
|
Specifies the command line to be passed to the HPPA boot loader when
|
|
making a bootable CD. Separate the parameters with spaces or
|
|
commas. More options must be passed to
|
|
<B>genisoimage,</B>
|
|
|
|
at the very least a kernel filename and the boot loader filename.
|
|
See the
|
|
<B>HPPA NOTES</B>
|
|
|
|
section below for more information.
|
|
<DT id="16"><B>-hppa-kernel-32</B><I> hppa_kernel_32</I>
|
|
|
|
<DD>
|
|
<DT id="17"><B>-hppa-kernel-64</B><I> hppa_kernel_64</I>
|
|
|
|
<DD>
|
|
Specifies the path and filename of the 32-bit and/or 64-bit kernel images
|
|
to be used when making an HPPA bootable CD. The pathnames must be
|
|
relative to the source path specified to
|
|
<B>genisoimage</B>.
|
|
|
|
Other options are required, at the very least the boot loader filename
|
|
and the boot command line. See the
|
|
<B>HPPA NOTES</B>
|
|
|
|
section below for more information.
|
|
<DT id="18"><B>-hppa-ramdisk</B><I> hppa_ramdisk_image</I>
|
|
|
|
<DD>
|
|
Specifies the path and filename of the ramdisk image to be used when
|
|
making an HPPA bootable CD. The pathname must be relative to the
|
|
source path specified to
|
|
<B>genisoimage</B>.
|
|
|
|
This parameter is optional. Other options are required, at the very
|
|
least a kernel filename and the boot command line. See the
|
|
<B>HPPA NOTES</B>
|
|
|
|
section below for more information.
|
|
<DT id="19"><B>-mips-boot</B><I> mips_boot_image</I>
|
|
|
|
<DD>
|
|
Specifies the path and filename of the boot image to be used when
|
|
making an SGI/big-endian MIPS bootable CD. The pathname must be
|
|
relative to the source path specified to
|
|
<B>genisoimage</B>.
|
|
|
|
This option may be specified several times, to store up to 15 boot
|
|
images.
|
|
<DT id="20"><B>-mipsel-boot</B><I> mipsel_boot_image</I>
|
|
|
|
<DD>
|
|
Specifies the path and filename of the boot image to be used when
|
|
making an DEC/little-endian MIPS bootable CD. The pathname must be
|
|
relative to the source path specified to
|
|
<B>genisoimage</B>.
|
|
|
|
<DT id="21"><B>-B</B><I> img_sun4,img_sun4c,img_sun4m,img_sun4d,img_sun4e</I>
|
|
|
|
<DD>
|
|
<DT id="22"><B>-sparc-boot</B><I> img_sun4,img_sun4c,img_sun4m,img_sun4d,img_sun4e</I>
|
|
|
|
<DD>
|
|
Specifies a comma-separated list of boot images that are needed to make
|
|
a bootable CD for SPARC systems.
|
|
Partition 0 is used for the ISO9660 image, the first image file is mapped
|
|
to partition 1.
|
|
The comma-separated list may have up to 7 fields, including empty fields.
|
|
This option is required to make a bootable CD for Sun SPARC systems.
|
|
If
|
|
<B>-B</B>
|
|
|
|
or
|
|
<B>-sparc-boot</B>
|
|
|
|
has been specified, the first sector of the resulting image will
|
|
contain a Sun disk label. This disk label specifies slice 0 for the
|
|
ISO9660 image and slices 1 to 7 for the boot images that
|
|
have been specified with this option. Byte offsets 512 to 8191
|
|
within each of the additional boot images must contain a primary boot
|
|
that works for the appropriate SPARC architecture. The rest of each
|
|
of the images usually contains a UFS filesystem used for the primary
|
|
kernel boot stage.
|
|
<DT id="23"><DD>
|
|
The implemented boot method is the one found with SunOS 4.x and SunOS 5.x.
|
|
However, it does not depend on SunOS internals but only on properties of
|
|
the Open Boot prom, so it should be usable for any OS for SPARC systems.
|
|
For more information also see the
|
|
<B>NOTES</B>
|
|
|
|
section below.
|
|
<DT id="24"><DD>
|
|
If the special filename
|
|
<B>...</B>
|
|
|
|
is used, the actual and all following boot partitions are mapped to the
|
|
previous partition. If
|
|
<B>genisoimage</B>
|
|
|
|
is called with
|
|
<B>-G</B><I> image </I><B>-B</B><I> ...</I>
|
|
|
|
all boot partitions are mapped to the partition that contains the ISO9660
|
|
filesystem image and the generic boot image that is located in the first
|
|
16 sectors of the disc is used for all architectures.
|
|
<DT id="25"><B>-G</B><I> generic_boot_image</I>
|
|
|
|
<DD>
|
|
Specifies the path and filename of the generic boot image to be used when making
|
|
a generic bootable CD. The boot image will be placed on the first 16
|
|
sectors of the CD, before the ISO9660 primary volume descriptor.
|
|
If this option is used together with
|
|
<B>-sparc-boot</B>,
|
|
|
|
the Sun disk label will overlay the first 512 bytes of the generic
|
|
boot image.
|
|
<DT id="26"><B>-b</B><I> eltorito_boot_image</I>
|
|
|
|
<DD>
|
|
Specifies the path and filename of the boot image to be used when making
|
|
an El Torito bootable CD for x86 PCs. The pathname must be relative to
|
|
the source path specified to
|
|
<B>genisoimage</B>.
|
|
|
|
This option is required to make an El Torito bootable CD.
|
|
The boot image must be exactly 1200 kB, 1440 kB or 2880 kB, and
|
|
<B>genisoimage</B>
|
|
|
|
will use this size when creating the output ISO9660 filesystem. The PC
|
|
BIOS will use the image to emulate a floppy disk, so the first 512-byte
|
|
sector should contain PC boot code. This will work, for example, if
|
|
the boot image is a LILO-based boot floppy.
|
|
<DT id="27"><DD>
|
|
If the boot image is not an image of a floppy, you need to add either
|
|
<B>-hard-disk-boot</B> or <B>-no-emul-boot</B>.
|
|
|
|
If the system should not boot off the emulated disk, use
|
|
<B>-no-boot</B>.
|
|
|
|
<DT id="28"><DD>
|
|
If
|
|
<B>-sort</B>
|
|
|
|
has not been specified, the boot images are sorted
|
|
with low priority (+2) to the beginning of the medium.
|
|
If you don't like this, you need to specify a sort weight of 0 for the boot images.
|
|
<DT id="29"><B>-eltorito-alt-boot</B>
|
|
|
|
<DD>
|
|
Start with a new set of El Torito boot parameters. Up to 63 El Torito
|
|
boot entries may be stored on a single CD.
|
|
<DT id="30"><B>-hard-disk-boot</B>
|
|
|
|
<DD>
|
|
Specifies that the boot image used to create El Torito bootable CDs is
|
|
a hard disk image. The image must begin with a master boot
|
|
record that contains a single partition.
|
|
<DT id="31"><B>-no-emul-boot</B>
|
|
|
|
<DD>
|
|
Specifies that the boot image used to create El Torito bootable CDs is
|
|
a "no emulation" image. The system will load and execute this image without
|
|
performing any disk emulation.
|
|
<DT id="32"><B>-no-boot</B>
|
|
|
|
<DD>
|
|
Specifies that the created El Torito CD should be marked as not bootable. The
|
|
system will provide an emulated drive for the image, but will boot off
|
|
a standard boot device.
|
|
<DT id="33"><B>-boot-load-seg</B><I> segment_address</I>
|
|
|
|
<DD>
|
|
Specifies the load segment address of the boot image for no-emulation
|
|
El Torito CDs.
|
|
<DT id="34"><B>-boot-load-size</B><I> load_sectors</I>
|
|
|
|
<DD>
|
|
Specifies the number of "virtual" (512-byte) sectors to load in
|
|
no-emulation mode. The default is to load the entire boot file. Some
|
|
BIOSes may have problems if this is not a multiple of 4.
|
|
<DT id="35"><B>-boot-info-table</B>
|
|
|
|
<DD>
|
|
Specifies that a 56-byte table with information of the CD-ROM layout
|
|
will be patched in at offset 8 in the boot file. If this option is
|
|
given, the boot file is
|
|
<I>modified in the source filesystem</I>,
|
|
|
|
so make a copy of this file if it cannot be easily regenerated!
|
|
See the
|
|
<B>EL TORITO BOOT INFO TABLE</B>
|
|
|
|
section for a description of this table.
|
|
<DT id="36"><B>-C</B><I> last_sess_start,next_sess_start</I>
|
|
|
|
<DD>
|
|
This option is needed to create a CD Extra or the image of a second
|
|
session or a higher-level session for a multisession disc.
|
|
<B>-C</B>
|
|
|
|
takes two numbers separated by a comma. The first is the first sector
|
|
in the last session of the disc that should be appended to.
|
|
The second number is the starting sector number of the new session.
|
|
The correct numbers may be retrieved by calling
|
|
<B>wodim -msinfo ...</B>
|
|
|
|
If
|
|
<B>-C</B>
|
|
|
|
is used in conjunction with
|
|
<B>-M</B>,
|
|
|
|
<B>genisoimage</B>
|
|
|
|
will create a filesystem image that is intended to be a continuation
|
|
of the previous session.
|
|
If
|
|
<B>-C</B>
|
|
|
|
is used without
|
|
<B>-M</B>,
|
|
|
|
<B>genisoimage</B>
|
|
|
|
will create a filesystem image that is intended to be used for a second
|
|
session on a CD Extra. This is a multisession CD that holds audio data
|
|
in the first session and an ISO9660 filesystem in the second session.
|
|
<DT id="37"><B>-c</B><I> boot_catalog</I>
|
|
|
|
<DD>
|
|
Specifies the path and filename of the boot catalog, which is required
|
|
for an El Torito bootable CD. The pathname must be relative to the source
|
|
path specified to
|
|
<B>genisoimage</B>.
|
|
|
|
This file will be inserted into the output tree and not created
|
|
in the source filesystem, so be
|
|
sure the specified filename does not conflict with an existing file, or
|
|
it will be excluded. Usually a name like
|
|
<I>boot.catalog</I>
|
|
|
|
is chosen.
|
|
<DT id="38"><DD>
|
|
If
|
|
<B>-sort</B>
|
|
|
|
has not been specified, the boot catalog sorted
|
|
with low priority (+1) to the beginning of the medium.
|
|
If you don't like this, you need to specify a sort weight of 0 for the boot catalog.
|
|
<DT id="39"><B>-check-oldnames</B>
|
|
|
|
<DD>
|
|
Check all filenames imported from the old session for compliance with
|
|
the ISO9660 file naming rules.
|
|
Without this option, only names longer than 31 characters are checked,
|
|
as these files are a serious violation of the ISO9660 standard.
|
|
<DT id="40"><B>-check-session</B><I> file</I>
|
|
|
|
<DD>
|
|
Check all old sessions for compliance with actual
|
|
<B>genisoimage </B>
|
|
|
|
ISO9660 file naming rules.
|
|
This is a high-level option that combines
|
|
<B>-M</B>
|
|
|
|
<I>file</I>
|
|
|
|
<B>-C 0,0 -check-oldnames</B>.
|
|
|
|
For the parameter
|
|
<I>file</I>,
|
|
|
|
see the description of
|
|
<B>-M</B>.
|
|
|
|
<DT id="41"><B>-copyright</B><I> file</I>
|
|
|
|
<DD>
|
|
Specifies copyright information, typically a filename on the disc.
|
|
There is space for 37 characters. Equivalent to
|
|
<B>COPY</B>
|
|
|
|
in the
|
|
<I>.genisoimagerc</I>
|
|
|
|
file.
|
|
<DT id="42"><B>-d</B>
|
|
|
|
<DD>
|
|
Do not append a period to files that do not have one.
|
|
<BR>
|
|
|
|
This violates the ISO9660 standard, but it happens to work on many systems.
|
|
Use with caution.
|
|
<DT id="43"><B>-D</B>
|
|
|
|
<DD>
|
|
Do not use deep directory relocation, and instead just pack them in the
|
|
way we see them.
|
|
<BR>
|
|
|
|
If ISO9660:1999 has not been selected,
|
|
this violates the ISO9660 standard, but it happens to work on many systems.
|
|
Use with caution.
|
|
<DT id="44"><B>-dir-mode</B><I> mode</I>
|
|
|
|
<DD>
|
|
Overrides the mode of directories used to create the image to
|
|
<I>mode</I>,
|
|
|
|
specified as 4 digits of permission bits as in
|
|
<B><A HREF="/cgi-bin/man/man2html?1+chmod">chmod</A></B>(1).
|
|
|
|
This option automatically enables Rock Ridge extensions.
|
|
<DT id="45"><B>-dvd-video</B>
|
|
|
|
<DD>
|
|
Generate a DVD-Video compliant UDF filesystem. This is done by sorting the
|
|
order of the content of the appropriate files and by adding padding
|
|
between the files if needed.
|
|
Note that the sorting only works if the DVD-Video filenames include uppercase
|
|
characters only.
|
|
<DT id="46"><DD>
|
|
Note that in order to get a DVD-Video compliant filesystem image, you
|
|
need to prepare a DVD-Video compliant directory tree. This requires a
|
|
directory
|
|
<B>VIDEO_TS</B>
|
|
|
|
(all caps) in the root directory of the resulting DVD, and usually
|
|
another directory
|
|
<B>AUDIO_TS</B>.
|
|
|
|
<B>VIDEO_TS</B>
|
|
|
|
needs to include all needed files (filenames must be all caps) for a
|
|
compliant DVD-Video filesystem.
|
|
<DT id="47"><B>-f</B>
|
|
|
|
<DD>
|
|
Follow symbolic links when generating the filesystem. When this option is not
|
|
in use, symbolic links will be entered using Rock Ridge if enabled, otherwise
|
|
they will be ignored.
|
|
<DT id="48"><B>-file-mode</B><I> mode</I>
|
|
|
|
<DD>
|
|
Overrides the mode of regular files used to create the image to
|
|
<I>mode</I>,
|
|
|
|
specified as 4 digits of permission bits as in
|
|
<B><A HREF="/cgi-bin/man/man2html?1+chmod">chmod</A></B>(1).
|
|
|
|
This option automatically enables Rock Ridge extensions.
|
|
<DT id="49"><B>-gid</B><I> gid</I>
|
|
|
|
<DD>
|
|
Overrides the group ID read from the source files to the value of
|
|
<I>gid</I>.
|
|
|
|
Specifying this option automatically enables Rock Ridge extensions.
|
|
<DT id="50"><B>-gui</B>
|
|
|
|
<DD>
|
|
Switch the behaviour for a GUI. This currently makes the output more verbose
|
|
but may have other effects in the future.
|
|
<DT id="51"><B>-graft-points</B>
|
|
|
|
<DD>
|
|
Allow use of graft points for filenames. If this option is used, all
|
|
filenames are checked for graft points. The filename is divided at the
|
|
first unescaped equal sign. All occurrences of `\' and `=' characters
|
|
must be escaped with `\' if
|
|
<B>-graft-points</B>
|
|
|
|
has been specified.
|
|
<DT id="52"><B>-hide</B><I> glob</I>
|
|
|
|
<DD>
|
|
Hide any files matching
|
|
<I>glob</I>,
|
|
|
|
a shell wildcard pattern, from being seen in the ISO9660 or Rock Ridge
|
|
directory.
|
|
<I>glob</I>
|
|
|
|
may match any part of the filename or path. If
|
|
<I>glob</I>
|
|
|
|
matches a directory, the contents of that directory will be hidden.
|
|
In order to match a directory name, make sure the pathname does not include
|
|
a trailing `/' character.
|
|
All the hidden files will still be written to the output CD image file.
|
|
See also
|
|
<B>-hide-joliet</B>,
|
|
|
|
and
|
|
<I>README.hide</I>.
|
|
|
|
This option may be used multiple times.
|
|
<DT id="53"><B>-hide-list</B><I> file</I>
|
|
|
|
<DD>
|
|
A file containing a list of shell wildcards to be hidden. See
|
|
<B>-hide</B>.
|
|
|
|
<DT id="54"><B>-hidden</B><I> glob</I>
|
|
|
|
<DD>
|
|
Add the hidden (existence) ISO9660 directory attribute for files and
|
|
directories matching
|
|
<I>glob</I>,
|
|
|
|
a shell wildcard pattern. This attribute will prevent the files from
|
|
being shown by some MS-DOS and Windows commands.
|
|
<I>glob</I>
|
|
|
|
may match any part of the filename or path.
|
|
In order to match a directory name, make sure the pathname does not include
|
|
a trailing `/' character.
|
|
This option may be used multiple times.
|
|
<DT id="55"><B>-hidden-list</B><I> file</I>
|
|
|
|
<DD>
|
|
A file containing a list of shell wildcards to get the hidden
|
|
attribute. See
|
|
<B>-hidden</B>.
|
|
|
|
<DT id="56"><B>-hide-joliet</B><I> glob</I>
|
|
|
|
<DD>
|
|
Hide files and directories matching
|
|
<I>glob</I>,
|
|
|
|
a shell wildcard pattern, from being seen in the Joliet directory.
|
|
<I>glob</I>
|
|
|
|
may match any part of the filename or path. If
|
|
<I>glob</I>
|
|
|
|
matches a directory, the contents of that directory will be hidden.
|
|
In order to match a directory name, make sure the pathname does not include
|
|
a trailing `/' character.
|
|
All the hidden files will still be written to the output CD image file.
|
|
This option is usually used with
|
|
<B>-hide</B>.
|
|
|
|
See also
|
|
<I>README.hide</I>.
|
|
|
|
This option may be used multiple times.
|
|
<DT id="57"><B>-hide-joliet-list</B><I> file</I>
|
|
|
|
<DD>
|
|
A file containing a list of shell wildcards to be hidden from the
|
|
Joliet tree. See
|
|
<B>-hide-joliet</B>.
|
|
|
|
<DT id="58"><B>-hide-joliet-trans-tbl</B>
|
|
|
|
<DD>
|
|
Hide the
|
|
<I>TRANS.TBL</I>
|
|
|
|
files from the Joliet tree.
|
|
These files usually don't make sense in the Joliet world as they list
|
|
the real name and the ISO9660 name which may both be different from the
|
|
Joliet name.
|
|
<DT id="59"><B>-hide-rr-moved</B>
|
|
|
|
<DD>
|
|
Rename the directory
|
|
<I>RR_MOVED</I>
|
|
|
|
to
|
|
<I>.rr_moved</I>
|
|
|
|
in the Rock Ridge tree.
|
|
It seems to be impossible to completely hide the
|
|
<I>RR_MOVED</I>
|
|
|
|
directory from the Rock Ridge tree.
|
|
This option only makes the visible tree less confusing for
|
|
people who don't know what this directory is for.
|
|
If you need to have no
|
|
<I>RR_MOVED</I>
|
|
|
|
directory at all, you should use
|
|
<B>-D</B>.
|
|
|
|
Note that if
|
|
<B>-D</B>
|
|
|
|
has been specified, the resulting filesystem is not ISO9660
|
|
level-1 compliant and will not be readable on MS-DOS.
|
|
See also the
|
|
<B>NOTES</B>
|
|
|
|
section.
|
|
<DT id="60"><B>-input-charset</B><I> charset</I>
|
|
|
|
<DD>
|
|
Input charset that defines the characters used in local filenames.
|
|
To get a list of valid charset names, call
|
|
<B>genisoimage -input-charset help</B>.
|
|
|
|
To get a 1:1 mapping, you may use
|
|
<B>default</B>
|
|
|
|
as charset name. The default initial values are
|
|
<I>cp437</I>
|
|
|
|
on DOS-based systems and
|
|
<I>iso8859-1</I>
|
|
|
|
on all other systems. See the
|
|
<B>CHARACTER SETS</B>
|
|
|
|
section below for more details.
|
|
<DT id="61"><B>-output-charset</B><I> charset</I>
|
|
|
|
<DD>
|
|
Output charset that defines the characters that will be used in Rock Ridge
|
|
filenames. Defaults to the input charset. See
|
|
<B>CHARACTER SETS</B>
|
|
|
|
section below for more details.
|
|
<DT id="62"><B>-iso-level</B><I> level</I>
|
|
|
|
<DD>
|
|
Set the ISO9660 conformance level. Valid numbers are 1 to 4.
|
|
<DT id="63"><DD>
|
|
With level 1, files may only consist of one section and filenames are
|
|
restricted to 8.3 characters.
|
|
<DT id="64"><DD>
|
|
With level 2, files may only consist of one section.
|
|
<DT id="65"><DD>
|
|
With level 3, no restrictions (other than ISO-9660:1988) do apply.
|
|
<DT id="66"><DD>
|
|
With all ISO9660 levels from 1 to 3, all filenames are restricted to
|
|
uppercase letters, numbers and underscores (_). Filenames are
|
|
limited to 31 characters, directory nesting is limited to 8
|
|
levels, and pathnames are limited to 255 characters.
|
|
<DT id="67"><DD>
|
|
Level 4 officially does not exist but
|
|
<B>genisoimage</B>
|
|
|
|
maps it to ISO-9660:1999, which is ISO9660 version 2.
|
|
<DT id="68"><DD>
|
|
With level 4, an enhanced volume descriptor with version number
|
|
and file structure version number set to 2 is emitted.
|
|
Directory nesting is not limited to 8 levels,
|
|
there is no need for a file to contain a dot and the dot has no
|
|
special meaning, filenames do not have version numbers,
|
|
|
|
|
|
|
|
and filenames can be up to 207 characters long, or 197 characters if
|
|
Rock Ridge is used.
|
|
<DT id="69"><DD>
|
|
When creating Version 2 images,
|
|
<B>genisoimage</B>
|
|
|
|
emits an enhanced volume descriptor, similar but not identical to a
|
|
primary volume descriptor. Be careful not to use broken software
|
|
to make ISO9660 images bootable by assuming a second PVD copy and patching
|
|
this putative PVD copy into an El Torito VD.
|
|
<DT id="70"><B>-J</B>
|
|
|
|
<DD>
|
|
Generate Joliet directory records in addition to regular ISO9660
|
|
filenames. This is primarily useful when the discs are to be used on
|
|
Windows machines. Joliet filenames are specified in Unicode and each
|
|
path component can be up to 64 Unicode characters long.
|
|
Note that Joliet is not a standard --- only Microsoft Windows and Linux
|
|
systems can read Joliet extensions. For greater portability, consider
|
|
using both Joliet and Rock Ridge extensions.
|
|
<DT id="71"><B>-joliet-long</B>
|
|
|
|
<DD>
|
|
Allow Joliet filenames to be up to 103 Unicode characters, instead of
|
|
64. This breaks the Joliet specification, but appears to work. Use
|
|
with caution.
|
|
|
|
|
|
|
|
|
|
<DT id="72"><B>-jcharset</B><I> charset</I>
|
|
|
|
<DD>
|
|
A combination of
|
|
<B>-J -input-charset</B>
|
|
|
|
<I>charset</I>.
|
|
|
|
See the
|
|
<B>CHARACTER SETS</B>
|
|
|
|
section below for more details.
|
|
<DT id="73"><B>-l</B>
|
|
|
|
<DD>
|
|
Allow full 31-character filenames. Normally the ISO9660 filename will be in an
|
|
8.3 format which is compatible with MS-DOS, even though the ISO9660 standard
|
|
allows filenames of up to 31 characters. If you use this option, the disc may
|
|
be difficult to use on a MS-DOS system, but will work on most other systems.
|
|
Use with caution.
|
|
<DT id="74"><B>-L</B>
|
|
|
|
<DD>
|
|
Outdated option; use
|
|
<B>-allow-leading-dots</B>
|
|
|
|
instead.
|
|
<DT id="75"><B>-jigdo-jigdo</B><I> jigdo_file</I>
|
|
|
|
<DD>
|
|
Produce a
|
|
<B>jigdo</B>
|
|
|
|
<I>.jigdo</I>
|
|
|
|
metadata file as well as the filesystem image. See the
|
|
<B>JIGDO NOTES</B>
|
|
|
|
section below for more information.
|
|
<DT id="76"><B>-jigdo-template</B><I> template_file</I>
|
|
|
|
<DD>
|
|
Produce a
|
|
<B>jigdo</B>
|
|
|
|
<I>.template</I>
|
|
|
|
file as well as the filesystem image. See the
|
|
<B>JIGDO NOTES</B>
|
|
|
|
section below for more information.
|
|
<DT id="77"><B>-jigdo-min-file-size</B><I> size</I>
|
|
|
|
<DD>
|
|
Specify the minimum size for a file to be listed in the
|
|
<I>.jigdo</I>
|
|
|
|
file. Default (and minimum allowed) is 1KB. See the
|
|
<B>JIGDO NOTES</B>
|
|
|
|
section below for more information.
|
|
<DT id="78"><B>-jigdo-force-md5</B><I> path</I>
|
|
|
|
<DD>
|
|
Specify a file pattern where files
|
|
<I>must</I>
|
|
|
|
be contained in the externally-supplied MD5 list as supplied by
|
|
<B>-md5-list</B>.
|
|
|
|
See the
|
|
<B>JIGDO NOTES</B>
|
|
|
|
section below for more information.
|
|
<DT id="79"><B>-jigdo-exclude</B><I> path</I>
|
|
|
|
<DD>
|
|
Specify a file pattern where files will not be listed in the
|
|
<I>.jigdo</I>
|
|
|
|
file. See the
|
|
<B>JIGDO NOTES</B>
|
|
|
|
section below for more information.
|
|
<DT id="80"><B>-jigdo-map</B><I> path</I>
|
|
|
|
<DD>
|
|
Specify a pattern mapping for the jigdo file
|
|
(e.g.
|
|
<I>Debian=/mirror/debian</I>).
|
|
|
|
See the
|
|
<B>JIGDO NOTES</B>
|
|
|
|
section below for more information.
|
|
<DT id="81"><B>-md5-list</B><I> md5_file</I>
|
|
|
|
<DD>
|
|
Specify a file containing the MD5sums, sizes and pathnames of the
|
|
files to be included in the
|
|
<I>.jigdo</I>
|
|
|
|
file. See the
|
|
<B>JIGDO NOTES</B>
|
|
|
|
section below for more information.
|
|
<DT id="82"><B>-jigdo-template-compress</B><I> algorithm</I>
|
|
|
|
<DD>
|
|
Specify a compression algorithm to use for template date. gzip and
|
|
bzip2 are currently supported, and gzip is the default. See the
|
|
<B>JIGDO NOTES</B>
|
|
|
|
section below for more information.
|
|
<DT id="83"><B>-log-file</B><I> log_file</I>
|
|
|
|
<DD>
|
|
Redirect all error, warning and informational messages to
|
|
<I>log_file</I>
|
|
|
|
instead of the standard error.
|
|
<DT id="84"><B>-m</B><I> glob</I>
|
|
|
|
<DD>
|
|
Exclude files matching
|
|
<I>glob</I>,
|
|
|
|
a shell wildcard pattern, from being written to CD-ROM.
|
|
<I>glob</I>
|
|
|
|
may match either the filename component or the full pathname.
|
|
This option may be used multiple times. For example:
|
|
<P>
|
|
<BR> genisoimage -o rom -m '*.o' -m core -m foobar
|
|
<P>
|
|
would exclude all files ending in `.o', or called
|
|
<I>core</I> or <I>foobar</I>
|
|
|
|
from the image. Note that if you had a directory called
|
|
<I>foobar</I>,
|
|
|
|
it too (and of course all its descendants) would be excluded.
|
|
<DT id="85"><B>-exclude-list</B><I> file</I>
|
|
|
|
<DD>
|
|
A file containing a list of shell wildcards to be excluded. See
|
|
<B>-m</B>.
|
|
|
|
<DT id="86"><B>-max-iso9660-filenames</B>
|
|
|
|
<DD>
|
|
Allow ISO9660 filenames to be up to 37 characters long.
|
|
This option enables
|
|
<B>-N</B>
|
|
|
|
as the extra name space is taken from the space reserved for
|
|
file version numbers.
|
|
<BR>
|
|
|
|
This violates the ISO9660 standard, but it happens to work on many systems.
|
|
Although a conforming application needs to provide a buffer space of at
|
|
least 37 characters, discs created with this option may cause a buffer
|
|
overflow in the reading operating system. Use with extreme care.
|
|
<DT id="87"><B>-M</B><I> path</I>
|
|
|
|
<DD>
|
|
<DT id="88"><B>-M</B><I> device</I>
|
|
|
|
<DD>
|
|
<DT id="89"><B>-dev</B><I> device</I>
|
|
|
|
<DD>
|
|
Specifies path to existing ISO9660 image to be merged. The alternate form
|
|
takes a SCSI device specifier that uses the same syntax as the
|
|
<B>dev=</B>
|
|
|
|
parameter of
|
|
<B>wodim</B>.
|
|
|
|
The output of
|
|
<B>genisoimage</B>
|
|
|
|
will be a new session which should get written to the end of the
|
|
image specified in
|
|
<B>-M</B>.
|
|
|
|
Typically this requires multisession capability for the CD recorder
|
|
used to write the image. This option may only be used in conjunction
|
|
with
|
|
<B>-C</B>.
|
|
|
|
<DT id="90"><B>-N</B>
|
|
|
|
<DD>
|
|
Omit version numbers from ISO9660 filenames.
|
|
<BR>
|
|
|
|
This violates the ISO9660 standard, but no one really uses the
|
|
version numbers anyway. Use with caution.
|
|
<DT id="91"><B>-new-dir-mode</B><I> mode</I>
|
|
|
|
<DD>
|
|
Specify the mode, a 4-digit number as used in
|
|
<B><A HREF="/cgi-bin/man/man2html?1+chmod">chmod</A></B>(1),
|
|
|
|
to use when creating new directories in the filesystem image. The
|
|
default is 0555.
|
|
<DT id="92"><B>-nobak</B>
|
|
|
|
<DD>
|
|
<DT id="93"><B>-no-bak</B>
|
|
|
|
<DD>
|
|
Exclude backup files files on the ISO9660 filesystem; that is,
|
|
filenames that contain the characters `~' or `#' or end in
|
|
<I>.bak</I>.
|
|
|
|
These are typically backup files for Unix text editors.
|
|
<DT id="94"><B>-force-rr</B>
|
|
|
|
<DD>
|
|
Do not use the automatic Rock Ridge attributes recognition for previous sessions.
|
|
This can work around problems with images created by, e.g., NERO Burning ROM.
|
|
<DT id="95"><B>-no-rr</B>
|
|
|
|
<DD>
|
|
Do not use the Rock Ridge attributes from previous sessions.
|
|
This may help to avoid problems when
|
|
<B>genisoimage</B>
|
|
|
|
finds illegal Rock Ridge signatures on an old session.
|
|
<DT id="96"><B>-no-split-symlink-components</B>
|
|
|
|
<DD>
|
|
Don't split the symlink components, but begin a new Continuation Area (CE)
|
|
instead. This may waste some space, but the SunOS 4.1.4 cdrom driver
|
|
has a bug in reading split symlink components.
|
|
<DT id="97"><DD>
|
|
It is questionable whether this option is useful nowadays.
|
|
<DT id="98"><B>-no-split-symlink-fields</B>
|
|
|
|
<DD>
|
|
Don't split the symlink fields, but begin a new Continuation Area (CE)
|
|
instead. This may waste some space, but the SunOS 4.1.4 and
|
|
Solaris 2.5.1 cdrom driver have a bug in reading split symlink fields
|
|
(a `/' can be dropped).
|
|
<DT id="99"><DD>
|
|
It is questionable whether this option is useful nowadays.
|
|
<DT id="100"><B>-o</B><I> filename</I>
|
|
|
|
<DD>
|
|
Specify the output file for the the ISO9660 filesystem image.
|
|
This can be a disk file, a tape drive, or it can correspond directly
|
|
to the device name of the optical disc writer. If not specified, stdout is
|
|
used. Note that the output can also be a block device for a regular
|
|
disk partition, in which case the ISO9660 filesystem can be mounted
|
|
normally to verify that it was generated correctly.
|
|
<DT id="101"><B>-pad</B>
|
|
|
|
<DD>
|
|
Pad the end of the whole image by 150 sectors (300 kB). This option is
|
|
enabled by default. If used in combination with
|
|
<B>-B</B>,
|
|
|
|
padding is inserted between the ISO9660 partition and the boot
|
|
partitions, such that the first boot partition starts
|
|
on a sector number that is a multiple of 16.
|
|
<DT id="102"><DD>
|
|
The padding is needed as many operating systems (e.g. Linux)
|
|
implement read-ahead bugs in their filesystem I/O. These bugs result in read
|
|
errors on files that are located near the end of a track, particularly
|
|
if the disc is written in Track At Once mode, or where a CD audio track
|
|
follows the data track.
|
|
|
|
|
|
<DT id="103"><B>-no-pad</B>
|
|
|
|
<DD>
|
|
Do not pad the end by 150 sectors (300 kB) and do not make the the boot partitions
|
|
start on a multiple of 16 sectors.
|
|
<DT id="104"><B>-path-list</B><I> file</I>
|
|
|
|
<DD>
|
|
A file containing a list of
|
|
<I>pathspec</I>
|
|
|
|
directories and filenames to be added to the ISO9660 filesystem. This list
|
|
of pathspecs are processed after any that appear on the command line. If the
|
|
argument is
|
|
<I>-</I>,
|
|
|
|
the list is read from the standard input.
|
|
<DT id="105"><B>-P</B>
|
|
|
|
<DD>
|
|
Outdated option; use
|
|
<B>-publisher</B>
|
|
|
|
instead.
|
|
<DT id="106"><B>-publisher</B><I> publisher_id</I>
|
|
|
|
<DD>
|
|
Specifies a text string that will be written into the volume header.
|
|
This should describe the publisher of the CD-ROM, usually with a
|
|
mailing address and phone number. There is space for 128 characters.
|
|
Equivalent to
|
|
<B>PUBL</B>
|
|
|
|
in the
|
|
<I>.genisoimagerc</I>
|
|
|
|
file.
|
|
<DT id="107"><B>-p</B><I> preparer_id</I>
|
|
|
|
<DD>
|
|
Specifies a text string that will be written into the volume header.
|
|
This should describe the preparer of the CD-ROM, usually with a mailing
|
|
address and phone number. There is space for 128 characters.
|
|
Equivalent to
|
|
<B>PREP</B>
|
|
|
|
in the
|
|
<I>.genisoimagerc</I>
|
|
|
|
file.
|
|
<DT id="108"><B>-print-size</B>
|
|
|
|
<DD>
|
|
Print estimated filesystem size in multiples of the sector size (2048 bytes)
|
|
and exit. This option is needed for
|
|
Disk At Once mode and with some CD-R drives when piping directly into
|
|
<B>wodim</B>,
|
|
|
|
cases where
|
|
<B>wodim</B>
|
|
|
|
needs to know the size of the filesystem image in advance.
|
|
Old versions of
|
|
<B>mkisofs</B>
|
|
|
|
wrote this information (among other information) to
|
|
<I>stderr</I>.
|
|
|
|
As this turns out to be hard to parse, the number without any other information
|
|
is now printed on
|
|
<I>stdout</I>
|
|
|
|
too.
|
|
If you like to write a simple shell script, redirect
|
|
<I>stderr</I>
|
|
|
|
and catch the number from
|
|
<I>stdout</I>.
|
|
|
|
This may be done with:
|
|
<P>
|
|
<BR> cdblocks=` genisoimage -print-size -quiet ... `
|
|
<BR>
|
|
|
|
<BR> genisoimage ... | wodim ... tsize=${cdblocks}s -
|
|
<DT id="109"><B>-quiet</B>
|
|
|
|
<DD>
|
|
This makes
|
|
<B>genisoimage</B>
|
|
|
|
even less verbose. No progress output will be provided.
|
|
<DT id="110"><B>-R</B>
|
|
|
|
<DD>
|
|
Generate SUSP and RR records using the Rock Ridge protocol to further describe
|
|
the files on the ISO9660 filesystem.
|
|
<DT id="111"><B>-r</B>
|
|
|
|
<DD>
|
|
This is like the -R option, but file ownership and modes are set to
|
|
more useful values. The uid and gid are set to zero, because they are
|
|
usually only useful on the author's system, and not useful to the
|
|
client. All the file read bits are set true, so that files and
|
|
directories are globally readable on the client. If any execute bit is
|
|
set for a file, set all of the execute bits, so that executables are
|
|
globally executable on the client. If any search bit is set for a
|
|
directory, set all of the search bits, so that directories are globally
|
|
searchable on the client. All write bits are cleared, because the
|
|
filesystem will be mounted read-only in any case. If any of the special
|
|
mode bits are set, clear them, because file locks are not useful on a
|
|
read-only filesystem, and set-id bits are not desirable for uid 0 or
|
|
gid 0.
|
|
When used on Win32, the execute bit is set on
|
|
<I>all</I>
|
|
|
|
files. This is a result of the lack of file permissions on Win32 and the
|
|
Cygwin POSIX emulation layer. See also
|
|
<B>-uid</B>, <B>-gid</B>,
|
|
|
|
<B>-dir-mode</B>, <B>-file-mode</B>
|
|
|
|
and
|
|
<B>-new-dir-mode</B>.
|
|
|
|
<DT id="112"><B>-relaxed-filenames</B>
|
|
|
|
<DD>
|
|
Allows ISO9660 filenames to include all 7-bit ASCII characters except
|
|
lowercase letters.
|
|
<BR>
|
|
|
|
This violates the ISO9660 standard, but it happens to work on many systems.
|
|
Use with caution.
|
|
<DT id="113"><B>-root</B><I> dir</I>
|
|
|
|
<DD>
|
|
Moves all files and directories into
|
|
<I>dir</I>
|
|
|
|
in the image. This is essentially the
|
|
same as using
|
|
<B>-graft-points</B>
|
|
|
|
and adding
|
|
<I>dir</I>
|
|
|
|
in front of every pathspec, but is easier to use.
|
|
<I>dir</I>
|
|
|
|
may actually be several levels deep. It is
|
|
created with the same permissions as other graft points.
|
|
<DT id="114"><B>-old-root</B><I> dir</I>
|
|
|
|
<DD>
|
|
This option is necessary when writing a multisession
|
|
image and the previous (or even older) session was written with
|
|
<B>-root</B>
|
|
|
|
<I>dir</I>.
|
|
|
|
Using a directory name not found in the previous session
|
|
causes
|
|
<B>genisoimage</B>
|
|
|
|
to abort with an error.
|
|
Without this option,
|
|
<B>genisoimage</B>
|
|
|
|
would not be able to find unmodified files and would
|
|
be forced to write their data into the image once more.
|
|
<B>-root</B>
|
|
|
|
and
|
|
<B>-old-root</B>
|
|
|
|
are meant to be used together to do incremental backups.
|
|
The initial session would e.g. use:
|
|
<B>genisoimage -root backup_1</B>
|
|
|
|
<I>dirs</I>.
|
|
|
|
The next incremental backup with
|
|
<B>genisoimage -root backup_2 -old-root backup_1</B>
|
|
|
|
<I>dirs</I>
|
|
|
|
would take another snapshot of these directories. The first
|
|
snapshot would be found in
|
|
<B>backup_1</B>,
|
|
|
|
the second one in
|
|
<B>backup_2</B>,
|
|
|
|
but only modified or new files need to be written
|
|
into the second session.
|
|
Without these options, new files would be added and old ones would be
|
|
preserved. But old ones would be overwritten if the file was
|
|
modified. Recovering the files by copying the whole directory back
|
|
from CD would also restore files that were deleted
|
|
intentionally. Accessing several older versions of a file requires
|
|
support by the operating system to choose which sessions are to be
|
|
mounted.
|
|
<DT id="115"><B>-sort</B><I> sort_file</I>
|
|
|
|
<DD>
|
|
Sort file locations on the media. Sorting is controlled by a file that
|
|
contains pairs of filenames and sorting offset weighting.
|
|
If the weighting is higher, the file will be located closer to the
|
|
beginning of the media, if the weighting is lower, the file will be located
|
|
closer to the end of the media. There must be only one space or tabs
|
|
character between the filename and the
|
|
weight and the weight must be the last characters on a line. The filename
|
|
is taken to include all the characters up to, but not including the last
|
|
space or tab character on a line. This is to allow for space characters to
|
|
be in, or at the end of a filename.
|
|
This option does
|
|
<B>not</B>
|
|
|
|
sort the order of the filenames that appear
|
|
in the ISO9660 directory. It sorts the order in which the file data is
|
|
written to the CD image, which is useful in order to optimize the
|
|
data layout on a CD. See
|
|
<B>README.sort</B>
|
|
|
|
for more details.
|
|
<DT id="116"><B>-sparc-boot</B><I> img_sun4,img_sun4c,img_sun4m,img_sun4d,img_sun4e</I>
|
|
|
|
<DD>
|
|
See
|
|
<B>-B</B>
|
|
|
|
above.
|
|
<DT id="117"><B>-sparc-label</B><I> label</I>
|
|
|
|
<DD>
|
|
Set the Sun disk label name for the Sun disk label that is created with
|
|
<B>-sparc-boot</B>.
|
|
|
|
<DT id="118"><B>-split-output</B>
|
|
|
|
<DD>
|
|
Split the output image into several files of approximately 1 GB each.
|
|
This helps to create DVD-sized ISO9660 images on operating systems without
|
|
large file support.
|
|
<B>wodim</B>
|
|
|
|
will concatenate more than one file into a single track if writing to a DVD.
|
|
To make
|
|
<B>-split-output</B>
|
|
|
|
work,
|
|
<B>-o</B><I> filename</I>
|
|
|
|
must be specified. The resulting output images will be named:
|
|
<I>filename_00</I>, <I>filename_01</I>, <I>filename_02</I>....
|
|
|
|
<DT id="119"><B>-stream-media-size</B><I> #</I>
|
|
|
|
<DD>
|
|
Select streaming operation and set the media size to # sectors.
|
|
This allows you to pipe the output of the
|
|
<B><A HREF="/cgi-bin/man/man2html?1+tar">tar</A></B>(1)
|
|
|
|
program into
|
|
<B>genisoimage</B>
|
|
|
|
and to create an ISO9660 filesystem without the need of an intermediate
|
|
tar archive file.
|
|
If this option has been specified,
|
|
<B>genisoimage</B>
|
|
|
|
reads from
|
|
<I>stdin </I>
|
|
|
|
and creates a file with the name
|
|
<I>STREAM.IMG</I>.
|
|
|
|
The maximum size of the file (with padding) is 200 sectors less than the
|
|
specified media size. If
|
|
<B>-no-pad</B>
|
|
|
|
has been specified, the file size is 50 sectors less than the specified media size.
|
|
If the file is smaller,
|
|
<B>genisoimage</B>
|
|
|
|
will write padding. This may take awhile.
|
|
<DT id="120"><DD>
|
|
The option
|
|
<B>-stream-media-size</B>
|
|
|
|
creates simple ISO9660 filesystems only and may not used together with multisession
|
|
or hybrid filesystem options.
|
|
<DT id="121"><B>-stream-file-name</B><I> name</I>
|
|
|
|
<DD>
|
|
Reserved for future use.
|
|
<DT id="122"><B>-sunx86-boot</B><I> UFS_img,,,AUX1_img</I>
|
|
|
|
<DD>
|
|
Specifies a comma-separated list of filesystem images that are needed to make
|
|
a bootable CD for Solaris x86 systems.
|
|
<DT id="123"><DD>
|
|
Note that partition 1 is used for the ISO9660 image and that partition 2 is
|
|
the whole disk, so partition 1 and 2 may not be used by external partition data.
|
|
The first image file is mapped to partition 0.
|
|
There may be empty fields in the comma-separated list,
|
|
and list entries for partition 1 and 2 must be empty.
|
|
The maximum number of supported partitions is 8 (although the Solaris x86
|
|
partition table could support up to 16 partitions), so it is impossible
|
|
to specify more than 6 partition images.
|
|
This option is required to make a bootable CD for Solaris x86 systems.
|
|
<DT id="124"><DD>
|
|
If
|
|
<B>-sunx86-boot</B>
|
|
|
|
has been specified, the first sector of the resulting image will
|
|
contain a PC fdisk label with a Solaris type 0x82 fdisk partition that
|
|
starts at offset 512 and spans the whole CD.
|
|
In addition, for the Solaris type 0x82 fdisk partition, there is a
|
|
SVr4 disk label at offset 1024 in the first sector of the CD.
|
|
This disk label specifies slice 0 for the first (usually UFS type)
|
|
filesystem image that is used to boot the PC and slice 1 for
|
|
the ISO9660 image.
|
|
Slice 2 spans the whole CD slice 3 ... slice 7 may be used for additional
|
|
filesystem images that have been specified with this option.
|
|
<DT id="125"><DD>
|
|
A Solaris x86 boot CD uses a 1024 byte sized primary boot that uses the
|
|
<B>El-Torito no-emulation</B>
|
|
|
|
boot mode and a secondary generic boot that is in CD sectors 1..15.
|
|
For this reason, both
|
|
<B>-b </B><I>bootimage</I><B> -no-emul-boot</B>
|
|
|
|
and
|
|
<B>-G</B><I> genboot</I>
|
|
|
|
must be specified.
|
|
<DT id="126"><B>-sunx86-label</B><I> label</I>
|
|
|
|
<DD>
|
|
Set the SVr4 disk label name for the SVr4 disk label that is created with
|
|
<B>-sunx86-boot</B>.
|
|
|
|
<DT id="127"><B>-sysid</B><I> ID</I>
|
|
|
|
<DD>
|
|
Specifies the system ID. There is space for 32 characters.
|
|
Equivalent to
|
|
<B>SYSI</B>
|
|
|
|
in the
|
|
<I>.genisoimagerc</I>
|
|
|
|
file.
|
|
<DT id="128"><B>-T</B>
|
|
|
|
<DD>
|
|
Generate a file
|
|
<I>TRANS.TBL</I>
|
|
|
|
in each directory on the CD-ROM, which can be used
|
|
on non-Rock Ridge-capable systems to help establish the correct filenames.
|
|
There is also information present in the file that indicates the major and
|
|
minor numbers for block and character devices, and each symlink has the name of
|
|
the link file given.
|
|
<DT id="129"><B>-table-name</B><I> table_name</I>
|
|
|
|
<DD>
|
|
Alternative translation table filename (see above). Implies
|
|
<B>-T</B>.
|
|
|
|
If you are creating a multisession image you must use the same name
|
|
as in the previous session.
|
|
<DT id="130"><B>-ucs-level</B><I> level</I>
|
|
|
|
<DD>
|
|
Set Unicode conformance level in the Joliet SVD. The default level is 3.
|
|
It may be set to 1..3 using this option.
|
|
<DT id="131"><B>-udf</B>
|
|
|
|
<DD>
|
|
Include UDF filesystem support in the generated filesystem image. UDF
|
|
support is currently in alpha status and for this reason, it is not
|
|
possible to create UDF-only images. UDF data structures are currently
|
|
coupled to the Joliet structures, so there are many pitfalls with the
|
|
current implementation. There is no UID/GID support, there is no POSIX
|
|
permission support, there is no support for symlinks. Note that UDF
|
|
wastes the space from sector ~20 to sector 256 at the beginning of the
|
|
disc in addition to the space needed for real UDF data structures.
|
|
<DT id="132"><B>-uid</B><I> uid</I>
|
|
|
|
<DD>
|
|
Overrides the uid read from the source files to the value of
|
|
<I>uid</I>.
|
|
|
|
Specifying this option automatically enables Rock Ridge extensions.
|
|
<DT id="133"><B>-use-fileversion</B>
|
|
|
|
<DD>
|
|
The option
|
|
<B>-use-fileversion</B>
|
|
|
|
allows
|
|
<B>genisoimage</B>
|
|
|
|
to use file version numbers from the filesystem.
|
|
If the option is not specified,
|
|
<B>genisoimage</B>
|
|
|
|
creates a version number of 1 for all files.
|
|
File versions are strings in the range
|
|
<I>;1</I>
|
|
|
|
to
|
|
<I>;32767</I>
|
|
|
|
This option is the default on VMS.
|
|
<DT id="134"><B>-U</B>
|
|
|
|
<DD>
|
|
Allows "untranslated" filenames, completely violating the ISO9660 standards
|
|
described above. Enables the following flags:
|
|
<B>-d -l -N -allow-leading-dots -relaxed-filenames</B>
|
|
|
|
<B>-allow-lowercase -allow-multidot -no-iso-translate</B>.
|
|
|
|
Allows more than one `.' character in the filename, as well as
|
|
mixed-case filenames. This is useful on HP-UX, where the built-in
|
|
<I>cdfs</I>
|
|
|
|
filesystem does not recognize any extensions. Use with extreme caution.
|
|
<DT id="135"><B>-no-iso-translate</B>
|
|
|
|
<DD>
|
|
Do not translate the characters `#' and `~' which are invalid for ISO9660 filenames.
|
|
Although invalid, these characters are often used by Microsoft systems.
|
|
<BR>
|
|
|
|
This violates the ISO9660 standard, but it happens to work on many systems.
|
|
Use with caution.
|
|
<DT id="136"><B>-V</B><I> volid</I>
|
|
|
|
<DD>
|
|
Specifies the volume ID (volume name or label) to be written into the
|
|
master block. There is space for 32 characters. Equivalent to
|
|
<B>VOLI</B>
|
|
|
|
in the
|
|
<I>.genisoimagerc</I>
|
|
|
|
file. The volume ID is used as the mount point by the Solaris volume
|
|
manager and as a label assigned to a disc on various other platforms
|
|
such as Windows and Apple Mac OS.
|
|
<DT id="137"><B>-volset</B><I> ID</I>
|
|
|
|
<DD>
|
|
Specifies the volume set ID. There is space for 128 characters.
|
|
Equivalent to
|
|
<B>VOLS</B>
|
|
|
|
in the
|
|
<I>.genisoimagerc</I>
|
|
|
|
file.
|
|
<DT id="138"><B>-volset-size</B><I> #</I>
|
|
|
|
<DD>
|
|
Sets the volume set size to #.
|
|
The volume set size is the number of CDs that are in a CD volume set.
|
|
A volume set is a collection of one or more volumes, on which a set of
|
|
files is recorded.
|
|
<DT id="139"><DD>
|
|
Volume Sets are not intended to be used to create a set numbered CDs
|
|
that are part of e.g. a Operation System installation set of CDs.
|
|
Volume Sets are rather used to record a big directory tree that would not
|
|
fit on a single volume.
|
|
Each volume of a Volume Set contains a description of all the directories
|
|
and files that are recorded on the volumes where the sequence numbers
|
|
are less than, or equal to, the assigned Volume Set Size of the current
|
|
volume.
|
|
<DT id="140"><DD>
|
|
<B>genisoimage</B>
|
|
|
|
currently does not support a
|
|
<B>-volset-size</B>
|
|
|
|
that is larger than 1.
|
|
<DT id="141"><DD>
|
|
The option
|
|
<B>-volset-size</B>
|
|
|
|
must be specified before
|
|
<B>-volset-seqno</B>
|
|
|
|
on each command line.
|
|
<DT id="142"><B>-volset-seqno</B><I> #</I>
|
|
|
|
<DD>
|
|
Sets the volume set sequence number to #.
|
|
The volume set sequence number is the index number of the current
|
|
CD in a CD set.
|
|
The option
|
|
<B>-volset-size</B>
|
|
|
|
must be specified before
|
|
<B>-volset-seqno</B>
|
|
|
|
on each command line.
|
|
<DT id="143"><B>-v</B>
|
|
|
|
<DD>
|
|
Verbose execution. If given twice on the command line, extra debug information
|
|
will be printed.
|
|
<DT id="144"><B>-x</B><I> glob</I>
|
|
|
|
<DD>
|
|
Identical to
|
|
<B>-m</B>
|
|
|
|
<I>glob</I>.
|
|
|
|
<DT id="145"><B>-z</B>
|
|
|
|
<DD>
|
|
Generate special
|
|
<I>RRIP</I>
|
|
|
|
records for transparently compressed files.
|
|
This is only of use and interest for hosts that support transparent
|
|
decompression, such as Linux 2.4.14 or later. You must specify
|
|
<B>-R</B> or <B>-r</B>
|
|
|
|
to enable Rock Ridge, and generate compressed files using the
|
|
<B>mkzftree</B>
|
|
|
|
utility before running
|
|
<B>genisoimage</B>.
|
|
|
|
Note that transparent compression is a nonstandard Rock Ridge extension.
|
|
The resulting disks are only transparently readable if used on Linux.
|
|
On other operating systems you will need to call
|
|
<B>mkzftree</B>
|
|
|
|
by hand to decompress the files.
|
|
|
|
</DL>
|
|
<A NAME="lbAF"> </A>
|
|
<H2>HFS OPTIONS</H2>
|
|
|
|
<DL COMPACT>
|
|
<DT id="146"><B>-hfs</B>
|
|
|
|
<DD>
|
|
Create an ISO9660/HFS hybrid CD. This option should be used in conjunction
|
|
with the
|
|
<B>-map</B>,
|
|
|
|
<B>-magic</B>
|
|
|
|
and/or the various
|
|
<I>double dash</I>
|
|
|
|
options given below.
|
|
<DT id="147"><B>-apple</B>
|
|
|
|
<DD>
|
|
Create an ISO9660 CD with Apple's extensions. Similar to
|
|
<B>-hfs</B>,
|
|
|
|
except that the Apple Extensions to ISO9660 are added instead of
|
|
creating an HFS hybrid volume.
|
|
Former
|
|
<B>genisoimage</B>
|
|
|
|
versions did include Rock Ridge attributes by default if
|
|
<B>-apple</B>
|
|
|
|
was specified. This versions of
|
|
<B>genisoimage</B>
|
|
|
|
does not do this anymore. If you like to have Rock Ridge attributes,
|
|
you need to specify this separately.
|
|
<DT id="148"><B>-map</B><I> mapping_file</I>
|
|
|
|
<DD>
|
|
Use the
|
|
<I>mapping_file</I>
|
|
|
|
to set the CREATOR and TYPE information for a file based on the
|
|
filename's extension. A filename is
|
|
mapped only if it is not one of the know Apple/Unix file formats. See the
|
|
<B>HFS CREATOR/TYPE</B>
|
|
|
|
section below.
|
|
<DT id="149"><B>-magic</B><I> magic_file</I>
|
|
|
|
<DD>
|
|
The CREATOR and TYPE information is set by using a file's
|
|
<I>magic number</I>
|
|
|
|
(usually the first few bytes of a file). The
|
|
<I>magic_file</I>
|
|
|
|
is only used if a file is not one of the known Apple/Unix file formats, or
|
|
the filename extension has not been mapped using
|
|
<B>-map</B>.
|
|
|
|
See the
|
|
<B>HFS CREATOR/TYPE</B>
|
|
|
|
section below for more details.
|
|
<DT id="150"><B>-hfs-creator</B><I> creator</I>
|
|
|
|
<DD>
|
|
Set the default CREATOR for all files. Must be exactly 4 characters. See the
|
|
<B>HFS CREATOR/TYPE</B>
|
|
|
|
section below for more details.
|
|
<DT id="151"><B>-hfs-type</B><I> type</I>
|
|
|
|
<DD>
|
|
Set the default TYPE for all files. Must be exactly 4 characters. See the
|
|
<B>HFS CREATOR/TYPE</B>
|
|
|
|
section below for more details.
|
|
<DT id="152"><B>-probe</B>
|
|
|
|
<DD>
|
|
Search the contents of files for all the known Apple/Unix file formats.
|
|
See the
|
|
<B>HFS MACINTOSH FILE FORMATS</B>
|
|
|
|
section below for more about these formats.
|
|
However, the only way to check for
|
|
<I>MacBinary</I>
|
|
|
|
and
|
|
<I>AppleSingle</I>
|
|
|
|
files is to open and read them, so this option may
|
|
increase processing time. It is better to use one or more
|
|
<I>double dash</I>
|
|
|
|
options given below if the Apple/Unix formats in use are known.
|
|
<DT id="153"><B>-no-desktop</B>
|
|
|
|
<DD>
|
|
Do not create (empty) Desktop files. New HFS Desktop files will be created
|
|
when the CD is used on a Macintosh (and stored in the System Folder).
|
|
By default, empty Desktop files are added to the HFS volume.
|
|
<DT id="154"><B>-mac-name</B>
|
|
|
|
<DD>
|
|
Use the HFS filename as the starting point for the ISO9660, Joliet and
|
|
Rock Ridge filenames. See the
|
|
<B>HFS MACINTOSH FILENAMES</B>
|
|
|
|
section below for more information.
|
|
<DT id="155"><B>-boot-hfs-file</B><I> driver_file</I>
|
|
|
|
<DD>
|
|
Installs the
|
|
<I>driver_file</I>
|
|
|
|
that
|
|
<I>may</I>
|
|
|
|
make the CD bootable on a Macintosh. See the
|
|
<B>HFS BOOT DRIVER</B>
|
|
|
|
section below. (Alpha).
|
|
<DT id="156"><B>-part</B>
|
|
|
|
<DD>
|
|
Generate an HFS partition table. By default, no partition table is generated,
|
|
but some older Macintosh CD-ROM drivers need an HFS partition table on the
|
|
CD-ROM to be able to recognize a hybrid CD-ROM.
|
|
<DT id="157"><B>-auto</B><I> AutoStart_file</I>
|
|
|
|
<DD>
|
|
Make the HFS CD use the QuickTime 2.0 Autostart feature to launch an
|
|
application or document. The given filename must be the name of a document or
|
|
application located at the top level of the CD. The filename must be less
|
|
than 12 characters. (Alpha).
|
|
<DT id="158"><B>-cluster-size</B><I> size</I>
|
|
|
|
<DD>
|
|
Set the size in bytes of the cluster or allocation units of PC Exchange
|
|
files. Implies
|
|
<B>--exchange</B>.
|
|
|
|
See the
|
|
<B>HFS MACINTOSH FILE FORMATS</B>
|
|
|
|
section below.
|
|
<DT id="159"><B>-hide-hfs</B><I> glob</I>
|
|
|
|
<DD>
|
|
Hide
|
|
<I>glob</I>,
|
|
|
|
a shell wildcard pattern, from the HFS volume. The file or directory
|
|
will still exist in the ISO9660 and/or Joliet directory.
|
|
<I>glob</I>
|
|
|
|
may match any part of the filename. Multiple globs may be excluded.
|
|
Example:
|
|
<P>
|
|
<BR> genisoimage -o rom -hfs -hide-hfs '*.o' -hide-hfs foobar
|
|
<P>
|
|
would exclude all files ending in `.o' or called
|
|
<I>foobar</I>
|
|
|
|
from the HFS volume. Note that if you had a directory called
|
|
<I>foobar</I>,
|
|
|
|
it too (and of course all its descendants) would be excluded. The
|
|
<I>glob</I>
|
|
|
|
can also be a path name relative to the source directories given on the
|
|
command line. Example:
|
|
<P>
|
|
<BR> genisoimage -o rom -hfs -hide-hfs src/html src
|
|
<P>
|
|
would exclude just the file or directory called
|
|
<I>html</I>
|
|
|
|
from the
|
|
<I>src</I>
|
|
|
|
directory. Any other file or directory called
|
|
<I>html</I>
|
|
|
|
in the tree will not be excluded. Should be used with
|
|
<B>-hide</B>
|
|
|
|
and/or
|
|
<B>-hide-joliet</B>.
|
|
|
|
In order to match a directory name, make sure the pattern does not
|
|
include a trailing `/' character. See
|
|
<I>README.hide</I>
|
|
|
|
for more details.
|
|
<DT id="160"><B>-hide-hfs-list</B><I> file</I>
|
|
|
|
<DD>
|
|
Specify a file containing a list of wildcard patterns to be hidden as in
|
|
<B>-hide-hfs</B>.
|
|
|
|
<DT id="161"><B>-hfs-volid</B><I> hfs_volid</I>
|
|
|
|
<DD>
|
|
Volume name for the HFS partition. This is the name that is
|
|
assigned to the disc on a Macintosh and replaces the
|
|
<I>volid</I>
|
|
|
|
used with
|
|
<B>-V</B>.
|
|
|
|
<DT id="162"><B>-icon-position</B>
|
|
|
|
<DD>
|
|
Use the icon position information, if it exists, from the Apple/Unix file.
|
|
The icons will appear in the same position as they would on a Macintosh
|
|
desktop. Folder location and size on screen, its scroll positions, folder
|
|
View (view as Icons, Small Icons, etc.) are also preserved.
|
|
|
|
(Alpha).
|
|
<DT id="163"><B>-root-info</B><I> file</I>
|
|
|
|
<DD>
|
|
Set the location, size on screen, scroll positions, folder View etc. for the
|
|
root folder of an HFS volume. See
|
|
<I>README.rootinfo</I>
|
|
|
|
for more information. (Alpha)
|
|
<DT id="164"><B>-prep-boot</B><I> file</I>
|
|
|
|
<DD>
|
|
PReP boot image file. Up to 4 are allowed. See
|
|
<I>README.prep_boot</I>
|
|
|
|
for more information. (Alpha)
|
|
<DT id="165"><B>-chrp-boot</B>
|
|
|
|
<DD>
|
|
Add CHRP boot header.
|
|
<DT id="166"><B>-input-hfs-charset</B><I> charset</I>
|
|
|
|
<DD>
|
|
Input charset that defines the characters used in HFS filenames when
|
|
used with
|
|
<B>-mac-name</B>.
|
|
|
|
The default charset is
|
|
<I>cp10000</I>
|
|
|
|
(Mac Roman). See the
|
|
<B>CHARACTER SETS</B>
|
|
|
|
and
|
|
<B>HFS MACINTOSH FILENAMES</B>
|
|
|
|
sections below for more details.
|
|
<DT id="167"><B>-output-hfs-charset</B><I> charset</I>
|
|
|
|
<DD>
|
|
Output charset that defines the characters that will be used in the HFS
|
|
filenames. Defaults to the input charset. See the
|
|
<B>CHARACTER SETS</B>
|
|
|
|
section below for more details.
|
|
<DT id="168"><B>-hfs-unlock</B>
|
|
|
|
<DD>
|
|
By default,
|
|
<B>genisoimage</B>
|
|
|
|
will create an HFS volume that is locked.
|
|
This option leaves the volume unlocked so that other applications (e.g.
|
|
<B>hfsutils</B>)
|
|
|
|
can modify the volume. See the
|
|
<B>HFS PROBLEMS/LIMITATIONS</B>
|
|
|
|
section below for warnings about using this option.
|
|
<DT id="169"><B>-hfs-bless</B><I> folder_name</I>
|
|
|
|
<DD>
|
|
"Bless" the given directory (folder). This is usually the
|
|
<I>System Folder</I>
|
|
|
|
and is used in creating HFS bootable CDs. The name of the directory must
|
|
be the whole path name as
|
|
<B>genisoimage</B>
|
|
|
|
sees it. E.g., if the given pathspec is
|
|
<I>./cddata</I>
|
|
|
|
and the required folder is called
|
|
<I>System Folder</I>,
|
|
|
|
the whole path name is
|
|
<I>"/cddata/System Folder"</I>
|
|
|
|
(remember to use quotes if the name contains spaces).
|
|
<DT id="170"><B>-hfs-parms</B><I> parameters</I>
|
|
|
|
<DD>
|
|
Override certain parameters used to create the HFS filesystem. Unlikely to
|
|
be used in normal circumstances. See the
|
|
<I>libhfs_iso/hybrid.h</I>
|
|
|
|
source file for details.
|
|
<DT id="171"><B>--cap</B>
|
|
|
|
<DD>
|
|
Look for AUFS CAP Macintosh files. Search for CAP Apple/Unix file formats
|
|
only. Searching for the other possible Apple/Unix file formats is disabled,
|
|
unless other
|
|
<I>double dash</I>
|
|
|
|
options are given.
|
|
<DT id="172"><B>--netatalk</B>
|
|
|
|
<DD>
|
|
Look for NETATALK Macintosh files
|
|
<DT id="173"><B>--double</B>
|
|
|
|
<DD>
|
|
Look for AppleDouble Macintosh files
|
|
<DT id="174"><B>--ethershare</B>
|
|
|
|
<DD>
|
|
Look for Helios EtherShare Macintosh files
|
|
<DT id="175"><B>--ushare</B>
|
|
|
|
<DD>
|
|
Look for IPT UShare Macintosh files
|
|
<DT id="176"><B>--exchange</B>
|
|
|
|
<DD>
|
|
Look for PC Exchange Macintosh files
|
|
<DT id="177"><B>--sgi</B>
|
|
|
|
<DD>
|
|
Look for SGI Macintosh files
|
|
<DT id="178"><B>--xinet</B>
|
|
|
|
<DD>
|
|
Look for XINET Macintosh files
|
|
<DT id="179"><B>--macbin</B>
|
|
|
|
<DD>
|
|
Look for MacBinary Macintosh files
|
|
<DT id="180"><B>--single</B>
|
|
|
|
<DD>
|
|
Look for AppleSingle Macintosh files
|
|
<DT id="181"><B>--dave</B>
|
|
|
|
<DD>
|
|
Look for Thursby Software Systems DAVE Macintosh files
|
|
<DT id="182"><B>--sfm</B>
|
|
|
|
<DD>
|
|
Look for Microsoft's Services for Macintosh files (NT only) (Alpha)
|
|
<DT id="183"><B>--osx-double</B>
|
|
|
|
<DD>
|
|
Look for Mac OS X AppleDouble Macintosh files
|
|
<DT id="184"><B>--osx-hfs</B>
|
|
|
|
<DD>
|
|
Look for Mac OS X HFS Macintosh files
|
|
|
|
</DL>
|
|
<A NAME="lbAG"> </A>
|
|
<H2>CHARACTER SETS</H2>
|
|
|
|
<B>genisoimage</B>
|
|
|
|
processes filenames in a POSIX-compliant way as strings of 8-bit characters.
|
|
To represent all codings for all languages, 8-bit characters are not
|
|
sufficient. Unicode or ISO-10646
|
|
define character codings that need at least 21 bits to represent all
|
|
known languages. They may be represented with
|
|
<I>UTF-32</I>, <I>UTF-16</I> or <I>UTF-8</I>
|
|
|
|
coding. UTF-32 uses a plain 32-bit coding but seems to be uncommon.
|
|
UTF-16 is used by Microsoft with Win32 with the disadvantage that
|
|
16-bit characters are not compliant with the POSIX filesystem
|
|
interface.
|
|
<P>
|
|
|
|
Modern Unix operating systems may use UTF-8 coding for filenames.
|
|
Each 32-bit character is represented by one or more 8-bit characters.
|
|
If a character is coded in
|
|
<I>ISO-8859-1</I>
|
|
|
|
(used in Central Europe and North America) is maps 1:1 to a
|
|
UTF-32 or UTF-16 coded Unicode character.
|
|
If a character is coded in
|
|
<I>7-Bit ASCII</I>
|
|
|
|
(used in USA and other countries with limited character set)
|
|
is maps 1:1 to a UTF-32, UTF-16 or UTF-8 coded Unicode character.
|
|
Character codes that cannot be represented as a single byte in UTF-8
|
|
(if the value is > 0x7F) use escape sequences that map to more than
|
|
one 8-bit character.
|
|
<P>
|
|
|
|
If all operating systems used UTF-8,
|
|
<B>genisoimage</B>
|
|
|
|
would not need to recode characters in filenames.
|
|
Unfortunately, Apple uses completely nonstandard codings and Microsoft
|
|
uses a Unicode coding that is not compatible with the POSIX filename
|
|
interface.
|
|
<P>
|
|
|
|
For all non-UTF-8-coded operating systems, the actual character
|
|
that each byte represents depends on the
|
|
<I>character set</I>
|
|
|
|
or
|
|
<I>codepage</I>
|
|
|
|
(the name used by Microsoft)
|
|
used by the local operating system --- the characters in a character
|
|
set will reflect the region or natural language set by the user.
|
|
<P>
|
|
|
|
Usually character codes 0x00-0x1f are control characters, codes 0x20-0x7f
|
|
are the 7-bit ASCII characters and (on PCs and Macs) 0x80-0xff are used
|
|
for other characters.
|
|
<P>
|
|
|
|
As there are a lot more than 256 characters/symbols in use, only a small
|
|
subset are represented in a character set. Therefore the same character code
|
|
may represent a different character in different character sets. So a filename
|
|
generated, say in central Europe, may not display the same character
|
|
when viewed on a machine in, say eastern Europe.
|
|
<P>
|
|
|
|
To make matters more complicated, different operating systems use
|
|
different character sets for the region or language. For example, the
|
|
character code for `é' (small e with acute accent)
|
|
may be character code 0x82 on a PC,
|
|
code 0x8e on a Macintosh, code 0xe9 on a Unix system in western Europe,
|
|
and code 0x000e9 in Unicode.
|
|
<P>
|
|
|
|
As long as not all operating systems and applications use the same
|
|
character set as the basis for filenames, it may be
|
|
necessary to specify which character set your filenames use in and which
|
|
character set the filenames should appear on the CD.
|
|
<P>
|
|
|
|
There are four options to specify the character sets you want to use:
|
|
<DL COMPACT>
|
|
<DT id="185"><B>-input-charset</B>
|
|
|
|
<DD>
|
|
Defines the local character set you are using on your host machine.
|
|
Any character set conversions that take place will use this character
|
|
set as the starting point. The default input character sets are
|
|
<I>cp437</I>
|
|
|
|
on MS-DOS-based systems and
|
|
<I>iso8859-1</I>
|
|
|
|
on all other systems. If
|
|
<B>-J</B>
|
|
|
|
is given, the Unicode equivalents of the input character set
|
|
will be used in the Joliet directory.
|
|
<B>-jcharset</B>
|
|
|
|
is the same as
|
|
<B>-input-charset -J</B>.
|
|
|
|
<DT id="186"><B>-output-charset</B>
|
|
|
|
<DD>
|
|
Defines the character set that will be used with for the Rock Ridge names
|
|
on the CD. Defaults to the input character set.
|
|
<DT id="187"><B>-input-hfs-charset</B>
|
|
|
|
<DD>
|
|
Defines the HFS character set used for HFS filenames decoded from
|
|
any of the various Apple/Unix file formats. Only useful when used with
|
|
<B>-mac-name</B>.
|
|
|
|
See the
|
|
<B>HFS MACINTOSH FILENAMES</B>
|
|
|
|
for more information. Defaults to
|
|
<I>cp10000</I>
|
|
|
|
(Mac Roman).
|
|
<DT id="188"><B>-output-hfs-charset</B>
|
|
|
|
<DD>
|
|
Defines the HFS character set used to create HFS filenames from the input
|
|
character set in use. In most cases this will be from the character set
|
|
given with
|
|
<B>-input-charset</B>.
|
|
|
|
Defaults to the input HFS character set.
|
|
</DL>
|
|
<P>
|
|
|
|
There are a number of character sets built in to
|
|
<B>genisoimage</B>.
|
|
|
|
To get a listing, use
|
|
<B>-input-charset help</B>.
|
|
|
|
This list doesn't include the charset derived from the current locale,
|
|
if
|
|
<B>genisoimage</B>
|
|
|
|
is built with
|
|
<I>iconv</I>
|
|
|
|
support.
|
|
<P>
|
|
|
|
Additional character sets can be read from file for any of the character
|
|
set options by giving a filename as the argument to the options. The given
|
|
file will only be read if its name does not match one of the built-in
|
|
character sets.
|
|
<P>
|
|
|
|
The format of the character set files is the same as the mapping files
|
|
available from
|
|
<I><A HREF="http://www.unicode.org/Public/MAPPINGS">http://www.unicode.org/Public/MAPPINGS</A></I>.
|
|
|
|
This format is:
|
|
<DL COMPACT>
|
|
<DT id="189"><DD>
|
|
Column #1 is the input byte code (in hex as 0xXX)
|
|
<BR>
|
|
|
|
Column #2 is the Unicode (in hex as 0xXXXX)
|
|
<BR>
|
|
|
|
The rest of the line is ignored.
|
|
</DL>
|
|
<P>
|
|
|
|
Any blank line, line without two (or more) columns in the above format
|
|
or comments lines (starting with the # character) are ignored without any
|
|
warnings. Any missing input code is mapped to Unicode character 0x0000.
|
|
<P>
|
|
|
|
Note that, while UTF-8 is supported, other Unicode encodings such as
|
|
UCS-2/UTF-16 and UCS-4/UTF-32 are not, as POSIX operating systems
|
|
cannot handle them natively.
|
|
<P>
|
|
|
|
A 1:1 character set mapping can be defined by using the keyword
|
|
<I>default</I>
|
|
|
|
as the argument to any of the character set options. This is the behaviour
|
|
of old versions of
|
|
<B>mkisofs</B>.
|
|
|
|
<P>
|
|
|
|
The ISO9660 filenames generated from the input filenames are not converted
|
|
from the input character set. The ISO9660 character set is a very limited
|
|
subset of the ASCII characters, so any conversion would be pointless.
|
|
<P>
|
|
|
|
Any character that
|
|
<B>genisoimage</B>
|
|
|
|
cannot convert will be replaced with a `_' character.
|
|
|
|
<A NAME="lbAH"> </A>
|
|
<H2>HFS CREATOR/TYPE</H2>
|
|
|
|
A Macintosh file has two properties associated with it which define
|
|
which application created the file, the
|
|
<I>CREATOR</I>
|
|
|
|
and what data the file contains, the
|
|
<I>TYPE</I>.
|
|
|
|
Both are (exactly) 4 letter strings. Usually this
|
|
allows a Macintosh user to double-click on a file and launch the correct
|
|
application etc. The CREATOR and TYPE of a particular file can be found by
|
|
using something like ResEdit (or similar) on a Macintosh.
|
|
<P>
|
|
|
|
The CREATOR and TYPE information is stored in all the various Apple/Unix
|
|
encoded files.
|
|
For other files it is possible to base the CREATOR and TYPE on the
|
|
filename's extension using a
|
|
<I>mapping</I>
|
|
|
|
file (with
|
|
<B>-map</B>)
|
|
|
|
and/or using the
|
|
<I>magic number</I>
|
|
|
|
(usually a
|
|
<I>signature</I>
|
|
|
|
in the first few bytes) of a file (with
|
|
<B>-magic</B>).
|
|
|
|
If both these options are given, their order on the command
|
|
line is significant. If
|
|
<B>-map</B>
|
|
|
|
is given first, a filename extension match is attempted
|
|
before a magic number match. However, if
|
|
<B>-magic</B>
|
|
|
|
is given first, a magic number match is attempted before a
|
|
filename extension match.
|
|
<P>
|
|
|
|
If a mapping or magic file is not used, or no match is found, the default
|
|
CREATOR and TYPE for all regular files can be set by using entries in the
|
|
<I>.genisoimagerc</I>
|
|
|
|
file or using
|
|
<B>-hfs-creator</B>
|
|
|
|
and/or
|
|
<B>-hfs-type</B>,
|
|
|
|
otherwise the default CREATOR and TYPE are
|
|
<I>Unix</I> and <I>TEXT</I>.
|
|
|
|
<P>
|
|
|
|
The format of the
|
|
<I>mapping</I>
|
|
|
|
file is the same
|
|
<I>afpfile</I>
|
|
|
|
format as used by
|
|
<B>aufs</B>.
|
|
|
|
This file has five columns for the
|
|
<I>extension</I>,
|
|
|
|
<I>file translation</I>,
|
|
|
|
<I>CREATOR</I>,
|
|
|
|
<I>TYPE</I> and
|
|
|
|
<I>Comment</I>.
|
|
|
|
Lines starting with the `#' character are
|
|
comment lines and are ignored. An example file would be like:
|
|
<P>
|
|
|
|
<TABLE>
|
|
<TR VALIGN=top><TD COLSPAN=5># Example filename mapping file<BR></TD></TR>
|
|
<TR VALIGN=top><TD COLSPAN=5>#<BR></TD></TR>
|
|
<TR VALIGN=top><TD># EXTN</TD><TD>XLate</TD><TD>CREATOR</TD><TD>TYPE</TD><TD>Comment<BR></TD></TR>
|
|
<TR VALIGN=top><TD>.tif</TD><TD>Raw</TD><TD>'8BIM'</TD><TD>'TIFF'</TD><TD>"Photoshop TIFF image"<BR></TD></TR>
|
|
<TR VALIGN=top><TD>.hqx</TD><TD>Ascii</TD><TD>'BnHq'</TD><TD>'TEXT'</TD><TD>"BinHex file"<BR></TD></TR>
|
|
<TR VALIGN=top><TD>.doc</TD><TD>Raw</TD><TD>'MSWD'</TD><TD>'WDBN'</TD><TD>"Word file"<BR></TD></TR>
|
|
<TR VALIGN=top><TD>.mov</TD><TD>Raw</TD><TD>'TVOD'</TD><TD>'MooV'</TD><TD>"QuickTime Movie"<BR></TD></TR>
|
|
<TR VALIGN=top><TD>*</TD><TD>Ascii</TD><TD>'ttxt'</TD><TD>'TEXT'</TD><TD>"Text file"<BR></TD></TR>
|
|
</TABLE>
|
|
|
|
<P>
|
|
|
|
Where:
|
|
<DL COMPACT>
|
|
<DT id="190"><DD>
|
|
The first column
|
|
<I>EXTN</I>
|
|
|
|
defines the Unix filename extension to be
|
|
mapped. The default mapping for any filename extension that doesn't
|
|
match is defined with the `*' character.
|
|
<DT id="191"><DD>
|
|
The
|
|
<I>Xlate</I>
|
|
|
|
column defines the type of text translation between the Unix and
|
|
Macintosh file it is ignored by
|
|
<B>genisoimage</B>,
|
|
|
|
but is kept to be compatible with
|
|
<B><A HREF="/cgi-bin/man/man2html?1+aufs">aufs</A></B>(1).
|
|
|
|
Although
|
|
<B>genisoimage</B>
|
|
|
|
does not alter the contents of a file, if a binary file has its TYPE
|
|
set as
|
|
<I>TEXT</I>, it <I>may</I>
|
|
|
|
be read incorrectly on a Macintosh. Therefore a better choice for the
|
|
default TYPE may be
|
|
<I>????</I>.
|
|
|
|
<DT id="192"><DD>
|
|
The
|
|
<I>CREATOR</I>
|
|
|
|
and
|
|
<I>TYPE</I>
|
|
|
|
keywords must be 4 characters long and enclosed in single quotes.
|
|
<DT id="193"><DD>
|
|
The comment field is enclosed in double quotes --- it is ignored by
|
|
<B>genisoimage</B>,
|
|
|
|
but is kept to be compatible with
|
|
<B>aufs</B>.
|
|
|
|
</DL>
|
|
<P>
|
|
|
|
The format of the
|
|
<I>magic</I>
|
|
|
|
file is almost identical to the
|
|
<B><A HREF="/cgi-bin/man/man2html?5+magic">magic</A></B>(5)
|
|
|
|
file used by the
|
|
<B><A HREF="/cgi-bin/man/man2html?1+file">file</A></B>(1)
|
|
|
|
command.
|
|
<P>
|
|
|
|
This file has four tab-separated columns for the
|
|
<I>byte offset</I>,
|
|
|
|
<I>type</I>,
|
|
|
|
<I>test</I>
|
|
|
|
and
|
|
<I>message</I>.
|
|
|
|
Lines starting with the `#' character are
|
|
comment lines and are ignored. An example file would be like:
|
|
<P>
|
|
|
|
<TABLE>
|
|
<TR VALIGN=top><TD COLSPAN=4># Example magic file<BR></TD></TR>
|
|
<TR VALIGN=top><TD COLSPAN=4>#<BR></TD></TR>
|
|
<TR VALIGN=top><TD># off</TD><TD>type</TD><TD>test</TD><TD>message<BR></TD></TR>
|
|
<TR VALIGN=top><TD>0</TD><TD>string</TD><TD>GIF8</TD><TD>8BIM GIFf GIF image<BR></TD></TR>
|
|
<TR VALIGN=top><TD>0</TD><TD>beshort</TD><TD>0xffd8</TD><TD>8BIM JPEG image data<BR></TD></TR>
|
|
<TR VALIGN=top><TD>0</TD><TD>string</TD><TD>SIT!</TD><TD>SIT! SIT! StuffIt Archive<BR></TD></TR>
|
|
<TR VALIGN=top><TD>0</TD><TD>string</TD><TD>\037\235</TD><TD>LZIV ZIVU standard Unix compress<BR></TD></TR>
|
|
<TR VALIGN=top><TD>0</TD><TD>string</TD><TD>\037\213</TD><TD>GNUz ZIVU gzip compressed data<BR></TD></TR>
|
|
<TR VALIGN=top><TD>0</TD><TD>string</TD><TD>%!</TD><TD>ASPS TEXT Postscript<BR></TD></TR>
|
|
<TR VALIGN=top><TD>0</TD><TD>string</TD><TD>\004%!</TD><TD>ASPS TEXT PC Postscript with a ^D to start<BR></TD></TR>
|
|
<TR VALIGN=top><TD>4</TD><TD>string</TD><TD>moov</TD><TD>txtt MooV QuickTime movie file (moov)<BR></TD></TR>
|
|
<TR VALIGN=top><TD>4</TD><TD>string</TD><TD>mdat</TD><TD>txtt MooV QuickTime movie file (mdat)<BR></TD></TR>
|
|
</TABLE>
|
|
|
|
<P>
|
|
|
|
The format of the file is described in
|
|
<B><A HREF="/cgi-bin/man/man2html?5+magic">magic</A></B>(5).
|
|
|
|
The only difference here is that for each entry in the magic file, the
|
|
<I>message</I>
|
|
|
|
for the initial offset must be be 4 characters for the CREATOR followed
|
|
by 4 characters for the TYPE --- white space is
|
|
optional between them. Any other characters on this line are ignored.
|
|
Continuation lines (starting with a `>') are also ignored, i.e., only
|
|
the initial offset lines are used.
|
|
<P>
|
|
|
|
Using
|
|
<B>-magic</B>
|
|
|
|
may significantly increase processing time as each file has to opened
|
|
and read to find its magic number.
|
|
<P>
|
|
|
|
In summary, for all files, the default CREATOR is
|
|
<I>Unix</I>
|
|
|
|
and the default TYPE is
|
|
<I>TEXT</I>.
|
|
|
|
These can be changed by using entries in the
|
|
<I>.genisoimagerc</I>
|
|
|
|
file or by using
|
|
<B>-hfs-creator</B>
|
|
|
|
and/or
|
|
<B>-hfs-type</B>.
|
|
|
|
<P>
|
|
|
|
If the a file is in one of the known Apple/Unix formats (and the format
|
|
has been selected), the CREATOR and TYPE are taken from the values
|
|
stored in the Apple/Unix file.
|
|
<P>
|
|
|
|
Other files can have their CREATOR and TYPE set from their filename
|
|
extension (with
|
|
<B>-map</B>),
|
|
|
|
or their magic number (with
|
|
<B>-magic</B>).
|
|
|
|
If the default match is used in the
|
|
<I>mapping</I>
|
|
|
|
file, these values override the default CREATOR and TYPE.
|
|
<P>
|
|
|
|
A full CREATOR/TYPE database can be found at
|
|
<I><A HREF="http://www.angelfire.com/il/szekely/">http://www.angelfire.com/il/szekely/</A></I>.
|
|
|
|
|
|
<A NAME="lbAI"> </A>
|
|
<H2>HFS MACINTOSH FILE FORMATS</H2>
|
|
|
|
Macintosh files have two parts called the
|
|
<I>Data</I>
|
|
|
|
and
|
|
<I>Resource fork</I>.
|
|
|
|
Either may be empty. Unix (and many other OSs) can only
|
|
cope with files having one part (or fork). To add to this, Macintosh files
|
|
have a number of attributes associated with them --- probably the most
|
|
important are the TYPE and CREATOR. Again, Unix has no concept of these
|
|
types of attributes.
|
|
<P>
|
|
|
|
E.g., a Macintosh file may be a JPEG image where the image is stored in the
|
|
Data fork and a desktop thumbnail stored in the Resource fork. It is usually
|
|
the information in the data fork that is useful across platforms.
|
|
<P>
|
|
|
|
Therefore to store a Macintosh file on a Unix filesystem, a way has to be
|
|
found to cope with the two forks and the extra attributes (which are
|
|
referred to as the
|
|
<I>Finder info</I>).
|
|
|
|
Unfortunately, it seems that every software package that stores Macintosh
|
|
files on Unix has chosen a completely different storage method.
|
|
<P>
|
|
|
|
The Apple/Unix formats that
|
|
<B>genisoimage</B>
|
|
|
|
(partially) supports are:
|
|
<DL COMPACT>
|
|
<DT id="194">CAP AUFS format<DD>
|
|
Data fork stored in a file. Resource fork in subdirectory
|
|
<I>.resource</I>
|
|
|
|
with same filename as data fork. Finder info in subdirectory
|
|
<I>.finderinfo</I>
|
|
|
|
with same filename.
|
|
<DT id="195">AppleDouble/Netatalk<DD>
|
|
Data fork stored in a file. Resource fork stored in a file with
|
|
same name prefixed with `%'. Finder info also stored in same
|
|
`%' file. Netatalk uses the same format, but the resource
|
|
fork/Finder info stored in subdirectory
|
|
<I>.AppleDouble</I>
|
|
|
|
with same filename as data fork.
|
|
<DT id="196">AppleSingle<DD>
|
|
Data structures similar to above, except both forks and Finder
|
|
info are stored in one file.
|
|
<DT id="197">Helios EtherShare<DD>
|
|
Data fork stored in a file. Resource fork and Finder info together in
|
|
subdirectory
|
|
<I>.rsrc</I>
|
|
|
|
with same filename as data fork.
|
|
<DT id="198">IPT UShare<DD>
|
|
Like the EtherShare format, but the Finder info
|
|
is stored slightly differently.
|
|
<DT id="199">MacBinary<DD>
|
|
Both forks and Finder info stored in one file.
|
|
<DT id="200">Apple PC Exchange<DD>
|
|
Used by Macintoshes to store Apple files on DOS (FAT) disks.
|
|
Data fork stored in a file. Resource fork in subdirectory
|
|
<I>resource.frk</I> (or <I>RESOURCE.FRK</I>).
|
|
|
|
Finder info as one record in file
|
|
<I>finder.dat</I> (or <I>FINDER.DAT</I>).
|
|
|
|
Separate
|
|
<I>finder.dat</I>
|
|
|
|
for each data fork directory.
|
|
<DT id="201"><DD>
|
|
Note:
|
|
<B>genisoimage</B>
|
|
|
|
needs to know the native FAT cluster size of the disk that the PC Exchange
|
|
files are on (or have been copied from). This size is given by
|
|
<B>-cluster-size</B>.
|
|
|
|
The cluster or allocation size can be found by using the DOS utility
|
|
<B>chkdsk</B>.
|
|
|
|
<DT id="202"><DD>
|
|
May not work with PC Exchange v2.2 or higher files (available with MacOS 8.1).
|
|
DOS media containing PC Exchange files should be mounted as type
|
|
<I>msdos</I>
|
|
|
|
(not
|
|
<I>vfat</I>)
|
|
|
|
when using Linux.
|
|
<DT id="203">SGI/XINET<DD>
|
|
Used by SGI machines when they mount HFS disks. Data fork stored
|
|
in a file. Resource fork in subdirectory
|
|
<I>.HSResource</I>
|
|
|
|
with same filename. Finder info as one record in file
|
|
<I>.HSancillary</I>. Separate <I>.HSancillary</I>
|
|
|
|
for each data fork directory.
|
|
<DT id="204">Thursby Software Systems DAVE<DD>
|
|
Allows Macintoshes to store Apple files on SMB servers.
|
|
Data fork stored in a file. Resource fork in subdirectory
|
|
<I>resource.frk</I>.
|
|
|
|
Uses the AppleDouble format to store resource fork.
|
|
<DT id="205">Services for Macintosh<DD>
|
|
Format of files stored by NT Servers on NTFS filesystems. Data fork is
|
|
stored as
|
|
<I>filename</I>.
|
|
|
|
Resource fork stored as a NTFS stream called
|
|
<I>filename:AFP_Resource</I>.
|
|
|
|
The Finder info is stored as a NTFS stream called
|
|
<I>filename:Afp_AfpInfo</I>.
|
|
|
|
NTFS streams are normally invisible to the user.
|
|
<DT id="206"><DD>
|
|
Warning:
|
|
<B>genisoimage</B>
|
|
|
|
only partially supports the SFM format. If an HFS file
|
|
or folder stored on the NT server contains an illegal
|
|
NT character in its name, NT converts these characters to
|
|
<I>Private Use Unicode</I>
|
|
|
|
characters. The characters are: " * / < > ? \ | and a space or
|
|
period if it is the last character of the filename, character codes 0x01
|
|
to 0x1f (control characters) and Apple's apple logo.
|
|
<DT id="207"><DD>
|
|
Unfortunately, these private Unicode characters are not readable by the
|
|
<B>genisoimage</B>
|
|
|
|
NT executable. Therefore any file or directory
|
|
name containing these characters will be ignored --- including the contents of
|
|
any such directory.
|
|
<DT id="208">Mac OS X AppleDouble<DD>
|
|
When HFS/HFS+ files are copied or saved by Mac OS X on to a non-HFS
|
|
filesystem (e.g. UFS, NFS etc.), the files are stored in AppleDouble format.
|
|
Data fork stored in a file. Resource fork stored in a file with
|
|
same name prefixed with `._'. Finder info also stored in same `._' file.
|
|
<DT id="209">Mac OS X HFS (Alpha)<DD>
|
|
Not really an Apple/Unix encoding, but actual HFS/HFS+ files on a Mac OS X
|
|
system. Data fork stored in a file. Resource fork stored in a pseudo file
|
|
with the same name with the suffix
|
|
<I>/rsrc</I>.
|
|
|
|
The Finder info is only available via a Mac OS X library call.
|
|
<DT id="210"><DD>
|
|
See also
|
|
<I>README.macosx</I>.
|
|
|
|
<DT id="211"><DD>
|
|
Only works when used on Mac OS X.
|
|
<DT id="212"><DD>
|
|
If a file is found with a zero
|
|
length resource fork and empty finderinfo, it is assumed not to have
|
|
any Apple/Unix encoding --- therefore a TYPE and CREATOR can be set using
|
|
other methods.
|
|
</DL>
|
|
<P>
|
|
|
|
<B>genisoimage</B>
|
|
|
|
will attempt to set the CREATOR, TYPE, date and possibly other flags from
|
|
the finder info. Additionally, if it exists, the Macintosh filename is set
|
|
from the finder info, otherwise the Macintosh name is based on the Unix
|
|
filename --- see the
|
|
<B>HFS MACINTOSH FILENAMES</B>
|
|
|
|
section below.
|
|
<P>
|
|
|
|
When using
|
|
<B>-apple</B>,
|
|
|
|
the TYPE and CREATOR are stored in the optional System Use or
|
|
<I>SUSP</I>
|
|
|
|
field
|
|
in the ISO9660 Directory Record --- in much the same way as the Rock Ridge
|
|
attributes are. In fact to make life easy, the Apple extensions are added
|
|
at the beginning of the existing Rock Ridge attributes (i.e., to get the Apple
|
|
extensions you get the Rock Ridge extensions as well).
|
|
<P>
|
|
|
|
The Apple extensions require the resource fork to be stored as an ISO9660
|
|
<I>associated</I>
|
|
|
|
file. This is just like any normal file stored in the ISO9660 filesystem
|
|
except that the associated file flag is set in the Directory Record (bit
|
|
2). This file has the same name as the data fork (the file seen by
|
|
non-Apple machines). Associated files are normally ignored by other OSs
|
|
<P>
|
|
|
|
When using
|
|
<B>-hfs</B>,
|
|
|
|
the TYPE and CREATOR plus other finder info, are stored in a separate
|
|
HFS directory, not visible on the ISO9660 volume. The HFS directory references
|
|
the same data and resource fork files described above.
|
|
<P>
|
|
|
|
In most cases, it is better to use
|
|
<B>-hfs</B>
|
|
|
|
instead of
|
|
<B>-apple</B>,
|
|
|
|
as the latter imposes the limited ISO9660 characters allowed in
|
|
filenames. However, the Apple extensions do give the advantage that the
|
|
files are packed on the disk more efficiently and it may be possible to fit
|
|
more files on a CD.
|
|
|
|
<A NAME="lbAJ"> </A>
|
|
<H2>HFS MACINTOSH FILENAMES</H2>
|
|
|
|
Where possible, the HFS filename that is stored with an Apple/Unix file
|
|
is used for the HFS part of the CD. However, not all the Apple/Unix
|
|
encodings store the HFS filename with the finderinfo. In these cases,
|
|
the Unix filename is used --- with escaped special characters. Special
|
|
characters include `/' and characters with codes over 127.
|
|
<P>
|
|
|
|
AUFS escapes these characters by using `:' followed by the character code
|
|
as two hex digits. Netatalk and EtherShare have a similar scheme, but uses
|
|
`%' instead of a `:'.
|
|
<P>
|
|
|
|
If
|
|
<B>genisoimage</B>
|
|
|
|
cannot find an HFS filename, it uses the Unix name, with any
|
|
<I>%xx</I> or <I>:xx</I>
|
|
|
|
characters
|
|
(<I>xx</I>
|
|
|
|
are two hex digits) converted to a single character code. If
|
|
<I>xx</I>
|
|
|
|
are not hex digits ([0-9a-fA-F]), they are
|
|
left alone --- although any remaining `:' is converted to `%', as `:'
|
|
is the HFS directory separator. Care must be taken, as an ordinary Unix
|
|
file with
|
|
<I>%xx</I>
|
|
|
|
or
|
|
<I>:xx</I>
|
|
|
|
will also be converted. e.g.
|
|
<P>
|
|
|
|
<TABLE>
|
|
<TR VALIGN=top><TD>This:2fFile</TD><TD>converted to This/File<BR></TD></TR>
|
|
<TR VALIGN=top><TD COLSPAN=2><BR></TD></TR>
|
|
<TR VALIGN=top><TD>This:File</TD><TD>converted to This%File<BR></TD></TR>
|
|
<TR VALIGN=top><TD COLSPAN=2><BR></TD></TR>
|
|
<TR VALIGN=top><TD>This:t7File</TD><TD>converted to This%t7File<BR></TD></TR>
|
|
</TABLE>
|
|
|
|
<P>
|
|
|
|
Although HFS filenames appear to support uppercase and lowercase letters,
|
|
the filesystem is case-insensitive, i.e., the filenames
|
|
<I>aBc</I> and <I>AbC</I>
|
|
|
|
are the same. If a file is found in a directory with the same HFS name,
|
|
<B>genisoimage</B>
|
|
|
|
will attempt to make a unique name by adding `_' characters
|
|
to one of the filenames.
|
|
<P>
|
|
|
|
If an HFS filename exists for a file,
|
|
<B>genisoimage</B>
|
|
|
|
can use this name as the starting point for the ISO9660, Joliet and
|
|
Rock Ridge filenames using
|
|
<B>-mac-name</B>.
|
|
|
|
Normal Unix files without an HFS name will still use their Unix name.
|
|
e.g.
|
|
<P>
|
|
|
|
If a MacBinary (or PC Exchange) file is stored as
|
|
<I>someimage.gif.bin</I>
|
|
|
|
on the Unix filesystem, but contains a HFS file called
|
|
<I>someimage.gif</I>,
|
|
|
|
this is the name that would appear on the HFS part of the CD. However, as
|
|
<B>genisoimage</B>
|
|
|
|
uses the Unix name as the starting point for the other names,
|
|
the ISO9660 name generated will probably be
|
|
<I>SOMEIMAG.BIN</I>
|
|
|
|
and the Joliet/Rock Ridge would be
|
|
<I>someimage.gif.bin</I>.
|
|
|
|
This option will use
|
|
the HFS filename as the starting point and the ISO9660 name will probably be
|
|
<I>SOMEIMAG.GIF</I>
|
|
|
|
and the Joliet/Rock Ridge would be
|
|
<I>someimage.gif</I>.
|
|
|
|
<P>
|
|
|
|
<B>-mac-name</B>
|
|
|
|
will not currently work with
|
|
<B>-T</B>
|
|
|
|
--- the Unix name will be used in the
|
|
<I>TRANS.TBL</I>
|
|
|
|
file, not the Macintosh name.
|
|
<P>
|
|
|
|
The character set used to convert any HFS filename to a Joliet/Rock Ridge
|
|
filename defaults to
|
|
<I>cp10000</I>
|
|
|
|
(Mac Roman).
|
|
The character set used can be specified using
|
|
<B>-input-hfs-charset</B>.
|
|
|
|
Other built-in HFS character sets are:
|
|
<I>cp10006</I>
|
|
|
|
(MacGreek),
|
|
<I>cp10007</I>
|
|
|
|
(MacCyrillic),
|
|
<I>cp10029</I>
|
|
|
|
(MacLatin2),
|
|
<I>cp10079</I>
|
|
|
|
(MacIcelandandic) and
|
|
<I>cp10081</I>
|
|
|
|
(MacTurkish).
|
|
<P>
|
|
|
|
Note: the character codes used by HFS filenames taken from the various
|
|
Apple/Unix formats will not be converted as they are assumed to be in the
|
|
correct Apple character set. Only the Joliet/Rock Ridge names derived from
|
|
the HFS filenames will be converted.
|
|
<P>
|
|
|
|
The existing
|
|
<B>genisoimage</B>
|
|
|
|
code will filter out any illegal characters for the ISO9660 and Joliet
|
|
filenames, but as
|
|
<B>genisoimage</B>
|
|
|
|
expects to be dealing directly with Unix names, it leaves the Rock
|
|
Ridge names as is. But as `/' is a legal HFS filename character,
|
|
<B>-mac-name</B>
|
|
|
|
converts `/' to a `_' in Rock Ridge filenames.
|
|
<P>
|
|
|
|
If the Apple extensions are used, only the ISO9660 filenames will
|
|
appear on the Macintosh. However, as the Macintosh ISO9660 drivers can use
|
|
<I>Level 2</I>
|
|
|
|
filenames, you can use options like
|
|
<B>-allow-multidot</B>
|
|
|
|
without problems on
|
|
a Macintosh --- still take care over the names, for example
|
|
<I>this.file.name</I>
|
|
|
|
will be converted to
|
|
<I>THIS.FILE</I>
|
|
|
|
i.e. only have one `.', also filename
|
|
<I>abcdefgh</I>
|
|
|
|
will be seen as
|
|
<I>ABCDEFGH</I>
|
|
|
|
but
|
|
<I>abcdefghi</I>
|
|
|
|
will be seen as
|
|
<I>ABCDEFGHI.</I>
|
|
|
|
i.e. with a `.' at the end --- don't know if this is a Macintosh
|
|
problem or a
|
|
<B>genisoimage</B>/<B>mkhybrid</B>
|
|
|
|
problem. All filenames will be in uppercase
|
|
when viewed on a Macintosh. Of course, DOS/Win3.X machines will not be able
|
|
to see Level 2 filenames...
|
|
|
|
<A NAME="lbAK"> </A>
|
|
<H2>HFS CUSTOM VOLUME/FOLDER ICONS</H2>
|
|
|
|
To give a HFS CD a custom icon, make sure the root (top level) folder includes
|
|
a standard Macintosh volume icon file. To give a volume a custom icon on
|
|
a Macintosh, an icon has to be pasted over the volume's icon in the "Get Info"
|
|
box of the volume. This creates an invisible file called
|
|
<I>Icon\r</I>
|
|
|
|
(`\r' is the carriage return character) in the root folder.
|
|
<P>
|
|
|
|
A custom folder icon is very similar --- an invisible file called
|
|
<I>Icon\r</I>
|
|
|
|
exists in the folder itself.
|
|
<P>
|
|
|
|
Probably the easiest way to create a custom icon that
|
|
<B>genisoimage</B>
|
|
|
|
can use is to format a blank HFS floppy disk on a Mac and paste an icon
|
|
to its "Get Info" box. If using Linux with the HFS module installed,
|
|
mount the floppy:
|
|
<DL COMPACT>
|
|
<DT id="213"><DD>
|
|
mount -t hfs /dev/fd0 /mnt/floppy
|
|
</DL>
|
|
<P>
|
|
|
|
The floppy will be mounted as a CAP filesystem by default. Then run
|
|
<B>genisoimage</B>
|
|
|
|
using something like:
|
|
<DL COMPACT>
|
|
<DT id="214"><DD>
|
|
genisoimage --cap -o output source_dir /mnt/floppy
|
|
</DL>
|
|
<P>
|
|
|
|
If you are not using Linux, you can use
|
|
<B>hfsutils</B>
|
|
|
|
to copy the icon file from the floppy. However, care has to be taken,
|
|
as the icon file contains a control character. For example:
|
|
<DL COMPACT>
|
|
<DT id="215"><DD>
|
|
hmount /dev/fd0
|
|
<BR>
|
|
|
|
hdir -a
|
|
<BR>
|
|
|
|
hcopy -m Icon^V^M icon_dir/icon
|
|
</DL>
|
|
<P>
|
|
|
|
Where `^V^M' is control-V followed by control-M. Then run
|
|
<B>genisoimage</B>
|
|
|
|
by using something like:
|
|
<DL COMPACT>
|
|
<DT id="216"><DD>
|
|
genisoimage --macbin -o output source_dir icon_dir
|
|
</DL>
|
|
<P>
|
|
|
|
The procedure for creating/using custom folder icons is very similar --- paste
|
|
an icon to folder's "Get Info" box and transfer the resulting
|
|
<I>Icon\r</I>
|
|
|
|
file to the relevant directory in the
|
|
<B>genisoimage</B>
|
|
|
|
source tree.
|
|
<P>
|
|
|
|
You may want to hide the icon files from the ISO9660 and Joliet trees.
|
|
<P>
|
|
|
|
To give a custom icon to a Joliet CD, follow the instructions found at
|
|
<I><A HREF="http://www.cdrfaq.org/faq03.html#S3-21-1">http://www.cdrfaq.org/faq03.html#S3-21-1</A></I>.
|
|
|
|
|
|
<A NAME="lbAL"> </A>
|
|
<H2>HFS BOOT DRIVER</H2>
|
|
|
|
It
|
|
<I>may</I>
|
|
|
|
be possible to make the hybrid CD bootable on a Macintosh.
|
|
<P>
|
|
|
|
A bootable HFS CD requires an Apple CD-ROM (or compatible) driver, a bootable
|
|
HFS partition and the necessary System, Finder, etc. files.
|
|
<P>
|
|
|
|
A driver can be obtained from any other Macintosh bootable CD-ROM using the
|
|
<B>apple_driver</B>
|
|
|
|
utility. This file can then be used with
|
|
<B>-boot-hfs-file</B>.
|
|
|
|
<P>
|
|
|
|
The HFS partition (i.e. the hybrid disk in our case) must contain a
|
|
suitable System Folder, again from another CD-ROM or disk.
|
|
<P>
|
|
|
|
For a partition to be bootable, it must have its
|
|
<I>boot block</I>
|
|
|
|
set. The boot
|
|
block is in the first two blocks of a partition. For a non-bootable partition
|
|
the boot block is full of zeros. Normally, when a System file is copied to
|
|
partition on a Macintosh disk, the boot block is filled with a number of
|
|
required settings --- unfortunately I don't know the full spec for the boot
|
|
block, so I'm guessing that the following will work.
|
|
<P>
|
|
|
|
Therefore, the utility
|
|
<B>apple_driver</B>
|
|
|
|
also extracts the boot block from the
|
|
first HFS partition it finds on the given CD-ROM and this is used for the
|
|
HFS partition created by
|
|
<B>genisoimage</B>.
|
|
|
|
<P>
|
|
|
|
<I>Please note:</I>
|
|
|
|
By using a driver from an Apple CD and copying Apple software to your CD,
|
|
you become liable to obey Apple Computer, Inc. Software License Agreements.
|
|
|
|
<A NAME="lbAM"> </A>
|
|
<H2>EL TORITO BOOT INFORMATION TABLE</H2>
|
|
|
|
When
|
|
<B>-boot-info-table</B>
|
|
|
|
is given,
|
|
<B>genisoimage</B>
|
|
|
|
will modify the boot file specified by
|
|
<B>-b</B>
|
|
|
|
by inserting a 56-byte
|
|
<I>boot information table</I>
|
|
|
|
at offset 8 in
|
|
the file. This modification is done in the source filesystem, so make
|
|
sure you use a copy if this file is not easily recreated! This file
|
|
contains pointers which may not be easily or reliably obtained at boot
|
|
time.
|
|
<P>
|
|
|
|
The format of this table is as follows; all integers are in
|
|
section 7.3.1 ("little endian") format.
|
|
<P>
|
|
<DL COMPACT><DT id="217"><DD>
|
|
|
|
|
|
<PRE>
|
|
Offset Name Size Meaning
|
|
8 bi_pvd 4 bytes LBA of primary volume descriptor
|
|
12 bi_file 4 bytes LBA of boot file
|
|
16 bi_length 4 bytes Boot file length in bytes
|
|
20 bi_csum 4 bytes 32-bit checksum
|
|
24 bi_reserved 40 bytes Reserved
|
|
</PRE>
|
|
|
|
</DL>
|
|
|
|
<DL COMPACT>
|
|
<DT id="218"><DD>
|
|
The 32-bit checksum is the sum of all the 32-bit words in the boot
|
|
file starting at byte offset 64. All linear block addresses (LBAs)
|
|
are given in CD sectors (normally 2048 bytes).
|
|
|
|
</DL>
|
|
<A NAME="lbAN"> </A>
|
|
<H2>HPPA NOTES</H2>
|
|
|
|
To make a bootable CD for HPPA, at the very least a boot loader file
|
|
(<B>-hppa-bootloader</B>),
|
|
|
|
a kernel image file (32-bit, 64-bit, or both, depending on hardware)
|
|
and a boot command line
|
|
(<B>-hppa-cmdline</B>)
|
|
|
|
must be specified. Some systems can boot either a 32- or a 64-bit
|
|
kernel, and the firmware will choose one if both are present.
|
|
Optionally, a ramdisk can be used for the root filesystem using
|
|
<B>-hppa-cmdline</B>.
|
|
|
|
|
|
<A NAME="lbAO"> </A>
|
|
<H2>JIGDO NOTES</H2>
|
|
|
|
Jigdo is a tool to help in the distribution of large files like CD and
|
|
DVD images; see
|
|
<I><A HREF="http://atterer.org/jigdo/">http://atterer.org/jigdo/</A></I>
|
|
|
|
for more details. Debian CDs and DVD ISO
|
|
images are published on the web in jigdo format to allow end users to download
|
|
them more efficiently.
|
|
<P>
|
|
|
|
To create jigdo and template files alongside the ISO image from
|
|
<B>genisoimage</B>,
|
|
|
|
you must first generate a list of the files that will be
|
|
used, in the following format:
|
|
<P>
|
|
<DL COMPACT><DT id="219"><DD>
|
|
|
|
|
|
<PRE>
|
|
MD5sum File size Path
|
|
32 chars 12 chars to end of line
|
|
</PRE>
|
|
|
|
</DL>
|
|
|
|
<DL COMPACT>
|
|
<DT id="220"><DD>
|
|
</DL>
|
|
<P>
|
|
|
|
The MD5sum must be written in standard hexadecimal notation, the
|
|
file size must list the size of the file in bytes, and the path
|
|
must list the absolute path to the file. For example:
|
|
<P>
|
|
<PRE>
|
|
00006dcd58ff0756c36d2efae21be376 14736 /mirror/debian/file1
|
|
000635c69b254a1be8badcec3a8d05c1 211822 /mirror/debian/file2
|
|
00083436a3899a09633fc1026ef1e66e 22762 /mirror/debian/file3
|
|
</PRE>
|
|
|
|
<P>
|
|
|
|
Once you have this file, call
|
|
<B>genisoimage</B>
|
|
|
|
with all of your normal command-line parameters. Specify the output
|
|
filenames for the jigdo and template files using
|
|
<B>-jigdo-jigdo</B> and <B>-jigdo-template</B>,
|
|
|
|
and pass in the location of your MD5 list with
|
|
<B>-md5-list</B>.
|
|
|
|
<P>
|
|
|
|
If there are files that you do NOT want to be added into the jigdo
|
|
file (e.g. if they are likely to change often), specify them using
|
|
-jigdo-exclude. If you want to verify some of the files as they are
|
|
written into the image, specify them using -jigdo-force-md5. If any
|
|
files don't match,
|
|
<B>genisoimage</B>
|
|
|
|
will then abort. Both of these options take
|
|
regular expressions as input. It is possible to restrict the set of
|
|
files that will be used further based on size --- use the
|
|
-jigdo-min-file-size option.
|
|
<P>
|
|
|
|
Finally, the jigdo code needs to know how to map the files it is given
|
|
onto a mirror-style configuration. Specify how to map paths using
|
|
<B>-jigdo-map</B>.
|
|
|
|
Using
|
|
<I>Debian=/mirror/debian</I>
|
|
|
|
will cause all
|
|
paths starting with
|
|
<I>/mirror/debian</I>
|
|
|
|
to be mapped to
|
|
<I>Debian:<file></I>
|
|
|
|
in the output jigdo file.
|
|
|
|
<A NAME="lbAP"> </A>
|
|
<H2>EXAMPLES</H2>
|
|
|
|
<P>
|
|
|
|
To create a vanilla ISO9660 filesystem image in the file
|
|
<I>cd.iso</I>,
|
|
|
|
where the directory
|
|
<I>cd_dir</I>
|
|
|
|
will become the root directory of the CD, call:
|
|
<DL COMPACT>
|
|
<DT id="221"><DD>
|
|
% genisoimage -o cd.iso cd_dir
|
|
</DL>
|
|
<P>
|
|
|
|
To create a CD with Rock Ridge extensions of
|
|
the source directory
|
|
<I>cd_dir</I>:
|
|
|
|
<DL COMPACT>
|
|
<DT id="222"><DD>
|
|
% genisoimage -o cd.iso -R cd_dir
|
|
</DL>
|
|
<P>
|
|
|
|
To create a CD with Rock Ridge extensions of
|
|
the source directory
|
|
<I>cd_dir</I>
|
|
|
|
where all files have at least read permission and all files
|
|
are owned by
|
|
<I>root</I>,
|
|
|
|
call:
|
|
<DL COMPACT>
|
|
<DT id="223"><DD>
|
|
% genisoimage -o cd.iso -r cd_dir
|
|
</DL>
|
|
<P>
|
|
|
|
To write a tar archive directly to a CD that will later contain a simple
|
|
ISO9660 filesystem with the tar archive call:
|
|
<DL COMPACT>
|
|
<DT id="224"><DD>
|
|
% tar cf - . | genisoimage -stream-media-size 333000 | \
|
|
<BR>
|
|
|
|
<BR> wodim dev=b,t,l -dao tsize=333000s -
|
|
</DL>
|
|
<P>
|
|
|
|
To create a HFS hybrid CD with the Joliet and Rock Ridge extensions of
|
|
the source directory
|
|
<I>cd_dir</I>:
|
|
|
|
<DL COMPACT>
|
|
<DT id="225"><DD>
|
|
% genisoimage -o cd.iso -R -J -hfs cd_dir
|
|
</DL>
|
|
<P>
|
|
|
|
To create a HFS hybrid CD from the source directory
|
|
<I>cd_dir</I>
|
|
|
|
that contains
|
|
Netatalk Apple/Unix files:
|
|
<DL COMPACT>
|
|
<DT id="226"><DD>
|
|
% genisoimage -o cd.iso --netatalk cd_dir
|
|
</DL>
|
|
<P>
|
|
|
|
To create a HFS hybrid CD from the source directory
|
|
<I>cd_dir</I>,
|
|
|
|
giving all files
|
|
CREATOR and TYPES based on just their filename extensions listed in the file
|
|
"mapping".:
|
|
<DL COMPACT>
|
|
<DT id="227"><DD>
|
|
% genisoimage -o cd.iso -map mapping cd_dir
|
|
</DL>
|
|
<P>
|
|
|
|
To create a CD with the Apple Extensions to ISO9660, from the source
|
|
directories
|
|
<I>cd_dir</I>
|
|
|
|
and
|
|
<I>another_dir</I>.
|
|
|
|
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
|
|
<I>magic</I>:
|
|
|
|
<DL COMPACT>
|
|
<DT id="228"><DD>
|
|
% genisoimage -o cd.iso -apple -magic magic -probe \
|
|
<BR>
|
|
|
|
<BR> cd_dir another_dir
|
|
</DL>
|
|
<P>
|
|
|
|
The following example puts different files on the CD that all have
|
|
the name README, but have different contents when seen as a
|
|
ISO9660/Rock Ridge, Joliet or HFS CD.
|
|
<P>
|
|
|
|
Current directory contains:
|
|
<DL COMPACT>
|
|
<DT id="229"><DD>
|
|
% ls -F
|
|
<BR>
|
|
|
|
README.hfs README.joliet README.Unix cd_dir/
|
|
</DL>
|
|
<P>
|
|
|
|
The following command puts the contents of the directory
|
|
<I>cd_dir</I>
|
|
|
|
on the
|
|
CD along with the three README files --- but only one will be seen from
|
|
each of the three filesystems:
|
|
<DL COMPACT>
|
|
<DT id="230"><DD>
|
|
% genisoimage -o cd.iso -hfs -J -r -graft-points \
|
|
<BR>
|
|
|
|
<BR> -hide README.hfs -hide README.joliet \
|
|
<BR>
|
|
|
|
<BR> -hide-joliet README.hfs -hide-joliet README.Unix \
|
|
<BR>
|
|
|
|
<BR> -hide-hfs README.joliet -hide-hfs README.Unix \
|
|
<BR>
|
|
|
|
<BR> README=README.hfs README=README.joliet \
|
|
<BR>
|
|
|
|
<BR> README=README.Unix cd_dir
|
|
</DL>
|
|
<P>
|
|
|
|
i.e. the file README.hfs will be seen as README on the HFS CD and the
|
|
other two README files will be hidden. Similarly for the Joliet and
|
|
ISO9660/Rock Ridge CD.
|
|
<P>
|
|
|
|
There are probably all sorts of strange results possible with
|
|
combinations of the hide options ...
|
|
|
|
<A NAME="lbAQ"> </A>
|
|
<H2>NOTES</H2>
|
|
|
|
<P>
|
|
|
|
<B>genisoimage</B>
|
|
|
|
may safely be installed suid root. This may be needed to allow
|
|
<B>genisoimage</B>
|
|
|
|
to read the previous session when creating a multisession image.
|
|
<P>
|
|
|
|
If
|
|
<B>genisoimage </B>
|
|
|
|
is creating a filesystem image with Rock Ridge attributes and the
|
|
directory nesting level of the source directory tree is too much
|
|
for ISO9660,
|
|
<B>genisoimage </B>
|
|
|
|
will do deep directory relocation.
|
|
This results in a directory called
|
|
<B>RR_MOVED</B>
|
|
|
|
in the root directory of the CD. You cannot avoid this directory.
|
|
<P>
|
|
|
|
Many boot code options for different platforms are mutualy exclusive because
|
|
the boot blocks cannot coexist, ie. different platforms share the same data
|
|
locations in the image. See
|
|
<A HREF="http://lists.debian.org/debian-cd/2006/12/msg00109.html">http://lists.debian.org/debian-cd/2006/12/msg00109.html</A> for details.
|
|
|
|
<A NAME="lbAR"> </A>
|
|
<H2>BUGS</H2>
|
|
|
|
<P>
|
|
|
|
Any files that have hard links to files not in the tree being copied to the
|
|
ISO9660 filesystem will have an incorrect file reference count.
|
|
<P>
|
|
|
|
Does not check for SUSP record(s) in `.' entry of the
|
|
root directory to verify the existence of Rock Ridge
|
|
enhancements.
|
|
This problem is present when reading old sessions while
|
|
adding data in multisession mode.
|
|
<P>
|
|
|
|
Does not properly read relocated directories in multisession
|
|
mode when adding data.
|
|
Any relocated deep directory is lost if the new session does not
|
|
include the deep directory.
|
|
|
|
|
|
|
|
<P>
|
|
|
|
Does not re-use
|
|
<I>RR_MOVED</I>
|
|
|
|
when doing multisession from
|
|
<I>TRANS.TBL</I>.
|
|
|
|
<P>
|
|
|
|
Does not create whole_name entry for
|
|
<I>RR_MOVED</I>
|
|
|
|
in multisession mode.
|
|
<P>
|
|
|
|
There may be other bugs. Please, report them to the maintainers.
|
|
|
|
<A NAME="lbAS"> </A>
|
|
<H2>HFS PROBLEMS/LIMITATIONS</H2>
|
|
|
|
I have had to make several assumptions on how I expect the modified
|
|
libhfs routines to work, however there may be situations that either
|
|
I haven't thought of, or come across when these assumptions fail.
|
|
Therefore I can't guarantee that
|
|
<B>genisoimage</B>
|
|
|
|
will work as expected
|
|
(although I haven't had a major problem yet). Most of the HFS features work
|
|
fine, but some are not fully tested. These are marked as
|
|
<I>Alpha</I>
|
|
|
|
above.
|
|
<P>
|
|
|
|
Although HFS filenames appear to support uppercase and lowercase letters,
|
|
the filesystem is case-insensitive, i.e., the filenames
|
|
<I>aBc</I> and AbC
|
|
|
|
are the same. If a file is found in a directory with the same HFS name,
|
|
<B>genisoimage</B>
|
|
|
|
will attempt to make a unique name by adding `_' characters
|
|
to one of the filenames.
|
|
<P>
|
|
|
|
HFS file/directory names that share the first 31 characters have
|
|
`_N' (a decimal number) substituted for the last few characters
|
|
to generate unique names.
|
|
<P>
|
|
|
|
Care must be taken when "grafting" Apple/Unix files or directories (see
|
|
above for the method and syntax involved). It is not possible to use a
|
|
new name for an Apple/Unix encoded file/directory. e.g. If a Apple/Unix
|
|
encoded file called
|
|
<I>oldname</I>
|
|
|
|
is to added to the CD, you cannot use the command line:
|
|
<DL COMPACT>
|
|
<DT id="231"><DD>
|
|
genisoimage -o output.raw -hfs -graft-points newname=oldname cd_dir
|
|
</DL>
|
|
<P>
|
|
|
|
<B>genisoimage</B>
|
|
|
|
will be unable to decode
|
|
<I>oldname</I>.
|
|
|
|
However, you can graft
|
|
Apple/Unix encoded files or directories as long as you do not attempt to
|
|
give them new names as above.
|
|
<P>
|
|
|
|
When creating an HFS volume with the multisession options,
|
|
<B>-M</B>
|
|
|
|
and
|
|
<B>-C</B>,
|
|
|
|
only files in the last session will be in the HFS volume. i.e.
|
|
<B>genisoimage</B>
|
|
|
|
cannot
|
|
<I>add</I>
|
|
|
|
existing files from previous sessions to the HFS volume.
|
|
<P>
|
|
|
|
However, if each session is created with
|
|
<B>-part</B>,
|
|
|
|
each session will appear as
|
|
separate volumes when mounted on a Mac. In this case, it is worth using
|
|
<B>-V</B> or <B>-hfs-volid</B>
|
|
|
|
to give each session a unique volume name,
|
|
otherwise each "volume" will appear on the Desktop with the same name.
|
|
<P>
|
|
|
|
Symbolic links (as with all other non-regular files) are not added to
|
|
the HFS directory.
|
|
<P>
|
|
|
|
Hybrid volumes may be larger than pure ISO9660 volumes
|
|
containing the same data. In some cases (e.g. DVD sized volumes) the
|
|
difference can be significant. As an HFS volume gets bigger, so does the
|
|
allocation block size (the smallest amount of space a file can occupy).
|
|
For a 650MB CD, the allocation block is 10kB, for a 4.7GB DVD it will be
|
|
about 70kB.
|
|
<P>
|
|
|
|
The maximum number of files in an HFS volume is about 65500 --- although
|
|
the real limit will be somewhat less than this.
|
|
<P>
|
|
|
|
The resulting hybrid volume can be accessed on a Unix machine by using
|
|
the hfsutils routines. However, no changes can be made to the volume as it
|
|
is set as
|
|
<B>locked.</B>
|
|
|
|
The option
|
|
<B>-hfs-unlock</B>
|
|
|
|
will create an output image that is unlocked --- however no changes should be
|
|
made to the contents of the volume (unless you really know what you are
|
|
doing) as it's not a "real" HFS volume.
|
|
<P>
|
|
|
|
<B>-mac-name</B>
|
|
|
|
will not currently work with
|
|
<B>-T</B>
|
|
|
|
--- the Unix name will be used in the
|
|
<I>TRANS.TBL</I>
|
|
|
|
file, not the Macintosh name.
|
|
<P>
|
|
|
|
Although
|
|
<B>genisoimage</B>
|
|
|
|
does not alter the contents of a file, if a binary file has its TYPE
|
|
set as
|
|
<I>TEXT</I>, it <I>may</I>
|
|
|
|
be read incorrectly on a Macintosh. Therefore a better choice for the
|
|
default TYPE may be
|
|
<I>????</I>.
|
|
|
|
<P>
|
|
|
|
<B>-mac-boot-file</B>
|
|
|
|
may not work at all...
|
|
<P>
|
|
|
|
May not work with PC Exchange v2.2 or higher files (available with MacOS 8.1).
|
|
DOS media containing PC Exchange files should be mounted as type
|
|
<B>msdos</B>
|
|
|
|
(not
|
|
<B>vfat</B>)
|
|
|
|
when using Linux.
|
|
<P>
|
|
|
|
The SFM format is only partially supported --- see
|
|
<B>HFS MACINTOSH FILE FORMATS</B>
|
|
|
|
section above.
|
|
<P>
|
|
|
|
It is not possible to use
|
|
<B>-sparc-boot</B> or <B>-generic-boot</B> with
|
|
|
|
<B>-boot-hfs-file</B> or <B>-prep-boot</B>.
|
|
|
|
<P>
|
|
|
|
<B>genisoimage</B>
|
|
|
|
should be able to create HFS hybrid images over 4Gb, although this has not
|
|
been fully tested.
|
|
|
|
<A NAME="lbAT"> </A>
|
|
<H2>SEE ALSO</H2>
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?5+genisoimagerc">genisoimagerc</A></B>(5),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+wodim">wodim</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?8+mkzftree">mkzftree</A></B>(8),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?5+magic">magic</A></B>(5).
|
|
|
|
|
|
<A NAME="lbAU"> </A>
|
|
<H2>AUTHORS</H2>
|
|
|
|
<B>genisoimage</B>
|
|
|
|
is derived from
|
|
<B>mkisofs</B>
|
|
|
|
from the
|
|
<B>cdrtools 2.01.01a08</B>
|
|
|
|
package from May 2006 (with few updates extracted from cdrtools 2.01.01a24 from
|
|
March 2007) from .IR <A HREF="http://cdrecord.berlios.de/">http://cdrecord.berlios.de/</A> ,
|
|
but is now part of the
|
|
<B>cdrkit</B>
|
|
|
|
suite, maintained by Joerg Jaspert, Eduard Bloch, Steve McIntyre, Peter
|
|
Samuelson, Christian Fromme, Ben Hutchings, and other contributors.
|
|
The maintainers can be contacted at
|
|
<I><A HREF="mailto:debburn-devel@lists.alioth.debian.org">debburn-devel@lists.alioth.debian.org</A></I>,
|
|
|
|
or see the
|
|
<B>cdrkit</B>
|
|
|
|
project web site at
|
|
<I><A HREF="http://www.cdrkit.org/">http://www.cdrkit.org/</A></I>.
|
|
|
|
<P>
|
|
|
|
Eric Youngdale wrote the first versions (1993-1998) of
|
|
<B>mkisofs</B>.
|
|
|
|
Jörg Schilling wrote the SCSI transport library and its
|
|
interface, and has maintained
|
|
<B>mkisofs</B>
|
|
|
|
since 1999. James Pearson wrote the HFS hybrid code, using
|
|
<I>libhfs</I>
|
|
|
|
by Robert Leslie. Pearson, Schilling, Jungshik Shin and Jaakko
|
|
Heinonen contributed to the character set conversion code. The
|
|
<B>cdrkit</B>
|
|
|
|
maintainers have maintained
|
|
<B>genisoimage</B>
|
|
|
|
since 2006.
|
|
<P>
|
|
|
|
<PRE>
|
|
Copyright 1993-1998 by Yggdrasil Computing, Inc.
|
|
Copyright 1996-1997 by Robert Leslie
|
|
Copyright 1997-2001 by James Pearson
|
|
Copyright 1999-2006 by Jörg Schilling
|
|
Copyright 2007 by Jörg Schilling (originating few updates)
|
|
Copyright 2002-2003 by Jungshik Shin
|
|
Copyright 2003 by Jaakko Heinonen
|
|
Copyright 2006 by the Cdrkit maintainers
|
|
</PRE>
|
|
|
|
<P>
|
|
|
|
If you want to take part in the development of
|
|
<B>genisoimage</B>,
|
|
|
|
you may join the
|
|
<B>cdrkit</B>
|
|
|
|
developer mailing list by following the instructions on
|
|
<I><A HREF="http://alioth.debian.org/mail/?group_id=31006">http://alioth.debian.org/mail/?group_id=31006</A></I>.
|
|
|
|
The email address of the list is
|
|
<I><A HREF="mailto:debburn-devel@lists.alioth.debian.org">debburn-devel@lists.alioth.debian.org</A></I>.
|
|
|
|
This is also the address for user support questions. Note that
|
|
<B>cdrkit</B> and <B>cdrtools</B>
|
|
|
|
are not affiliated.
|
|
<P>
|
|
|
|
|
|
<A NAME="lbAV"> </A>
|
|
<H2>ACKNOWLEDGEMENTS</H2>
|
|
|
|
UNIX is a registered trademark of The Open Group in the US and other countries.
|
|
<P>
|
|
|
|
<HR>
|
|
<A NAME="index"> </A><H2>Index</H2>
|
|
<DL>
|
|
<DT id="232"><A HREF="#lbAB">NAME</A><DD>
|
|
<DT id="233"><A HREF="#lbAC">SYNOPSIS</A><DD>
|
|
<DT id="234"><A HREF="#lbAD">DESCRIPTION</A><DD>
|
|
<DT id="235"><A HREF="#lbAE">OPTIONS</A><DD>
|
|
<DT id="236"><A HREF="#lbAF">HFS OPTIONS</A><DD>
|
|
<DT id="237"><A HREF="#lbAG">CHARACTER SETS</A><DD>
|
|
<DT id="238"><A HREF="#lbAH">HFS CREATOR/TYPE</A><DD>
|
|
<DT id="239"><A HREF="#lbAI">HFS MACINTOSH FILE FORMATS</A><DD>
|
|
<DT id="240"><A HREF="#lbAJ">HFS MACINTOSH FILENAMES</A><DD>
|
|
<DT id="241"><A HREF="#lbAK">HFS CUSTOM VOLUME/FOLDER ICONS</A><DD>
|
|
<DT id="242"><A HREF="#lbAL">HFS BOOT DRIVER</A><DD>
|
|
<DT id="243"><A HREF="#lbAM">EL TORITO BOOT INFORMATION TABLE</A><DD>
|
|
<DT id="244"><A HREF="#lbAN">HPPA NOTES</A><DD>
|
|
<DT id="245"><A HREF="#lbAO">JIGDO NOTES</A><DD>
|
|
<DT id="246"><A HREF="#lbAP">EXAMPLES</A><DD>
|
|
<DT id="247"><A HREF="#lbAQ">NOTES</A><DD>
|
|
<DT id="248"><A HREF="#lbAR">BUGS</A><DD>
|
|
<DT id="249"><A HREF="#lbAS">HFS PROBLEMS/LIMITATIONS</A><DD>
|
|
<DT id="250"><A HREF="#lbAT">SEE ALSO</A><DD>
|
|
<DT id="251"><A HREF="#lbAU">AUTHORS</A><DD>
|
|
<DT id="252"><A HREF="#lbAV">ACKNOWLEDGEMENTS</A><DD>
|
|
</DL>
|
|
<HR>
|
|
This document was created by
|
|
<A HREF="/cgi-bin/man/man2html">man2html</A>,
|
|
using the manual pages.<BR>
|
|
Time: 00:05:13 GMT, March 31, 2021
|
|
</BODY>
|
|
</HTML>
|