mkisofs.8

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

desktop. Folder location and size on screen, its scroll positions, folder
View (view as Icons, Small Icons, etc.) are also preserved.
This option may become set by default in the future.
(Alpha).
.TP
.BI \-root-info " file
Set the location, size on screen, scroll positions, folder View etc. for the
root folder of an HFS volume. See README.rootinfo for more information.
(Alpha)
.TP
.BI \-prep-boot " FILE
PReP boot image file. Up to 4 are allowed. See README.prep_boot (Alpha)
.TP
.B \--cap
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
options are given.
.TP
.B \--netatalk
Look for NETATALK Macintosh files
.TP
.B \--double
Look for AppleDouble Macintosh files
.TP
.B \--ethershare
Look for Helios EtherShare Macintosh files
.TP
.B \--ushare
Look for IPT UShare Macintosh files
.TP
.B \--exchange
Look for PC Exchange Macintosh files
.TP
.B \--sgi
Look for SGI Macintosh files
.TP
.B \--xinet
Look for XINET Macintosh files
.TP
.B \--macbin
Look for MacBinary Macintosh files
.TP
.B \--single
Look for AppleSingle Macintosh files
.TP
.B \--dave
Look for Thursby Software Systems DAVE Macintosh files
.TP
.B \--sfm
Look for Microsoft's Services for Macintosh files (NT only) (Alpha)

.SH "HFS CREATOR/TYPE
A Macintosh file has two properties associated with it which define
which application created the file, the
.I CREATOR
and what data the file contains, the
.IR TYPE .
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.
.LP
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
file (the
.B \-map
option) and/or using the
.I magic number
(usually a
.I signature
in the first few bytes)
of a file (the
.B \-magic
option). If both these options are given, then their order on the command
line is important. If the
.B \-map
option is given first, then a filename extension match is attempted
before a magic number match. However, if the
.B \-magic
option is given first, then a magic number match is attempted before a
filename extension match.
.PP
If a mapping or magic file is not used, or no match is found then the default
CREATOR and TYPE for all regular files can be set by using entries in the 
.B \&.m\&kisofsrc
file or using the 
.B \-hfs-creator
and/or
.B \-hfs-type
options, otherwise the default CREATOR and TYPE are 'unix' and 'TEXT'.
.PP
The format of the
.I mapping
file is the same
.I afpfile
format as used by
.IR aufs .
This file has five columns for the
.IR extension ,
.I file
.IR translation ,
.IR CREATOR ,
.I TYPE
and
.IR Comment .
Lines starting with the '#' character are
comment lines and are ignored. An example file would be like:
.LP
.TS
tab (/);
l s s s s
l s s s s
l l l l l .
# Example filename mapping file
#
# EXTN/XLate/CREATOR/TYPE/Comment
\.tif/Raw/'8BIM'/'TIFF'/"Photoshop TIFF image"
\.hqx/Ascii/'BnHq'/'TEXT'/"BinHex file"
\.doc/Raw/'MSWD'/'WDBN'/"Word file"
\.mov/Raw/'TVOD'/'MooV'/"QuickTime Movie"
*/Ascii/'ttxt'/'TEXT'/"Text file"
.TE
.LP
Where:
.IP
The first column
.I EXTN
defines the Unix filename extension to be
mapped. The default mapping for any filename extension that doesn't
match is defined with the "*" character.
.IP
The
.I Xlate
column defines the type of text translation between the Unix and
Macintosh file it is ignored by
.BR mkisofs ,
but is kept to be compatible with
.BR aufs (1).
Although 
.B mkisofs
does not alter the contents of a file, if a binary file has it's TYPE
set as 'TEXT', it
.I may
be read incorrectly on a Macintosh. Therefore a better choice for the
default TYPE may be '????'
.IP
The
.I CREATOR
and
.I TYPE
keywords must be 4 characters long and enclosed in single quotes.
.IP
The comment field is enclosed in double quotes - it is ignored by
.BR mkisofs ,
but is kept to be compatible with 
.BR aufs .
.PP
The format of the
.I magic
file is almost identical to the
.BR magic (4)
file used by the Linux
.BR file (1)
command - the routines for reading and decoding the
.I magic
file are based on the Linux
.BR file (1)
command.
.PP
This file has four tab separated columns for the 
.I byte
.IR offset ,
.IR type ,
.I test
and
.IR message .
Lines starting with the '#' character are
comment lines and are ignored. An example file would be like:
.LP
.TS
tab (/);
l s s s
l s s s
l l l l .
# Example magic file
#
# off/type/test/message
0/string/GIF8/8BIM GIFf  GIF image
0/beshort/0xffd8/8BIM JPEG  image data
0/string/SIT!/SIT! SIT!  StuffIt Archive
0/string/\\037\\235/LZIV ZIVU  standard unix compress
0/string/\\037\\213/GNUz ZIVU  gzip compressed data
0/string/%!/ASPS TEXT  Postscript
0/string/\\004%!/ASPS TEXT  PC Postscript with a ^D to start
4/string/moov/txtt MooV  QuickTime movie file (moov)
4/string/mdat/txtt MooV  QuickTime movie file (mdat)
.TE
.PP
The format of the file is described in the
.BR magic (4)
man page. The only difference here is that for each entry in the magic file, the
.I message
for the initial offset
.B must
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.
.PP
Using the
.B \-magic
option may significantly increase processing time as each file has to opened
and read to find it's magic number.
.PP
In summary, for all files, the default CREATOR is 'unix' and the default
TYPE is 'TEXT'.  These can be changed by using entries in the 
.I \&.m\&kisofsrc 
file or by using the
.B \-hfs-creator
and/or
.B \-hfs-type
options. 
.PP
If the a file is in one of the known Apple/Unix formats (and the format
has been selected), then the CREATOR and TYPE are taken from the values
stored in the Apple/Unix file.
.PP
Other files can have their CREATOR and TYPE set from their file name
extension (the
.B \-map
option), or their magic number (the
.B \-magic
option). If the default match is used in the
.I mapping
file, then these values override the default CREATOR and TYPE.
.PP
A full CREATOR/TYPE database can be found at 
http://www.angelfire.com/il/szekely/index.html

