mkisofs.8

创建一个符合iso-9660标准的iso文件系统

.I SOMEIMAG.GIF
and the Joliet/Rock Ridge would be
.IR someimage.gif .
.PP
Using the
.B \-mac-name
option will not currently work with the
.B \-T
option - the Unix
name will be used in the TRANS.TBL file, not the Macintosh name.
.PP
The existing mkisofs code will filter out any illegal characters for the
ISO9660 and Joliet filenames, but as mkisofs expects to be dealing
directly with Unix names, it leaves the Rock Ridge names as is.
But as '/' is a legal HFS filename character, the
.B \-mac-name
option converts '/' to a '_' in Rock Ridge filenames.
.PP
If the Apple extensions are used, then only the ISO9660 filenames will
appear on the Macintosh. However, as the Macintosh ISO9660 drivers can use
.I Level 2
filenames, then you can use options like
.B \-allow-multidot
without problems on
a Macintosh - still take care over the names, for example
.I this.file.name
will be converted to
.I THIS.FILE
i.e. only have one '.', also filename
.I abcdefgh
will be seen as
.I ABCDEFGH
but
.I abcdefghi
will be seen as
.I ABCDEFGHI.
i.e. with a '.' at the end - don't know if this is a Macintosh
problem or m\&kisofs/mkhybrid 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...

.SH "HFS CUSTOM VOLUME/FOLDER ICONS
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 'Icon\\r' ('\\r' is
the 'carriage return' character) in the root folder.
.P
A custom folder icon is very similar - an invisible file called 'Icon\\r'
exits in the folder itself.
.P
Probably the easiest way to create a custom icon that mkisofs can use, is to
format a blank HFS floppy disk on a Mac, paste an icon to its "Get Info"
box. If using Linux with the HFS module installed, mount the floppy using
something like:

	mount \-t hfs /dev/fd0 /mnt/floppy

The floppy will be mounted as a CAP file system by default. Then run mkisofs
using something like:

	mkisofs \--cap \-o output source_dir /mnt/floppy

If you are not using Linux, then you can use the hfsutils to copy the icon
file from the floppy. However, care has to be taken, as the icon file
contains a control character. e.g.

	hmount /dev/fd0
.br
	hdir \-a
.br
	hcopy \-m Icon^V^M icon_dir/icon

Where '^V^M' is control-V followed by control-M. Then run 
.B mkisofs
by using something like:

	mkisofs \--macbin \-o output source_dir icon_dir
.PP
The procedure for creating/using custom folder icons is very similar - paste
an icon to folder's "Get Info" box and transfer the resulting 'Icon\\r'
file to the relevant directory in the mkisofs source tree.
.PP
You may want to hide the icon files from the ISO9660 and Joliet trees.
.PP
To give a custom icon to a Joliet CD, follow the instructions found at:
http://www.fadden.com/cdrfaq/faq03.html#[3-21]

