Open Source .NET Development [Electronic resources] نسخه متنی

DESCRIPTION

mkisofs is effectively a pre-mastering program to generate an ISO9660/JOLIET/HFS hybrid file system.

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 file system 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 file system 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 file system unless the Joliet or HFS hybrid command-line options are given.

mkisofs can generate a true (or shared) HFS hybrid file system. 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 Extensions 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 later.

mkisofs takes a snapshot of a given directory tree and generates a binary image, which will correspond to an ISO9660 or HFS file system when written to a block device.

Each file written to the ISO9660 file system must have a filename in the 8.3 format (8 characters, period, 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. mkisofs generally tries to form correct names by forcing the Unix filename to uppercase and truncating as required, but often times this yields unsatisfactory results when 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~ -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 that 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 disk. The latest version of cdrecord is available from ftp://ftp.berlios.de/pub/cdrecord.

Also you should know that most CD writers are very particular about timing. Once you start to burn a disk, you cannot let the buffer empty before you are done, or you will end up with a corrupt disk. 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 file system. Multiple paths can be specified, and mkisofs will merge the files found in all of the specified path components to form the CD-ROM 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 CD-ROM image with names different than what they have in the source file system. 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 CD-ROM image.

foo/bar/=../old.lis

will include the file old.lis in the CD-ROM image at

/foo/bar/old.lis

while

foo/bar/xxx=../old.lis

will include the file old.lis in the CD-ROM 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 CD-ROM image - the directories do not need to appear in one of the paths. 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, the easiest solution is to create real directories in the path such that mkisofs doesn't have to invent them.

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.