.SH "HFS MACINTOSH FILE FORMATS
Macintosh files have two parts called the
.I Data
and
.I Resource
fork. 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.
.PP
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.
.PP
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
.IR info ).
Unfortunately, it seems that every software package that stores Macintosh
files on Unix has chosen a completely different storage method.
.PP
The Apple/Unix formats that
.I mkisofs
(partially) supports are:
.IP "CAP AUFS format"
Data fork stored in a file. Resource fork in subdirectory .resource
with same filename as data fork. Finder info
in .finderinfo subdirectory with same filename.
.IP "AppleDouble/Netatalk"
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/finderinfo stored in subdirectory .AppleDouble with same
name as data fork.
.IP AppleSingle
Data structures similar to above, except both forks and finder
info are stored in one file.
.IP "Helios EtherShare"
Data fork stored in a file. Resource fork and finder info together in
subdirectory .rsrc with same filename as data fork.
.IP "IPT UShare"
Very similar to the EtherShare format, but the finder info
is stored slightly differently.
.IP MacBinary
Both forks and finder info stored in one file.
.IP "Apple PC Exchange"
Used by Macintoshes to store Apple files on DOS (FAT) disks.
Data fork stored in a file. Resource fork in subdirectory
resource.frk (or RESOURCE.FRK). Finder info as one record
in file finder.dat (or FINDER.DAT). Separate finder.dat for
each data fork directory.
.IP
Note: 
.I mkisofs
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 the
.B \-cluster-size
option.
The cluster or allocation size can be found by using the DOS utility
.BR CHKDSK .
.IP
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
(not
.BR vfat )
when using Linux.
.IP "SGI/XINET"
Used by SGI machines when they mount HFS disks. Data fork stored
in a file. Resource fork in subdirectory .HSResource with same
name. Finder info as one record in file .HSancillary. Separate .HSancillary
for each data fork directory.
.IP "Thursby Software Systems DAVE"
Allows Macintoshes to store Apple files on SMB servers.
Data fork stored in a file. Resource fork in subdirectory
resource.frk. Uses the AppleDouble format to store resource fork.
.IP "Services for Macintosh"
Format of files stored by NT Servers on NTFS filesystems. Data fork is
stored as "filename". Resource fork stored as a NTFS
.I stream
called "filename:AFP_Resource". The finder info is stored as a NTFS
.I stream
called "filename:Afp_AfpInfo". These streams are normally invisible to the
user.
.IP
Warning: mkisofs only partially supports the SFM format. If an HFS file
or folder stored on the NT server contains an
.I illegal
NT character in its name, then NT converts these characters to
.I Private Use Unicode
characters. The characters are: " * / < > ? \ | also a space or
period if it is the last character of the file name, character codes 0x01
to 0x1f (control characters) and Apple' apple logo.
.IP
Unfortunately, these private Unicode characters are not
readable by the mkisofs NT executable. Therefore any file or directory
name containing these characters will be ignored - including the contents of
any such directory.
.LP
.I mkisofs
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 FILE NAMES
section below.
.PP
When using the
.B \-apple
option, the TYPE and CREATOR are stored in the optional System Use or SUSP 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).
.PP
The Apple extensions require the resource fork to be stored as an ISO9660
.I associated
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
.PP
When using the
.B \-hfs
option, 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.
.PP
In most cases, it is better to use the
.B \-hfs
option instead of the
.B \-apple
option, 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 - important when the total size of the source files is
approaching 650MB.

.SH "HFS MACINTOSH FILE NAMES
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.
.PP
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 ":".
.PP
If mkisofs can't find an HFS filename, then it uses the Unix name, with
any %xx or :xx characters (xx == two hex digits) converted to a single
character code. If "xx" are not hex digits ([0-9a-fA-F]), then they are
left alone - although any remaining ":" is converted to "%" as colon
is the HFS directory separator. Care must be taken, as an ordinary Unix
file with %xx or :xx will also be converted. e.g.
.PP
.TS
l l 
l s
l l
l s
l l .
This:2fFile	converted to This/File
	
This:File	converted to This%File
	
This:t7File	converted to This%t7File
.TE
.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
If an HFS filename exists for a file, then mkisofs can use this name as
the starting point for the ISO9660, Joliet and Rock Ridge filenames using
the
.B \-mac-name
option. Normal Unix files without an HFS name will still use their Unix name.
e.g.
.PP
If a
.I MacBinary
(or
.I PC
.IR Exchange )
file is stored as 
.I someimage.gif.bin
on the Unix filesystem, but contains a HFS file called
.IR someimage.gif ,
then this is the name that would appear on the HFS part of the CD. However, as
mkisofs uses the Unix name as the starting point for the other names, then
the ISO9660 name generated will probably be 
.I SOMEIMAG.BIN
and the Joliet/Rock Ridge would be
.IR someimage.gif.bin .
Although the actual data (in this case) is a GIF image. This option will use
the HFS filename as the starting point and the ISO9660 name will probably be