.SH "HFS BOOT DRIVER
It 
.I may
be possible to make the hybrid CD bootable on a Macintosh.
.PP
A bootable HFS CD requires an Apple CD-ROM (or compatible) driver, a bootable
HFS partition and the necessary System, Finder, etc. files.
.PP
A driver can be obtained from any other Macintosh bootable CD-ROM using the
.I apple_driver
utility. This file can then be used with the
.B \-boot-hfs-file
option.
.PP
The HFS partition (i.e. the hybrid disk in our case) must contain a
suitable System Folder, again from another CD-ROM or disk.
.PP
For a partition to be bootable, it must have it's 
.I boot block
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 OK.
.PP
Therefore, the utility
.I apple_driver
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
.BR mkisofs .
.IP "PLEASE NOTE"
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.
.SH "EL TORITO BOOT INFORMATION TABLE
When the
.B \-boot-info-table
option is given,
.B mkisofs
will modify the boot file specified by the
.B \-b
option by inserting a 56-byte "boot information table" 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.
.PP
The format of this table is as follows; all integers are in
section 7.3.1 ("little endian") format.
.sp
.RS +.2i
.ta 1.0i 2.5i 3.5i
.nf
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
.fi
.RE
.sp
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).
.SH CONFIGURATION
.B mkisofs
looks for the
.B \&.m\&kisofsrc
file,
first in the current working directory,
then in the user's home directory,
and then in the directory in which the
.B mkisofs
binary is stored.  This file is assumed to contain a series of lines
of the form
.BI TAG= value,
and in this way you can specify certain options.
The case of the tag is not significant.
Some fields in the volume header
are not settable on the command line, but can be altered through this
facility.
Comments may be placed in this file,
using lines which start with a hash (#) character.
.TP
.B APPI
The application identifier
should describe the application that will be on the disc.
There is space on the disc for 128 characters of information.
May be overridden using the
.B \-A
command line option.
.TP
.B COPY
The copyright information,
often the name of a file on the disc containing the copyright notice.
There is space in the disc for 37 characters of information.
May be overridden using the
.B \-copyright
command line option.
.TP
.B ABST
The abstract information,
often the name of a file on the disc containing an abstract.
There is space in the disc for 37 characters of information.
May be overridden using the
.B \-abstract
command line option.
.TP
.B BIBL
The bibliographic information,
often the name of a file on the disc containing a bibliography.
There is space in the disc for 37 characters of information.
May be overridden using the
.B \-bilio
command line option.
.TP
.B PREP
This should describe the preparer of the CDROM,
usually with a mailing address and phone number.
There is space on the disc for 128 characters of information.
May be overridden using the
.B \-p
command line option.
.TP
.B PUBL
This should describe the publisher of the CDROM,
usually with a mailing address and phone number.
There is space on the disc for 128 characters of information.
May be overridden using the
.B \-P
command line option.
.TP
.B SYSI
The System Identifier.
There is space on the disc for 32 characters of information.
May be overridden using the
.B \-sysid
command line option.
.TP
.B VOLI
The Volume Identifier.
There is space on the disc for 32 characters of information.
May be overridden using the
.B \-V
command line option.
.TP
.B VOLS
The Volume Set Name.
There is space on the disc for 128 characters of information.
May be overridden using the
.B \-volset
command line option.
.TP
.B HFS_TYPE
The default TYPE for Macintosh files. Must be exactly 4 characters.
May be overridden using the
.B \-hfs-type
command line option.
.TP
.B HFS_CREATOR
The default CREATOR for Macintosh files. Must be exactly 4 characters.
May be overridden using the
.B \-hfs-creator
command line option.
.PP
.B mkisofs
can also be configured at compile time with defaults for many of these fields.
See the file defaults.h.

.SH EXAMPLES
.PP
To create a vanilla ISO-9660 filesystem image in the file 
.IR cd.iso ,
where the directory
.I cd_dir
will become the root directory if the CD, call:
.PP
% mkisofs \-o cd.iso cd_dir
.PP
To create a HFS hybrid CD with Rock Ridge extensions of
the source directory
.IR cd_dir :
.PP
% mkisofs \-o cd.iso \-R cd_dir
.PP
To create a HFS hybrid CD with Rock Ridge extensions of
the source directory
.I cd_dir
where all files have at least read permission and all files
are owned by
.IR root ,
call:
.PP
% mkisofs \-o cd.iso \-r cd_dir
.PP
To create a HFS hybrid CD with the Joliet and Rock Ridge extensions of
the source directory
.IR cd_dir :
.PP
% mkisofs \-o cd.iso \-R \-J \-hfs cd_dir
.PP
To create a HFS hybrid CD from the source directory 
.I cd_dir
that contains
Netatalk Apple/Unix files:
.PP
% mkisofs \-o cd.iso \--netatalk cd_dir
.PP
To create a HFS hybrid CD from the source directory
.IR cd_dir ,
giving all files
CREATOR and TYPES based on just their filename extensions listed in the file 
"mapping".:
.PP
% mkisofs \-o cd.iso \-map mapping cd_dir
.PP
To create a CD with the 'Apple Extensions to ISO9660', from the source
directories
.I cd_dir
and
.IR another_dir.
Files in all the known Apple/Unix format
are decoded and any other files are given CREATOR and TYPE based on their
magic number given in the file "magic":
.PP
% mkisofs \-o cd.iso \-apple \-magic magic \-probe \\
.br
        cd_dir another_dir
.PP
The following example puts different files on the CD that all have
the name README, but have different contents when seen as a
ISO9660/RockRidge, Joliet or HFS CD.
.PP
Current directory contains:
.PP
% ls \-F
.br
README.hfs     README.joliet  README.unix    cd_dir/
.PP
The following command puts the contents of the directory
.I cd_dir
on the
CD along with the three README files - but only one will be seen from
each of the three filesystems:
.PP
% mkisofs \-o cd.iso \-hfs \-J \-r \\
.br
        \-hide README.hfs \-hide README.joliet \\
.br
        \-hide-joliet README.hfs \-hide-joliet README.unix \\
.br
        \-hide-hfs README.joliet \-hide-hfs README.unix \\
.br
        README=README.hfs README=README.joliet \\
.br
        README=README.unix cd_dir
.PP
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/RockRidge CD.
.PP
There are probably all sorts of strange results possible with
combinations of the hide options ...

.SH AUTHOR
.B m\&kisofs
is not based on the standard mk*fs tools for unix, because we must generate
a complete  copy of an existing filesystem on a disk in the  iso9660
filesystem.  The name m\&kisofs is probably a bit of a misnomer, since it
not only creates the filesystem, but it also populates it as well.
However, the appropriate tool name for a UNIX tool that creates populated
filesystems - mkproto - is not well known.
.PP
.br
Eric Youngdale <[e-mail]> or <[e-mail]> wrote the
first versions (1993 .\|.\|. 1998) of the m\&kisofs utility.
The copyright for old versions of the m\&kisofs utility is held by
Yggdrasil Computing, Incorporated.
J\*org Schilling wrote the SCSI transport library and it's adaptation layer to
.B mkisofs
and newer parts (starting from 1999) of the utility, this makes
.B mkisofs
Copyright (C) 1999, 2000 J\*org Schilling.
.PP
HFS hybrid code Copyright (C) James Pearson 1997, 1998, 1999, 2000
.br
libhfs code Copyright (C) 1996, 1997 Robert Leslie
.br
libfile code Copyright (C) Ian F. Darwin 1986, 1987, 1989, 1990, 1991,
1992, 1994, 1995.
.SH NOTES
.B Mkisofs
may safely be installed suid root. This may be needed to allow
.B mkisofs
to read the previous session when creating a multi session image.
.SH BUGS
.TP
\(bu
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.
.TP
\(bu
Does not check for SUSP record(s) in "." entry of the
root directory to verify the existence of Rock Ridge
enhancements.
.sp
This problem is present when reading old sessions while
adding data in multi-session mode.
.TP
\(bu
Does not properly read relocated directories in multi-session
mode when adding data.
.sp
Any relocated deep directory is lost if the new session does not
include the deep directory.
.sp
Repeat by: create first session with deep directory relocation
then add new session with a single dir that differs from the
old deep path.
.TP
\(bu
Does not re-use RR_MOVED when doing multi-session from TRANS.TBL
.TP
\(bu
Does not create whole_name entry for RR_MOVED in multi-session
mode.
.PP
There may be some other ones.  Please, report them to the author.

.SH "HFS PROBLEMS/LIMITATIONS
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 mkisofs will work as expected
(although I haven't had a major problem yet). Most of the HFS features work
fine, however, some are not fully tested. These are marked as
.I Alpha
above.
.PP
Although HFS filenames appear to support upper and lower case letters,
the filesystem is case insensitive. i.e. the filenames "aBc" and "AbC"
are the same. If a file is found in a directory with the same HFS name, then
.I mkisofs
will attempt, where possible, to make a unique name by adding '_' characters
to one of the filenames.
.PP
HFS file/directory names that share the first 31 characters have
_N' (N == decimal number) substituted for the last few characters
to generate unique names.
.PP
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 "oldname" is to added to the CD, then you can not use
the command line:
.IP
mkisofs \