mkisofs - create an hybrid ISO9660/JOLIET/HFS filesystem with optional Rock Ridge attributes.
mkisofs [ __-abstract__ ''FILE''? [ __-allow-lowercase__? [ __-allow-multidot__? [ __-biblio__ ''FILE''? [ __-cache-inodes__? [ __-no-cache-inodes__? [ __-b__ ''eltorito_boot_image''? [ __-eltorito-alt-boot__? [ __-B__ ''sparc_boot_image_list''? [ __-G__ ''generic_boot_image''? [ __-gui__? [ __-C__ ''#,#''? [ __-hard-disk-boot__? [ __-no-emul-boot__? [ __-no-boot__? [ __-boot-load-seg__? [ __-boot-load-size__? [ __-boot-info-table__? [ __-c__ ''boot_catalog''? [ __-check-oldnames__? [ __-check-session__ ''FILE''? [ __-copyright__ ''FILE''? [ __-A__ ''application_id''? [ __-f__? [ __-d__? [ __-D__? [ __-dir-mode__ ''mode''? [ __-file-mode__ ''mode''? [ __-gid__ ''gid''? [ __-hide__ ''glob''? [ __-hide-list__ ''file''? [ __-hidden__ ''glob''? [ __-hidden-list__ ''file''? [ __-hide-joliet__ ''glob''? [ __-hide-joliet-list__ ''file''? [ __-hide-joliet-trans-tbl__? [ __-hide-rr-moved__? [ __-iso-level__ ''level''? [ __-input-charset__ ''charset''? [ __-output-charset__ ''charset''? [ __-J__? [ __-jcharset__ ''charset''? [ __-l__? [ __-L__? [ __-log-file__ ''log_file''? [ __-max-iso9660-filenames__? [ __-M__ ''path? [ __-new-dir-mode__ ''mode''? [ __-nobak__? [ __-no-bak__? [ __-no-split-symlink-components__? [ __-no-split-symlink-fields__? [ __-pad__? [ __-no-pad__? [ __-path-list__ ''file''? [ __-p__ ''preparer''? [ __-print-size__? [ __-P__ ''publisher''? [ __-quiet__? [ __-r__? [ __-R__? [ __-relaxed-filenames__? [ __-sort__ ''sort file''? [ __-sysid__ ''ID''? [ __-T__? [ __-ucs-level__ ''level''? [ __-uid__ ''uid''? [ __-use-fileversion__? [ __-U__? [ __-no-iso-translate__? [ __-v__? [ __-V__ ''volid''? [ __-volset__ ''ID''? [ __-volset-size__ ''#''? [ __-volset-seqno__ ''#''? [ __-x__ ''path''? [ __-exclude-list__ ''file''? [ __-z__? [ __-m__ ''glob''? [ __-hfs__? [ __-map__ ''mapping_file''? [ __-magic__ ''magic_file''? [ __-probe__? [ __-no-desktop__? [ __-mac-name__? [ __-boot-hfs-file__ ''driver_file'' [[ __-part__? [ __-auto__ ''!AutoStart_file''? [ __-cluster-size__ ''size''? [ __-hide-hfs__ ''glob''? [ __-hide-hfs-list__ ''file''? [ __-hfs-volid__ ''hfs_volid''? [ __-icon-position__? [ __-root-info__ ''FILE'' [[ __-prep-boot__ ''FILE''? [ __-hfs-creator__ ''CREATOR''? [ __-hfs-type__ ''TYPE''? [ __-input-hfs-charset__ ''charset''? [ __-output-hfs-charset__ ''charset''? [ __-hfs-unlock__? [ __-hfs-bless__ ''folder_name''? [ __--cap__? [ __--netatalk__? [ __--double__? [ __--ethershare__? [ __--ushare__? [ __--exchange__? [ __--sgi__? [ __--xinet__? [ __--macbin__? [ __--single__? [ __--dave__? [ __--sfm__? -o filename pathspec [pathspec?
mkisofs is effectively a pre-mastering program to generate an ISO9660/JOLIET/HFS hybrid filesystem.
mkisofs is capable of generating the System Use Sharing Protocol records (SUSP) specified by the Rock Ridge Interchange Protocol. This is used to further describe the files in the iso9660 filesystem to a unix host, and provides information such as longer filenames, uid/gid, posix permissions, symbolic links, block and character devices.
If Joliet or HFS hybrid command line options are specified, mkisofs will create additional filesystem meta data for Joliet or HFS. The file content in this case refers to the same data blocks on the media. It will generate a pure ISO9660 filesystem unless the Joliet or HFS hybrid command line options are given.
mkisofs can generate a true (or shared ) 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 Hierarchical File System and is the native file system used on Macintosh computers.
As an alternative, mkisofs can generate the Apple Entensions to ISO9660 for each file. These extensions provide each file with CREATOR, TYPE and certain Finder Flags when accessed from a Macintosh. See the HFS MACINTOSH FILE FORMATS section below.
mkisofs takes a snapshot of a given directory tree, and generates a binary image which will correspond to an ISO9660 or HFS filesystem when written to a block device.
Each file written to the iso9660 filesystem must have a filename in the 8.3 format (8 characters, period, 3 characters, all upper case), 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. mkisofs generally tries to form correct names by forcing the unix filename to upper case and truncating as required, but often times this yields unsatisfactory results when there are cases where the truncated names are not all unique. mkisofs 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 have a 3 digit number as an extension (where the number is guaranteed to be unique). An example of this would be the files foo.bar and foo.bar.1 - the file foo.bar.1 would be written as FOO000.BAR;1 and the file foo.bar would be written as FOO.BAR;1
When used with various HFS options, mkisofs 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 HFS MACINTOSH FILE FORMATS section below for more about formats mkisofs supports.
Note that mkisofs 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 disk.
The cdrecord utility is a utility capable of burning an actual disc. The latest version of cdrecord is available from 
ftp://ftp.fokus.gmd.de/pub/unix/cdrecord
Also you should know that most cd writers are very particular about timing. Once you start to burn a disc, you cannot let their buffer empty before you are done, or you will end up with a corrupt disc. Thus it is critical that you be able to maintain an uninterrupted data stream to the writer for the entire time that the disc is being written.
pathspec is the path of the directory tree to be copied into the iso9660 filesystem. Multiple paths can be specified, and mkisofs will merge the files found in all of the specified path components to form the cdrom image.
If the option -graft-points 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 ../old.lis exists, and you wish to include it in the cdrom image.
foo/bar/=../old.lis
will include the file old.lis in the cdrom image at /foo/bar/old.lis, while
foo/bar/xxx=../old.lis
will include the file old.lis in the cdrom image at /foo/bar/xxx. The same sort of syntax can be used with directories as well. mkisofs 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 mkisofs. If you wish other permissions or owners of the intermediate directories, see -uid, -gid, -dir-mode, -file-mode and -new-dir-mode.
mkisofs will also run on Win9X/NT4 machines when compiled with Cygnus' cygwin (available from 
http://sourceware.cygnus.com/cygwin/). Therefore most references in this man page to Unix can be replaced with Win32 .
This violates the ISO9660 standard, but it happens to work on some systems. Use with caution.
This violates the ISO9660 standard, but it happens to work on many systems. Use with caution.
The implemented boot method is the boot method 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. For this reason, it should be usable for any OS that boots off a sparc system.
If the special filename ... is used, the actual and all following boot partitions are mapped to the previous partition. If mkisofs is called with -G image -B ... 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 disk is used for all architectures.
This violates the ISO9660 standard, but it happens to work on many systems. Use with caution.
This violates the ISO9660 standard, but it happens to work on many systems. Use with caution.
With level 1, files may only consist of one section and filenames are restricted to 8.3 characters.
With level 2, files may only consist of one section.
With level 3, no restrictions apply.
With all iso9660 levels all filenames are restricted to upper case letters, numbers and the underscore (_). The maximum filename length is restricted to 31 characters, the directory nesting level is restricted to 8 and the maximum path length is limited to 255 characters.
This violates the ISO9660 standard, but it happens to work on many systems. Use with caution.
mkisofs -o rom -m '*.o' -m core -m foobar
would exclude all files ending in ".o", called "core" or "foobar" to be copied to CDROM. Note that if you had a directory called "foobar" it too (and of course all its descendants) would be excluded.
NOTE: The -m and -x option description should both be updated, they are wrong. Both now work identical and use filename globbing. A file is excluded if either the last component matches or the whole path matches.
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, disks created with this option may cause a buffer overflow in the reading operating system. Use with extreme care.
This violates the ISO9660 standard, but no one really uses the version numbers anyway. Use with caution.
;-nobak :
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 one or more files that are located at the end of a track. They are usually present when the CD is written in Track at Once mode or when the disk is written as mixed mode CD where an audio track follows the data track.
To avoid problems with I/O error on the last file on the filesystem, the -pad option has been made the default.
cdblocks=` mkisofs -print-size -quiet ... `
mkisofs ... | cdrecord ... tsize=${cdblocks}s -
This violates the ISO9660 standard, but it happens to work on many systems. Use with caution.
This violates the ISO9660 standard, but it happens to work on many systems. Use with caution.
mkisofs -o cd -x /local/dir1 -x /local/dir2 /local
NOTE: The -m and -x option description should both be updated, they are wrong. Both now work identical and use filename globbing. A file is excluded if either the last component matches or the whole path matches.
mkisofs -o rom -hfs -hide-hfs '*.o' -hide-hfs foobar
would exclude all files ending in ".o" or called "foobar" from the HFS volume. Note that if you had a directory called "foobar" it too (and of course all its descendants) would be excluded. The glob can also be a path name relative to the source directories given on the command line. Example:
mkisofs -o rom -hfs -hide-hfs src/html src
would exclude just the file or directory called "html" from the "src" directory. Any other file or directory called "html" in the tree will not be excluded. Should be used with the -hide and/or -hide-joliet options. In order to match a directory name, make sure the pathname does not include a trailing '/' character.
mkisofs processes file names 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 UTF-32 , UTF-16 or UTF-8 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 it only supports a subset of all codes and that 16-bit characters are not compliant with the POSIX filesystem interface.
Modern UNIX operating systems use UTF-8 coding for filenames. This coding allows to use the complete Unicode code set. Each 32-bit character is represented by one or more 8-bit characters. If a character is coded in ISO-8859-1 (used in Central Europe and North America) is maps 1:1 to a Unicode character. Character codes that cannot be represented as a single byte in UTF-8 (typically if the value is > 0x7F) use escape sequences that map to more than one 8-bit character.
If all operating systems would use UTF-8 coding, mkisofs would not need to recode characters in file names. Unfortunately, Apple uses completely nonstandard codings and Microsoft uses a Unicode coding that is not compatible with the POSIX filename interface.
For all non UTF-8 coded operating systems, the actual character that each byte represents depends on the character set or codepage (which is the name used by Microsoft) used by the local operating system in use - the characters in a character set will reflect the region or natural language used by the user.
Usually character codes 0x00-0x1f are control characters, codes 0x20-0x7f are the 7 bit ASCII characters and (on PC's and Mac's) 0x80-0xff are used for other characters. Unfortunately even this does not follow ISO standards that reserve the range 0x80-0x9f for control characters and only allow 0xa0-0xff for other characters.
As there is 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 file name generated, say in central Europe, may not display the same character when viewed on a machine in, say eastern Europe.
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 and code 0xe9 on a UNIX system. Note while the codings used on a PC or Mac are nonstandard, Unicode codes this character as 0x00000000e9 which is basically the same value as the value used by most UNIX systems.
As long as not all operating systems and applications will use the Unicode character set as the basis for file names in a unique way, it may be necessary to specify which character set your file names use in and which character set the file names should appear on the CD.
There are four options to specify the character sets you want to use:
If the -J option is given, then the Unicode equivalents of the input character set will be used in the Joliet directory. Using the -jcharset option is the same as using the -input-charset and -J options.
There are a number of character sets built in to mkisofs . To get a listing, use mkisofs -input-charset help.
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.
http://www.unicode.org/Public/MAPPINGS The format of these files isColumn #1 is the input byte code (in hex as 0xXX) Column #2 is the Unicode (in hex as 0xXXXX) Rest of the line is ignored.
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.
Note that there is no support for 16 bit UNICODE (UTF-16) or 32 bit UNICODE (UTF-32) coding because this coding is not POSIX compliant. There should be support for UTF-8 UNICODE coding which is compatible to POSIX filenames and supported by moder UNIX implementations such as Solaris.
A 1:1 character set mapping can be defined by using the keyword default as the argument to any of the character set options. This is the behaviour of older (v1.12) versions of mkisofs .
The ISO9660 file names 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.
Any character that mkisofs can not convert will be replaced with a '_' character.
A Macintosh file has two properties associated with it which define which application created the file, the CREATOR and what data the file contains, the 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.
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 mapping file (the -map option) and/or using the magic number (usually a signature in the first few bytes) of a file (the -magic option). If both these options are given, then their order on the command line is important. If the -map option is given first, then a filename extension match is attempted before a magic number match. However, if the -magic option is given first, then a magic number match is attempted before a filename extension match.
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 .mkisofsrc file or using the -hfs-creator and/or -hfs-type options, otherwise the default CREATOR and TYPE are 'unix' and 'TEXT'.
The format of the mapping file is the same afpfile format as used by aufs . This file has five columns for the extension , file translation , CREATOR , TYPE and Comment . Lines starting with the '#' character are comment lines and are ignored. An example file would be like:
|s# Example filename mapping files |s#s |# 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"
Where:
The format of the magic file is almost identical to the magic(4)? file used by the Linux file(1) command - the routines for reading and decoding the magic file are based on the Linux file(1) command.
This file has four tab separated columns for the byte offset , type , test and message . Lines starting with the '#' character are comment lines and are ignored. An example file would be like:
|s# Example magic files |s#s |# 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/ 37\235/LZIV ZIVU standard unix compress |0/string/ 37\213/GNUz ZIVU gzip compressed data |0/string/%!/ASPS TEXT Postscript |0/string/ 04%!/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)
The format of the file is described in the magic(4)? man page. The only difference here is that for each entry in the magic file, the message for the initial offset 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.
Using the -magic option may significantly increase processing time as each file has to opened and read to find it's magic number.
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 .mkisofsrc file or by using the -hfs-creator and/or -hfs-type options.
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.
Other files can have their CREATOR and TYPE set from their file name extension (the -map option), or their magic number (the -magic option). If the default match is used in the mapping file, then these values override the default CREATOR and TYPE.
A full CREATOR/TYPE database can be found at http://www.angelfire.com/il/szekely/index.html
Macintosh files have two parts called the Data and 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.
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.
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 finder info ). Unfortunately, it seems that every software package that stores Macintosh files on Unix has chosen a completely different storage method.
The Apple/Unix formats that mkisofs (partially) supports are:
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 HFS MACINTOSH FILE NAMES section below.
When using the -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).
The Apple extensions require the resource fork to be stored as an ISO9660 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
When using the -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.
In most cases, it is better to use the -hfs option instead of the -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.
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.
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 ":".
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.
|This:2fFile|converted to This/File | |This:File|converted to This%File | |This:t7File|converted to This%t7File
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 mkisofs will attempt, where possible, to make a unique name by adding '_' characters to one of the filenames.
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 -mac-name option. Normal Unix files without an HFS name will still use their Unix name. e.g.
If a !MacBinary? (or PC Exchange ) file is stored as someimage.gif.bin on the Unix filesystem, but contains a HFS file called 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 SOMEIMAG.BIN and the Joliet/Rock Ridge would be 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 SOMEIMAG.GIF and the Joliet/Rock Ridge would be someimage.gif .
Using the -mac-name option will not currently work with the -T option - the Unix name will be used in the TRANS.TBL file, not the Macintosh name.
The character set used to convert any HFS file name to a Joliet/Rock Ridge file name defaults to cp10000 (Mac Roman). The character set used can be specified using the -input-hfs-charset option. Other built in HFS character sets are: cp10006 (!MacGreek?), cp10007 (!MacCyrillic?), cp10029 (!MacLatin2), cp10079 (!MacIcelandandic?) and cp10081 (!MacTurkish?).
Note: the character codes used by HFS file names 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 file names will be converted.
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 -mac-name option converts '/' to a '_' in Rock Ridge filenames.
If the Apple extensions are used, then only the ISO9660 filenames will appear on the Macintosh. However, as the Macintosh ISO9660 drivers can use Level 2 filenames, then you can use options like -allow-multidot without problems on a Macintosh - still take care over the names, for example this.file.name will be converted to THIS.FILE i.e. only have one '.', also filename abcdefgh will be seen as ABCDEFGH but abcdefghi will be seen as ABCDEFGHI. i.e. with a '.' at the end - don't know if this is a Macintosh problem or mkisofs/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...
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.
A custom folder icon is very similar - an invisible file called 'Icon\r' exits in the folder itself.
mount -t hfs /dev/fd0 /mnt/floppy
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 hdir -a hcopy -m Icon^V^M icon_dir/icon
mkisofs --macbin -o output source_dir icon_dir
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.
You may want to hide the icon files from the ISO9660 and Joliet trees.
To give a custom icon to a Joliet CD, follow the instructions found at: http://www.fadden.com/cdrfaq/faq03.html#[[3-21]
It may be possible to make the hybrid CD bootable on a Macintosh.
A bootable HFS CD requires an Apple CD-ROM (or compatible) driver, a bootable HFS partition and the necessary System, Finder, etc. files.
A driver can be obtained from any other Macintosh bootable CD-ROM using the apple_driver utility. This file can then be used with the -boot-hfs-file option.
The HFS partition (i.e. the hybrid disk in our case) must contain a suitable System Folder, again from another CD-ROM or disk.
For a partition to be bootable, it must have it's 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.
Therefore, the utility 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 mkisofs .
When the -boot-info-table option is given, mkisofs will modify the boot file specified by the -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.
The format of this table is as follows; all integers are in section 7.3.1 ("little endian") format.
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
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).
mkisofs looks for the .mkisofsrc file, first in the current working directory, then in the user's home directory, and then in the directory in which the mkisofs binary is stored. This file is assumed to contain a series of lines of the form 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.
mkisofs can also be configured at compile time with defaults for many of these fields. See the file defaults.h.
To create a vanilla ISO-9660 filesystem image in the file cd.iso , where the directory cd_dir will become the root directory if the CD, call:
% mkisofs -o cd.iso cd_dir
To create a CD with Rock Ridge extensions of the source directory cd_dir :
% mkisofs -o cd.iso -R cd_dir
To create a CD with Rock Ridge extensions of the source directory cd_dir where all files have at least read permission and all files are owned by root , call:
% mkisofs -o cd.iso -r cd_dir
To create a HFS hybrid CD with the Joliet and Rock Ridge extensions of the source directory cd_dir :
% mkisofs -o cd.iso -R -J -hfs cd_dir
To create a HFS hybrid CD from the source directory cd_dir that contains Netatalk Apple/Unix files:
% mkisofs -o cd.iso --netatalk cd_dir
To create a HFS hybrid CD from the source directory cd_dir , giving all files CREATOR and TYPES based on just their filename extensions listed in the file "mapping".:
% mkisofs -o cd.iso -map mapping cd_dir
To create a CD with the 'Apple Extensions to ISO9660', from the source directories cd_dir and another_dir. Files in all the known Apple/Unix format are decoded and any other files are given CREATOR and TYPE based on their magic number given in the file "magic":
% mkisofs -o cd.iso -apple -magic magic -probe \
cd_dir another_dir
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.
Current directory contains:
% ls -F README.hfs README.joliet README.unix cd_dir/
The following command puts the contents of the directory cd_dir on the CD along with the three README files - but only one will be seen from each of the three filesystems:
% mkisofs -o cd.iso -hfs -J -r -graft-points \
- hide README.hfs -hide README.joliet \
- hide-joliet README.hfs -hide-joliet README.unix \
- hide-hfs README.joliet -hide-hfs README.unix \
README=README.hfs README=README.joliet \
README=README.unix cd_dir
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.
There are probably all sorts of strange results possible with combinations of the hide options ...
mkisofs 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 mkisofs 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.
Eric Youngdale <ericy@gnu.ai.mit.edu> or <eric@andante.org> wrote the first versions (1993 ... 1998) of the mkisofs utility. The copyright for old versions of the mkisofs utility is held by Yggdrasil Computing, Incorporated. Joerg Schilling wrote the SCSI transport library and it's adaptation layer to mkisofs and newer parts (starting from 1999) of the utility, this makes mkisofs Copyright (C) 1999, 2000, 2001 Joerg Schilling.
HFS hybrid code Copyright (C) James Pearson 1997, 1998, 1999, 2000, 2001
libhfs code Copyright (C) 1996, 1997 Robert Leslie libfile code Copyright (C) Ian F. Darwin 1986, 1987, 1989, 1990, 1991, 1992, 1994, 1995.
Mkisofs may safely be installed suid root. This may be needed to allow mkisofs to read the previous session when creating a multi session image.
If mkisofs is creating a filesystem image with Rock Ridge attributes and the directory nesting level of the source directory tree is too much for ISO-9660, mkisofs will do deep directory relocation. This results in a directory called RR_MOVED in the root directory of the CD. You cannot avoid this directory.
This problem is present when reading old sessions while adding data in multi-session mode.
Any relocated deep directory is lost if the new session does not include the deep directory.
Repeat by: create first session with deep directory relocation then add new session with a single dir that differs from the old deep path.
There may be some other ones. Please, report them to the author.
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 Alpha above.
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 mkisofs will attempt, where possible, to make a unique name by adding '_' characters to one of the filenames.
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.
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:
mkisofs will be unable to decode "oldname". However, you can graft Apple/Unix encoded files or directories as long as you do not attempt to give them new names as above.
When creating an HFS volume with the multisession options, -M and -C , only files in the last session will be in the HFS volume. i.e. mkisofs can not add existing files from previous sessions to the HFS volume.
Symbolic links (as with all other non-regular files) are not added to the HFS directory.
Hybrid volumes may be larger than pure ISO9660 volumes containing the same data.
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 locked. The option -hfs-unlock 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.
Using the -mac-name option will not currently work with the -T option - the Unix name will be used in the TRANS.TBL file, not the Macintosh name.
Although mkisofs does not alter the contents of a file, if a binary file has it's TYPE set as 'TEXT', it may be read incorrectly on a Macintosh. Therefore a better choice for the default TYPE may be '????'
The -mac-boot-file option may not work at all...
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 msdos (not vfat ) when using Linux.
The SFM format is only partially supported - see HFS MACINTOSH FILE FORMATS section above.
It is not possible to use the the -sparc-boot or -generic-boot options with the -boot-hfs-file or -prep-boot options.
cdrecord(1), magic(5), apple_driver(8)?
Some sort of gui interface.
mkisofs is available as part of the cdrecord package from ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ hfsutils from ftp://ftp.mars.org/pub/hfs
other-cdwrite-request@lists.debian.org
cdwrite@lists.debian.org
Joerg Schilling
Seestr. 110
D-13353 Berlin
Germany
James Pearson
j.pearson@ge.ucl.ac.uk
If you have support questions, send them to:
cdrecord-support@berlios.de
or other-cdwrite@lists.debian.org
Of you definitely found a bug, send a mail to:
cdrecord-developers@berlios.de
or schilling@fokus.gmd.de
To subscribe, use:
__http://lists.berlios.de/mailman/listinfo/cdrecord-developers__
or __http://lists.berlios.de/mailman/listinfo/cdrecord-support__
4 pages link to mkisofs(8):
