mkisofs: create ISO9660/Joliet/HFS filesystem with optional Rock Ridge attributes

Command to display mkisofs manual in Linux: $ man 1 mkisofs

NAME

genisoimage - create ISO9660/Joliet/HFS filesystem with optional Rock Ridge attributes

SYNOPSIS

genisoimage[options][-ofilename]pathspec [pathspec ...]

DESCRIPTION

genisoimageis a pre-mastering program to generate ISO9660/Joliet/HFS hybridfilesystems.

genisoimageis capable of generating the System Use Sharing Protocol records (SUSP)specified by theRock Ridge Interchange Protocol.This is used to further describe thefiles in the ISO9660 filesystem to a Unix host, and provides information suchas long filenames, UID/GID, POSIX permissions, symbolic links, andblock and character device files.

If Joliet or HFS hybrid command line options are specified, genisoimagewill create the additional filesystem metadata needed for Joliet or HFS.Otherwisegenisoimagewill generate a pure ISO9660 filesystem.

genisoimagecan generate a true(orshared)HFS hybrid filesystem. The same files are seen as HFS files whenaccessed from a Macintosh and as ISO9660 files when accessed from other machines. HFS stands forHierarchical File Systemand is the native filesystem used on Macintosh computers.

As an alternative,genisoimagecan generate theApple Extensions to ISO9660for each file. These extensions provide each file with CREATOR, TYPE andcertain Finder flags when accessed from a Macintosh. See theHFS MACINTOSH FILE FORMATSsection below.

genisoimagetakes a snapshot of a given directory tree, and generates abinary image which will correspond to an ISO9660 and/or HFS filesystem whenwritten to a block device.

Each file written to the ISO9660 filesystem must have a filename in the 8.3format (up to 8 characters, period, up to 3 characters, all uppercase), evenif Rock Ridge is in use. This filename is used on systems that are not ableto make use of the Rock Ridge extensions (such as MS-DOS), and each filenamein each directory must be different from the other filenames in the samedirectory.genisoimagegenerally tries to form correct names by forcing the Unix filename touppercase and truncating as required, but often this yields unsatisfactoryresults when the truncated names are not all unique.genisoimageassigns weightings to each filename, and if two names that are otherwise thesame are found, the name with the lower priority is renamed to include a3-digit number (guaranteed to be unique). For example, the two filesfoo.barandfoo.bar.~1~could be rendered asFOO.BAR;1andFOO000.BAR;1.

When used with various HFS options,genisoimagewill attempt to recognise files stored in a number of Apple/Unix file formatsand will copy the data and resource forks as well as anyrelevant Finder information. See theHFS MACINTOSH FILE FORMATSsection below for more about formatsgenisoimagesupports.

Note thatgenisoimageis not designed to communicate with the writer directly. Most writershave proprietary command sets which vary from one manufacturer toanother, and you need a specialized tool to actually burn the disc.wodimis one such tool. The latest version ofwodimis available fromhttp://www.cdrkit.org/.

pathspecis the path of the directory tree to be copied into the ISO9660 filesystem.Multiple paths can be specified, andgenisoimagewill merge the files found in all of the specified path components toform the filesystem image.

If the option-graft-pointshas been specified, it is possible to graft the paths at points otherthan the root directory, and it is possible to graft files ordirectories onto the cdrom image with names different than what theyhave in the source filesystem. This is easiest to illustrate with acouple of examples. Let's start by assuming that a local file../old.lisexists, and you wish to include it in the cdrom image.

: foo/bar/=../old.lis

will includeold.lisin the cdrom image at/foo/bar/old.lis,while

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

will include old.lisin the cdrom image at/foo/bar/xxx.The same sort of syntax can be used with directories as well.genisoimagewill create any directories required such that the graftpoints exist on the cdrom image --- the directories do not need toappear 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 theperson runninggenisoimage.If you wish other permissions or owners ofthe intermediate directories, see-uid, -gid, -dir-mode, -file-mode and -new-dir-mode.

genisoimagewill also run on Windows machines when compiled with Cygnus' cygwin(available fromhttp://www.cygwin.com/).Therefore most references in this man page toUnixcan be replaced withWin32.

OPTIONS

Several options can be specified as defaults in a.genisoimagercconfiguration file, as well as on the command line. If a parameter isspecified in both places, the setting from the command line is used.For details on the format and possible locations of this file, seegenisoimagerc(5).

-abstract file

Specifies the abstract filename. There is space for 37 characters.Equivalent toABSTin the.genisoimagercfile.

-A application_id

Specifies a text string that will be written into the volume header.This should describe the application that will be on the disc. Thereis space for 128 characters. Equivalent toAPPIin the.genisoimagercfile.

-allow-limited-size

When processing files larger than 2GiB which cannot be easily represented inISO9660, add them with a shrunk visible file size to ISO9660 and with thecorrect visible file size to the UDF system. The result is an inconsistentfilesystem and users need to make sure that they really use UDF rather thanISO9660 driver to read a such disk. Implies enabling-udf.

-allow-leading-dots

-ldots

Allow ISO9660 filenames to begin with a period. Usually, a leading dot isreplaced with an underscore in order to maintain MS-DOS compatibility.
This violates the ISO9660 standard, but it happens to work on many systems.Use with caution.

-allow-lowercase

This options allows lowercase characters to appear in ISO9660 filenames.
This violates the ISO9660 standard, but it happens to work on some systems.Use with caution.

-allow-multidot

This options allows more than one dot to appear in ISO9660 filenames.A leading dot is not affected by this option, itmay be allowed separately using-allow-leading-dots.
This violates the ISO9660 standard, but it happens to work on many systems.Use with caution.

-biblio file

Specifies the bibliographic filename. There is space for 37 characters.Equivalent toBIBLin the.genisoimagercfile.

-cache-inodes

-no-cache-inodes

Enable or disable caching inode and device numbers to find hard linksto files. Ifgenisoimagefinds a hard link (a file with multiple names), the file will also behard-linked on the CD, so the file contents only appear once. Thishelps to save space.-cache-inodesis default on Unix-like operating systems, but-no-cache-inodesis default on some other systems such as Cygwin, because it is not safeto assume that inode numbers are unique on those systems. (Someversions of Cygwin create fake inode numbers using a weak hashingalgorithm, which may produce duplicates.) If two files have the sameinode number but are not hard links to the same file,genisoimage -cache-inodeswill not behave correctly.-no-cache-inodesis safe in all situations, but in that casegenisoimagecannot detect hard links, so the resulting CD image may be largerthan necessary.

-alpha-boot alpha_boot_image

Specifies the path and filename of the boot image to be used whenmaking an Alpha/SRM bootable CD. The pathname must be relative to thesource path specified togenisoimage.

-hppa-bootloader hppa_bootloader_image

Specifies the path and filename of the boot image to be used whenmaking an HPPA bootable CD. The pathname must be relative to thesource path specified togenisoimage.Other options are required, at the very least a kernel filename anda boot command line. See theHPPA NOTESsection below for more information.

-hppa-cmdline hppa_boot_command_line

Specifies the command line to be passed to the HPPA boot loader whenmaking a bootable CD. Separate the parameters with spaces orcommas. More options must be passed togenisoimage,at the very least a kernel filename and the boot loader filename.See theHPPA NOTESsection below for more information.

-hppa-kernel-32 hppa_kernel_32

-hppa-kernel-64 hppa_kernel_64

Specifies the path and filename of the 32-bit and/or 64-bit kernel imagesto be used when making an HPPA bootable CD. The pathnames must berelative to the source path specified togenisoimage.Other options are required, at the very least the boot loader filenameand the boot command line. See theHPPA NOTESsection below for more information.

-hppa-ramdisk hppa_ramdisk_image

Specifies the path and filename of the ramdisk image to be used whenmaking an HPPA bootable CD. The pathname must be relative to thesource path specified togenisoimage.This parameter is optional. Other options are required, at the veryleast a kernel filename and the boot command line. See theHPPA NOTESsection below for more information.

-mips-boot mips_boot_image

Specifies the path and filename of the boot image to be used whenmaking an SGI/big-endian MIPS bootable CD. The pathname must berelative to the source path specified togenisoimage.This option may be specified several times, to store up to 15 bootimages.

-mipsel-boot mipsel_boot_image

Specifies the path and filename of the boot image to be used whenmaking an DEC/little-endian MIPS bootable CD. The pathname must berelative to the source path specified togenisoimage.

-B img_sun4,img_sun4c,img_sun4m,img_sun4d,img_sun4e

-sparc-boot img_sun4,img_sun4c,img_sun4m,img_sun4d,img_sun4e

Specifies a comma-separated list of boot images that are needed to makea bootable CD for SPARC systems.Partition 0 is used for the ISO9660 image, the first image file is mappedto 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-Bor-sparc-boothas been specified, the first sector of the resulting image willcontain a Sun disk label. This disk label specifies slice 0 for theISO9660 image and slices 1 to 7 for the boot images thathave been specified with this option. Byte offsets 512 to 8191within each of the additional boot images must contain a primary bootthat works for the appropriate SPARC architecture. The rest of eachof the images usually contains a UFS filesystem used for the primarykernel boot stage.

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 ofthe Open Boot prom, so it should be usable for any OS for SPARC systems.For more information also see the NOTESsection below.

If the special filename...is used, the actual and all following boot partitions are mapped to theprevious partition. Ifgenisoimageis called with-G image -B ...all boot partitions are mapped to the partition that contains the ISO9660filesystem image and the generic boot image that is located in the first16 sectors of the disc is used for all architectures.

-G generic_boot_image

Specifies the path and filename of the generic boot image to be used when makinga generic bootable CD. The boot image will be placed on the first 16sectors of the CD, before the ISO9660 primary volume descriptor.If this option is used together with-sparc-boot,the Sun disk label will overlay the first 512 bytes of the genericboot image.

-b eltorito_boot_image

Specifies the path and filename of the boot image to be used when makingan El Torito bootable CD for x86 PCs. The pathname must be relative tothe source path specified togenisoimage.This option is required to make an El Torito bootable CD.The boot image must be exactly 1200 kB, 1440 kB or 2880 kB, andgenisoimagewill use this size when creating the output ISO9660 filesystem. The PCBIOS will use the image to emulate a floppy disk, so the first 512-bytesector should contain PC boot code. This will work, for example, ifthe boot image is a LILO-based boot floppy.

If the boot image is not an image of a floppy, you need to add either-hard-disk-boot or -no-emul-boot.If the system should not boot off the emulated disk, use-no-boot.

If-sorthas not been specified, the boot images are sortedwith 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.

-eltorito-alt-boot

Start with a new set of El Torito boot parameters. Up to 63 El Toritoboot entries may be stored on a single CD.

-hard-disk-boot

Specifies that the boot image used to create El Torito bootable CDs isa hard disk image. The image must begin with a master bootrecord that contains a single partition.

-no-emul-boot

Specifies that the boot image used to create El Torito bootable CDs isa "no emulation" image. The system will load and execute this image withoutperforming any disk emulation.

-no-boot

Specifies that the created El Torito CD should be marked as not bootable. Thesystem will provide an emulated drive for the image, but will boot offa standard boot device.

-boot-load-seg segment_address

Specifies the load segment address of the boot image for no-emulationEl Torito CDs.

-boot-load-size load_sectors

Specifies the number of "virtual" (512-byte) sectors to load inno-emulation mode. The default is to load the entire boot file. SomeBIOSes may have problems if this is not a multiple of 4.

-boot-info-table

Specifies that a 56-byte table with information of the CD-ROM layoutwill be patched in at offset 8 in the boot file. If this option isgiven, the boot file ismodified in the source filesystem,so make a copy of this file if it cannot be easily regenerated!See theEL TORITO BOOT INFO TABLEsection for a description of this table.

-C last_sess_start,next_sess_start

This option is needed to create a CD Extra or the image of a secondsession or a higher-level session for a multisession disc.-Ctakes two numbers separated by a comma. The first is the first sectorin 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 callingwodim -msinfo ...If-Cis used in conjunction with-M,genisoimagewill create a filesystem image that is intended to be a continuationof the previous session.If-Cis used without-M,genisoimagewill create a filesystem image that is intended to be used for a secondsession on a CD Extra. This is a multisession CD that holds audio datain the first session and an ISO9660 filesystem in the second session.

-c boot_catalog

Specifies the path and filename of the boot catalog, which is requiredfor an El Torito bootable CD. The pathname must be relative to the sourcepath specified togenisoimage.This file will be inserted into the output tree and not createdin the source filesystem, so besure the specified filename does not conflict with an existing file, orit will be excluded. Usually a name likeboot.catalogis chosen.

If-sorthas not been specified, the boot catalog sortedwith 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.

-check-oldnames

Check all filenames imported from the old session for compliance withthe 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.

-check-session file

Check all old sessions for compliance with actualgenisoimage ISO9660 file naming rules.This is a high-level option that combines-Mfile-C 0,0 -check-oldnames.For the parameter file,see the description of-M.

-copyright file

Specifies copyright information, typically a filename on the disc.There is space for 37 characters. Equivalent toCOPYin the.genisoimagercfile.

-d

Do not append a period to files that do not have one.
This violates the ISO9660 standard, but it happens to work on many systems.Use with caution.

-D

Do not use deep directory relocation, and instead just pack them in theway we see them.
If ISO9660:1999 has not been selected,this violates the ISO9660 standard, but it happens to work on many systems.Use with caution.

-dir-mode mode

Overrides the mode of directories used to create the image tomode,specified as 4 digits of permission bits as inchmod(1).This option automatically enables Rock Ridge extensions.

-dvd-video

Generate a DVD-Video compliant UDF filesystem. This is done by sorting theorder 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 uppercasecharacters only.

Note that in order to get a DVD-Video compliant filesystem image, youneed to prepare a DVD-Video compliant directory tree. This requires adirectoryVIDEO_TS(all caps) in the root directory of the resulting DVD, and usuallyanother directoryAUDIO_TS.VIDEO_TSneeds to include all needed files (filenames must be all caps) for acompliant DVD-Video filesystem.

-f

Follow symbolic links when generating the filesystem. When this option is notin use, symbolic links will be entered using Rock Ridge if enabled, otherwisethey will be ignored.

-file-mode mode

Overrides the mode of regular files used to create the image tomode,specified as 4 digits of permission bits as inchmod(1).This option automatically enables Rock Ridge extensions.

-gid gid

Overrides the group ID read from the source files to the value ofgid.Specifying this option automatically enables Rock Ridge extensions.

-gui

Switch the behaviour for a GUI. This currently makes the output more verbosebut may have other effects in the future.

-graft-points

Allow use of graft points for filenames. If this option is used, allfilenames are checked for graft points. The filename is divided at thefirst unescaped equal sign. All occurrences of `\' and `=' charactersmust be escaped with `\' if-graft-pointshas been specified.

-hide glob

Hide any files matchingglob,a shell wildcard pattern, from being seen in the ISO9660 or Rock Ridgedirectory.globmay match any part of the filename or path. Ifglobmatches a directory, the contents of that directory will be hidden.In order to match a directory name, make sure the pathname does not includea trailing `/' character.All the hidden files will still be written to the output CD image file.See also-hide-joliet,andREADME.hide.This option may be used multiple times.

-hide-list file

A file containing a list of shell wildcards to be hidden. See-hide.

-hidden glob

Add the hidden (existence) ISO9660 directory attribute for files anddirectories matchingglob,a shell wildcard pattern. This attribute will prevent the files frombeing shown by some MS-DOS and Windows commands.globmay match any part of the filename or path.In order to match a directory name, make sure the pathname does not includea trailing `/' character.This option may be used multiple times.

-hidden-list file

A file containing a list of shell wildcards to get the hiddenattribute. See-hidden.

-hide-joliet glob

Hide files and directories matchingglob,a shell wildcard pattern, from being seen in the Joliet directory.globmay match any part of the filename or path. Ifglobmatches a directory, the contents of that directory will be hidden.In order to match a directory name, make sure the pathname does not includea trailing `/' character.All the hidden files will still be written to the output CD image file.This option is usually used with-hide.See alsoREADME.hide.This option may be used multiple times.

-hide-joliet-list file

A file containing a list of shell wildcards to be hidden from theJoliet tree. See-hide-joliet.

-hide-joliet-trans-tbl

Hide theTRANS.TBLfiles from the Joliet tree.These files usually don't make sense in the Joliet world as they listthe real name and the ISO9660 name which may both be different from theJoliet name.

-hide-rr-moved

Rename the directoryRR_MOVEDto.rr_movedin the Rock Ridge tree.It seems to be impossible to completely hide theRR_MOVEDdirectory from the Rock Ridge tree.This option only makes the visible tree less confusing forpeople who don't know what this directory is for.If you need to have noRR_MOVEDdirectory at all, you should use-D.Note that if-Dhas been specified, the resulting filesystem is not ISO9660level-1 compliant and will not be readable on MS-DOS.See also theNOTESsection.

-input-charset charset

Input charset that defines the characters used in local filenames.To get a list of valid charset names, callgenisoimage -input-charset help.To get a 1:1 mapping, you may usedefaultas charset name. The default initial values arecp437on DOS-based systems andiso8859-1on all other systems. See theCHARACTER SETSsection below for more details.

-output-charset charset

Output charset that defines the characters that will be used in Rock Ridgefilenames. Defaults to the input charset. SeeCHARACTER SETSsection below for more details.

-iso-level level

Set the ISO9660 conformance level. Valid numbers are 1 to 4.

With level 1, files may only consist of one section and filenames arerestricted to 8.3 characters.

With level 2, files may only consist of one section.

With level 3, no restrictions (other than ISO-9660:1988) do apply.

With all ISO9660 levels from 1 to 3, all filenames are restricted touppercase letters, numbers and underscores (_). Filenames arelimited to 31 characters, directory nesting is limited to 8levels, and pathnames are limited to 255 characters.

Level 4 officially does not exist butgenisoimagemaps it to ISO-9660:1999, which is ISO9660 version 2.

With level 4, an enhanced volume descriptor with version numberand 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 nospecial meaning, filenames do not have version numbers,and filenames can be up to 207 characters long, or 197 characters ifRock Ridge is used.

When creating Version 2 images,genisoimageemits an enhanced volume descriptor, similar but not identical to aprimary volume descriptor. Be careful not to use broken softwareto make ISO9660 images bootable by assuming a second PVD copy and patching this putative PVD copy into an El Torito VD.

-J

Generate Joliet directory records in addition to regular ISO9660filenames. This is primarily useful when the discs are to be used onWindows machines. Joliet filenames are specified in Unicode and eachpath component can be up to 64 Unicode characters long.Note that Joliet is not a standard --- only Microsoft Windows and Linuxsystems can read Joliet extensions. For greater portability, considerusing both Joliet and Rock Ridge extensions.

-joliet-long

Allow Joliet filenames to be up to 103 Unicode characters, instead of64. This breaks the Joliet specification, but appears to work. Usewith caution.

-jcharset charset

A combination of-J -input-charsetcharset.See theCHARACTER SETSsection below for more details.

-l

Allow full 31-character filenames. Normally the ISO9660 filename will be in an8.3 format which is compatible with MS-DOS, even though the ISO9660 standardallows filenames of up to 31 characters. If you use this option, the disc maybe difficult to use on a MS-DOS system, but will work on most other systems.Use with caution.

-L

Outdated option; use-allow-leading-dotsinstead.

-jigdo-jigdo jigdo_file

Produce ajigdo.jigdometadata file as well as the filesystem image. See theJIGDO NOTESsection below for more information.

-jigdo-template template_file

Produce ajigdo.templatefile as well as the filesystem image. See theJIGDO NOTESsection below for more information.

-jigdo-min-file-size size

Specify the minimum size for a file to be listed in the.jigdofile. Default (and minimum allowed) is 1KB. See theJIGDO NOTESsection below for more information.

-jigdo-force-md5 path

Specify a file pattern where filesmustbe contained in the externally-supplied MD5 list as supplied by-md5-list.See theJIGDO NOTESsection below for more information.

-jigdo-exclude path

Specify a file pattern where files will not be listed in the.jigdofile. See theJIGDO NOTESsection below for more information.

-jigdo-map path

Specify a pattern mapping for the jigdo file(e.g.Debian=/mirror/debian).See theJIGDO NOTESsection below for more information.

-md5-list md5_file

Specify a file containing the MD5sums, sizes and pathnames of thefiles to be included in the.jigdofile. See theJIGDO NOTESsection below for more information.

-jigdo-template-compress algorithm

Specify a compression algorithm to use for template date. gzip andbzip2 are currently supported, and gzip is the default. See theJIGDO NOTESsection below for more information.

-log-file log_file

Redirect all error, warning and informational messages tolog_fileinstead of the standard error.

-m glob

Exclude files matchingglob,a shell wildcard pattern, from being written to CD-ROM.globmay match either the filename component or the full pathname.This option may be used multiple times. For example:

genisoimage -o rom -m'*.o'-m core -m foobar

would exclude all files ending in `.o', or calledcore or foobarfrom the image. Note that if you had a directory calledfoobar,it too (and of course all its descendants) would be excluded.

-exclude-list file

A file containing a list of shell wildcards to be excluded. See-m.

-max-iso9660-filenames

Allow ISO9660 filenames to be up to 37 characters long.This option enables-Nas the extra name space is taken from the space reserved forfile version numbers.
This violates the ISO9660 standard, but it happens to work on many systems.Although a conforming application needs to provide a buffer space of atleast 37 characters, discs created with this option may cause a bufferoverflow in the reading operating system. Use with extreme care.

-M path

-M device

-dev device

Specifies path to existing ISO9660 image to be merged. The alternate formtakes a SCSI device specifier that uses the same syntax as thedev=parameter ofwodim.The output of genisoimagewill be a new session which should get written to the end of theimage specified in-M.Typically this requires multisession capability for the CD recorderused to write the image. This option may only be used in conjunctionwith-C.

-N

Omit version numbers from ISO9660 filenames.
This violates the ISO9660 standard, but no one really uses theversion numbers anyway. Use with caution.

-new-dir-mode mode

Specify the mode, a 4-digit number as used inchmod(1),to use when creating new directories in the filesystem image. Thedefault is 0555.

-nobak

-no-bak

Exclude backup files files on the ISO9660 filesystem; that is,filenames that contain the characters `~' or `#' or end in.bak.These are typically backup files for Unix text editors.

-force-rr

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.

-no-rr

Do not use the Rock Ridge attributes from previous sessions.This may help to avoid problems whengenisoimagefinds illegal Rock Ridge signatures on an old session.

-no-split-symlink-components

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 driverhas a bug in reading split symlink components.

It is questionable whether this option is useful nowadays.

-no-split-symlink-fields

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 andSolaris 2.5.1 cdrom driver have a bug in reading split symlink fields(a `/' can be dropped).

It is questionable whether this option is useful nowadays.

-o filename

Specify the output file for the the ISO9660 filesystem image.This can be a disk file, a tape drive, or it can correspond directlyto the device name of the optical disc writer. If not specified, stdout isused. Note that the output can also be a block device for a regulardisk partition, in which case the ISO9660 filesystem can be mountednormally to verify that it was generated correctly.

-pad

Pad the end of the whole image by 150 sectors (300 kB). This option isenabled by default. If used in combination with-B,padding is inserted between the ISO9660 partition and the bootpartitions, such that the first boot partition startson a sector number that is a multiple of 16.

The padding is needed as many operating systems (e.g. Linux)implement read-ahead bugs in their filesystem I/O. These bugs result in readerrors on files that are located near the end of a track, particularlyif the disc is written in Track At Once mode, or where a CD audio trackfollows the data track.

-no-pad

Do not pad the end by 150 sectors (300 kB) and do not make the the boot partitionsstart on a multiple of 16 sectors.

-path-list file

A file containing a list ofpathspecdirectories and filenames to be added to the ISO9660 filesystem. This listof pathspecs are processed after any that appear on the command line. If theargument is-,the list is read from the standard input.

-P

Outdated option; use-publisherinstead.

-publisher publisher_id

Specifies a text string that will be written into the volume header.This should describe the publisher of the CD-ROM, usually with amailing address and phone number. There is space for 128 characters.Equivalent toPUBLin the.genisoimagercfile.

-p preparer_id

Specifies a text string that will be written into the volume header.This should describe the preparer of the CD-ROM, usually with a mailingaddress and phone number. There is space for 128 characters.Equivalent toPREPin the.genisoimagercfile.

-print-size

Print estimated filesystem size in multiples of the sector size (2048 bytes)and exit. This option is needed forDisk At Once mode and with some CD-R drives when piping directly intowodim,cases wherewodimneeds to know the size of the filesystem image in advance.Old versions ofmkisofswrote this information (among other information) to stderr.As this turns out to be hard to parse, the number without any other informationis now printed on stdouttoo.If you like to write a simple shell script, redirectstderrand catch the number fromstdout.This may be done with:

cdblocks=`genisoimage -print-size -quiet ...`

genisoimage ... | wodim ... tsize=${cdblocks}s -

-quiet

This makesgenisoimageeven less verbose. No progress output will be provided.

-R

Generate SUSP and RR records using the Rock Ridge protocol to further describethe files on the ISO9660 filesystem.

-r

This is like the -R option, but file ownership and modes are set tomore useful values. The uid and gid are set to zero, because they areusually only useful on the author's system, and not useful to theclient. All the file read bits are set true, so that files anddirectories are globally readable on the client. If any execute bit isset for a file, set all of the execute bits, so that executables areglobally executable on the client. If any search bit is set for adirectory, set all of the search bits, so that directories are globallysearchable on the client. All write bits are cleared, because thefilesystem will be mounted read-only in any case. If any of the specialmode bits are set, clear them, because file locks are not useful on aread-only filesystem, and set-id bits are not desirable for uid 0 orgid 0.When used on Win32, the execute bit is set onallfiles. This is a result of the lack of file permissions on Win32 and theCygwin POSIX emulation layer. See also-uid, -gid,-dir-mode, -file-modeand-new-dir-mode.

-relaxed-filenames

Allows ISO9660 filenames to include all 7-bit ASCII characters exceptlowercase letters.
This violates the ISO9660 standard, but it happens to work on many systems.Use with caution.

-root dir

Moves all files and directories intodirin the image. This is essentially thesame as using -graft-pointsand addingdirin front of every pathspec, but is easier to use.dirmay actually be several levels deep. It iscreated with the same permissions as other graft points.

-old-root dir

This option is necessary when writing a multisessionimage and the previous (or even older) session was written with-rootdir.Using a directory name not found in the previous sessioncausesgenisoimageto abort with an error.Without this option,genisoimagewould not be able to find unmodified files and wouldbe forced to write their data into the image once more.-rootand-old-rootare meant to be used together to do incremental backups.The initial session would e.g. use:genisoimage -root backup_1dirs.The next incremental backup withgenisoimage -root backup_2 -old-root backup_1dirswould take another snapshot of these directories. The firstsnapshot would be found inbackup_1,the second one inbackup_2,but only modified or new files need to be writteninto the second session.Without these options, new files would be added and old ones would bepreserved. But old ones would be overwritten if the file wasmodified. Recovering the files by copying the whole directory backfrom CD would also restore files that were deletedintentionally. Accessing several older versions of a file requiressupport by the operating system to choose which sessions are to bemounted.

-sort sort_file

Sort file locations on the media. Sorting is controlled by a file thatcontains pairs of filenames and sorting offset weighting.If the weighting is higher, the file will be located closer to thebeginning of the media, if the weighting is lower, the file will be locatedcloser to the end of the media. There must be only one space or tabscharacter between the filename and theweight and the weight must be the last characters on a line. The filenameis taken to include all the characters up to, but not including the lastspace or tab character on a line. This is to allow for space characters tobe in, or at the end of a filename.This option doesnotsort the order of the filenames that appearin the ISO9660 directory. It sorts the order in which the file data iswritten to the CD image, which is useful in order to optimize thedata layout on a CD. SeeREADME.sortfor more details.

-sparc-boot img_sun4,img_sun4c,img_sun4m,img_sun4d,img_sun4e

See-Babove.

-sparc-label label

Set the Sun disk label name for the Sun disk label that is created with-sparc-boot.

-split-output

Split the output image into several files of approximately 1 GB each.This helps to create DVD-sized ISO9660 images on operating systems withoutlarge file support.wodimwill concatenate more than one file into a single track if writing to a DVD.To make-split-outputwork,-o filenamemust be specified. The resulting output images will be named:filename_00, filename_01, filename_02....

-stream-media-size #

Select streaming operation and set the media size to # sectors.This allows you to pipe the output of thetar(1)program intogenisoimageand to create an ISO9660 filesystem without the need of an intermediatetar archive file. If this option has been specified,genisoimagereads from stdin and creates a file with the nameSTREAM.IMG.The maximum size of the file (with padding) is 200 sectors less than the specified media size. If -no-padhas been specified, the file size is 50 sectors less than the specified media size.If the file is smaller,genisoimagewill write padding. This may take awhile.

The option -stream-media-sizecreates simple ISO9660 filesystems only and may not used together with multisessionor hybrid filesystem options.

-stream-file-name name

Reserved for future use.

-sunx86-boot UFS_img,,,AUX1_img

Specifies a comma-separated list of filesystem images that are needed to makea bootable CD for Solaris x86 systems.

Note that partition 1 is used for the ISO9660 image and that partition 2 isthe 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 x86partition table could support up to 16 partitions), so it is impossibleto specify more than 6 partition images.This option is required to make a bootable CD for Solaris x86 systems.

If-sunx86-boothas been specified, the first sector of the resulting image willcontain a PC fdisk label with a Solaris type 0x82 fdisk partition thatstarts at offset 512 and spans the whole CD.In addition, for the Solaris type 0x82 fdisk partition, there is aSVr4 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 forthe ISO9660 image.Slice 2 spans the whole CD slice 3 ... slice 7 may be used for additionalfilesystem images that have been specified with this option.

A Solaris x86 boot CD uses a 1024 byte sized primary boot that uses theEl-Torito no-emulationboot mode and a secondary generic boot that is in CD sectors 1..15.For this reason, both-b bootimage -no-emul-bootand-G genbootmust be specified.

-sunx86-label label

Set the SVr4 disk label name for the SVr4 disk label that is created with-sunx86-boot.

-sysid ID

Specifies the system ID. There is space for 32 characters.Equivalent toSYSIin the.genisoimagercfile.

-T

Generate a fileTRANS.TBLin each directory on the CD-ROM, which can be usedon non-Rock Ridge-capable systems to help establish the correct filenames.There is also information present in the file that indicates the major andminor numbers for block and character devices, and each symlink has the name ofthe link file given.

-table-name table_name

Alternative translation table filename (see above). Implies-T.If you are creating a multisession image you must use the same nameas in the previous session.

-ucs-level level

Set Unicode conformance level in the Joliet SVD. The default level is 3.It may be set to 1..3 using this option.

-udf

Include UDF filesystem support in the generated filesystem image. UDFsupport is currently in alpha status and for this reason, it is notpossible to create UDF-only images. UDF data structures are currentlycoupled to the Joliet structures, so there are many pitfalls with thecurrent implementation. There is no UID/GID support, there is no POSIXpermission support, there is no support for symlinks. Note that UDFwastes the space from sector ~20 to sector 256 at the beginning of thedisc in addition to the space needed for real UDF data structures.

-uid uid

Overrides the uid read from the source files to the value ofuid.Specifying this option automatically enables Rock Ridge extensions.

-use-fileversion

The option -use-fileversionallowsgenisoimageto use file version numbers from the filesystem.If the option is not specified, genisoimagecreates a version number of 1 for all files.File versions are strings in the range ;1to;32767This option is the default on VMS.

-U

Allows "untranslated" filenames, completely violating the ISO9660 standardsdescribed above. Enables the following flags:-d -l -N -allow-leading-dots -relaxed-filenames-allow-lowercase -allow-multidot -no-iso-translate.Allows more than one `.' character in the filename, as well asmixed-case filenames. This is useful on HP-UX, where the built-incdfsfilesystem does not recognize any extensions. Use with extreme caution.

-no-iso-translate

Do not translate the characters `#' and `~' which are invalid for ISO9660 filenames.Although invalid, these characters are often used by Microsoft systems.
This violates the ISO9660 standard, but it happens to work on many systems.Use with caution.

-V volid

Specifies the volume ID (volume name or label) to be written into themaster block. There is space for 32 characters. Equivalent toVOLIin the.genisoimagercfile. The volume ID is used as the mount point by the Solaris volumemanager and as a label assigned to a disc on various other platformssuch as Windows and Apple Mac OS.

-volset ID

Specifies the volume set ID. There is space for 128 characters.Equivalent toVOLSin the.genisoimagercfile.

-volset-size #

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 offiles is recorded.

Volume Sets are not intended to be used to create a set numbered CDsthat 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 notfit on a single volume.Each volume of a Volume Set contains a description of all the directoriesand files that are recorded on the volumes where the sequence numbersare less than, or equal to, the assigned Volume Set Size of the currentvolume.

genisoimagecurrently does not support a-volset-sizethat is larger than 1.

The option-volset-sizemust be specified before-volset-seqnoon each command line.

-volset-seqno #

Sets the volume set sequence number to #.The volume set sequence number is the index number of the currentCD in a CD set.The option-volset-sizemust be specified before-volset-seqnoon each command line.

-v

Verbose execution. If given twice on the command line, extra debug informationwill be printed.

-x glob

Identical to-mglob.

-z

Generate specialRRIPrecords for transparently compressed files.This is only of use and interest for hosts that support transparentdecompression, such as Linux 2.4.14 or later. You must specify-R or -rto enable Rock Ridge, and generate compressed files using themkzftreeutility before runninggenisoimage.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 callmkzftreeby hand to decompress the files.

HFS OPTIONS

-hfs

Create an ISO9660/HFS hybrid CD. This option should be used in conjunctionwith the-map,-magicand/or the variousdouble dashoptions given below.

-apple

Create an ISO9660 CD with Apple's extensions. Similar to-hfs,except that the Apple Extensions to ISO9660 are added instead ofcreating an HFS hybrid volume.Former genisoimageversions did include Rock Ridge attributes by default if -applewas specified. This versions ofgenisoimagedoes not do this anymore. If you like to have Rock Ridge attributes,you need to specify this separately.

-map mapping_file

Use themapping_fileto set the CREATOR and TYPE information for a file based on thefilename's extension. A filename is mapped only if it is not one of the know Apple/Unix file formats. See theHFS CREATOR/TYPEsection below.

-magic magic_file

The CREATOR and TYPE information is set by using a file'smagic number(usually the first few bytes of a file). Themagic_fileis only used if a file is not one of the known Apple/Unix file formats, orthe filename extension has not been mapped using-map.See the HFS CREATOR/TYPEsection below for more details.

-hfs-creator creator

Set the default CREATOR for all files. Must be exactly 4 characters. See theHFS CREATOR/TYPEsection below for more details.

-hfs-type type

Set the default TYPE for all files. Must be exactly 4 characters. See theHFS CREATOR/TYPEsection below for more details.

-probe

Search the contents of files for all the known Apple/Unix file formats.See theHFS MACINTOSH FILE FORMATSsection below for more about these formats.However, the only way to check forMacBinaryandAppleSinglefiles is to open and read them, so this option mayincrease processing time. It is better to use one or moredouble dashoptions given below if the Apple/Unix formats in use are known.

-no-desktop

Do not create (empty) Desktop files. New HFS Desktop files will be createdwhen the CD is used on a Macintosh (and stored in the System Folder).By default, empty Desktop files are added to the HFS volume.

-mac-name

Use the HFS filename as the starting point for the ISO9660, Joliet andRock Ridge filenames. See theHFS MACINTOSH FILENAMESsection below for more information.

-boot-hfs-file driver_file

Installs thedriver_filethatmaymake the CD bootable on a Macintosh. See theHFS BOOT DRIVERsection below. (Alpha).

-part

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 theCD-ROM to be able to recognize a hybrid CD-ROM.

-auto AutoStart_file

Make the HFS CD use the QuickTime 2.0 Autostart feature to launch anapplication or document. The given filename must be the name of a document orapplication located at the top level of the CD. The filename must be lessthan 12 characters. (Alpha).

-cluster-size size

Set the size in bytes of the cluster or allocation units of PC Exchangefiles. Implies--exchange.See theHFS MACINTOSH FILE FORMATSsection below.

-hide-hfs glob

Hideglob,a shell wildcard pattern, from the HFS volume. The file or directorywill still exist in the ISO9660 and/or Joliet directory.globmay match any part of the filename. Multiple globs may be excluded.Example:

genisoimage -o rom -hfs -hide-hfs'*.o'-hide-hfs foobar

would exclude all files ending in `.o' or calledfoobarfrom the HFS volume. Note that if you had a directory calledfoobar,it too (and of course all its descendants) would be excluded. Theglobcan also be a path name relative to the source directories given on thecommand line. Example:

genisoimage -o rom -hfs -hide-hfs src/html src

would exclude just the file or directory calledhtmlfrom thesrcdirectory. Any other file or directory calledhtmlin the tree will not be excluded. Should be used with-hideand/or-hide-joliet.In order to match a directory name, make sure the pattern does notinclude a trailing `/' character. SeeREADME.hidefor more details.

-hide-hfs-list file

Specify a file containing a list of wildcard patterns to be hidden as in-hide-hfs.

-hfs-volid hfs_volid

Volume name for the HFS partition. This is the name that isassigned to the disc on a Macintosh and replaces thevolidused with-V.

-icon-position

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 Macintoshdesktop. Folder location and size on screen, its scroll positions, folderView (view as Icons, Small Icons, etc.) are also preserved.(Alpha).

-root-info file

Set the location, size on screen, scroll positions, folder View etc. for theroot folder of an HFS volume. SeeREADME.rootinfofor more information. (Alpha)

-prep-boot file

PReP boot image file. Up to 4 are allowed. SeeREADME.prep_bootfor more information. (Alpha)

-chrp-boot

Add CHRP boot header.

-input-hfs-charset charset

Input charset that defines the characters used in HFS filenames whenused with-mac-name.The default charset iscp10000(Mac Roman). See theCHARACTER SETSandHFS MACINTOSH FILENAMESsections below for more details.

-output-hfs-charset charset

Output charset that defines the characters that will be used in the HFSfilenames. Defaults to the input charset. See theCHARACTER SETSsection below for more details.

-hfs-unlock

By default,genisoimagewill create an HFS volume that is locked.This option leaves the volume unlocked so that other applications (e.g.hfsutils)can modify the volume. See theHFS PROBLEMS/LIMITATIONSsection below for warnings about using this option.

-hfs-bless folder_name

"Bless" the given directory (folder). This is usually the System Folderand is used in creating HFS bootable CDs. The name of the directory mustbe the whole path name asgenisoimagesees it. E.g., if the given pathspec is./cddataand the required folder is calledSystem Folder,the whole path name is"/cddata/System Folder"(remember to use quotes if the name contains spaces).

-hfs-parms parameters

Override certain parameters used to create the HFS filesystem. Unlikely tobe used in normal circ*mstances. See thelibhfs_iso/hybrid.hsource file for details.

--cap

Look for AUFS CAP Macintosh files. Search for CAP Apple/Unix file formatsonly. Searching for the other possible Apple/Unix file formats is disabled,unless otherdouble dashoptions are given.

--netatalk

Look for NETATALK Macintosh files

--double

Look for AppleDouble Macintosh files

--ethershare

Look for Helios EtherShare Macintosh files

--ushare

Look for IPT UShare Macintosh files

--exchange

Look for PC Exchange Macintosh files

--sgi

Look for SGI Macintosh files

--xinet

Look for XINET Macintosh files

--macbin

Look for MacBinary Macintosh files

--single

Look for AppleSingle Macintosh files

--dave

Look for Thursby Software Systems DAVE Macintosh files

--sfm

Look for Microsoft's Services for Macintosh files (NT only) (Alpha)

--osx-double

Look for Mac OS X AppleDouble Macintosh files

--osx-hfs

Look for Mac OS X HFS Macintosh files

CHARACTER SETS

genisoimageprocesses filenames in a POSIX-compliant way as strings of 8-bit characters.To represent all codings for all languages, 8-bit characters are notsufficient. Unicode or ISO-10646define character codings that need at least 21 bits to represent allknown languages. They may be represented withUTF-32, UTF-16 or UTF-8coding. UTF-32 uses a plain 32-bit coding but seems to be uncommon.UTF-16 is used by Microsoft with Win32 with the disadvantage that16-bit characters are not compliant with the POSIX filesysteminterface.

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 inISO-8859-1(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 in7-Bit ASCII(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 thanone 8-bit character.

If all operating systems used UTF-8,genisoimagewould not need to recode characters in filenames.Unfortunately, Apple uses completely nonstandard codings and Microsoftuses a Unicode coding that is not compatible with the POSIX filenameinterface.

For all non-UTF-8-coded operating systems, the actual characterthat each byte represents depends on thecharacter setorcodepage(the name used by Microsoft)used by the local operating system --- the characters in a characterset will reflect the region or natural language set by the user.

Usually character codes 0x00-0x1f are control characters, codes 0x20-0x7fare the 7-bit ASCII characters and (on PCs and Macs) 0x80-0xff are usedfor other characters.

As there are a lot more than 256 characters/symbols in use, only a smallsubset are represented in a character set. Therefore the same character codemay represent a different character in different character sets. So a filenamegenerated, say in central Europe, may not display the same characterwhen viewed on a machine in, say eastern Europe.

To make matters more complicated, different operating systems usedifferent character sets for the region or language. For example, thecharacter 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.

As long as not all operating systems and applications use the samecharacter set as the basis for filenames, it may benecessary to specify which character set your filenames use in and whichcharacter set the filenames should appear on the CD.

There are four options to specify the character sets you want to use:

-input-charset: Defines the local character set you are using on your host machine.Any character set conversions that take place will use this characterset as the starting point. The default input character sets arecp437on MS-DOS-based systems andiso8859-1on all other systems. If-Jis given, the Unicode equivalents of the input character setwill be used in the Joliet directory.-jcharsetis the same as-input-charset -J.
-output-charset: Defines the character set that will be used with for the Rock Ridge nameson the CD. Defaults to the input character set.
-input-hfs-charset: Defines the HFS character set used for HFS filenames decoded fromany of the various Apple/Unix file formats. Only useful when used with-mac-name.See theHFS MACINTOSH FILENAMESfor more information. Defaults tocp10000(Mac Roman).
-output-hfs-charset: Defines the HFS character set used to create HFS filenames from the inputcharacter set in use. In most cases this will be from the character setgiven with-input-charset.Defaults to the input HFS character set.

There are a number of character sets built in togenisoimage.To get a listing, use-input-charset help.This list doesn't include the charset derived from the current locale,ifgenisoimageis built withiconvsupport.

Additional character sets can be read from file for any of the characterset options by giving a filename as the argument to the options. The givenfile will only be read if its name does not match one of the built-incharacter sets.

The format of the character set files is the same as the mapping filesavailable fromhttp://www.unicode.org/Public/MAPPINGS.This format is:

: Column #1 is the input byte code (in hex as 0xXX)
Column #2 is the Unicode (in hex as 0xXXXX)
The rest of the line is ignored.

Any blank line, line without two (or more) columns in the above formator comments lines (starting with the # character) are ignored without anywarnings. Any missing input code is mapped to Unicode character 0x0000.

HFS CREATOR/TYPE

A Macintosh file has two properties associated with it which definewhich application created the file, theCREATORand what data the file contains, theTYPE.Both are (exactly) 4 letter strings. Usually thisallows a Macintosh user to double-click on a file and launch the correctapplication etc. The CREATOR and TYPE of a particular file can be found byusing something like ResEdit (or similar) on a Macintosh.

The CREATOR and TYPE information is stored in all the various Apple/Unixencoded files.For other files it is possible to base the CREATOR and TYPE on thefilename's extension using amappingfile (with-map)and/or using themagic number(usually asignaturein the first few bytes) of a file (with-magic).If both these options are given, their order on the commandline is significant. If-mapis given first, a filename extension match is attemptedbefore a magic number match. However, if-magicis given first, a magic number match is attempted before afilename extension match.

If a mapping or magic file is not used, or no match is found, the defaultCREATOR and TYPE for all regular files can be set by using entries in the .genisoimagercfile or using-hfs-creatorand/or-hfs-type,otherwise the default CREATOR and TYPE areUnix and TEXT.

The format of themappingfile is the sameafpfileformat as used byaufs.This file has five columns for theextension,file translation,CREATOR,TYPE andComment.Lines starting with the `#' character arecomment lines and are ignored. An example file would be like:

# 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"

Where:

: The first columnEXTNdefines the Unix filename extension to bemapped. The default mapping for any filename extension that doesn'tmatch is defined with the `*' character.
: TheXlatecolumn defines the type of text translation between the Unix andMacintosh file it is ignored bygenisoimage,but is kept to be compatible withaufs(1).Although genisoimagedoes not alter the contents of a file, if a binary file has its TYPEset asTEXT, it maybe read incorrectly on a Macintosh. Therefore a better choice for thedefault TYPE may be????.
: TheCREATORandTYPEkeywords must be 4 characters long and enclosed in single quotes.
: The comment field is enclosed in double quotes --- it is ignored bygenisoimage,but is kept to be compatible with aufs.

The format of themagicfile is almost identical to themagic(5)file used by thefile(1)command.

This file has four tab-separated columns for thebyte offset,type,testandmessage.Lines starting with the `#' character arecomment lines and are ignored. An example file would be like:

# 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)

The format of the file is described inmagic(5).The only difference here is that for each entry in the magic file, themessagefor the initial offset must be be 4 characters for the CREATOR followedby 4 characters for the TYPE --- white space isoptional between them. Any other characters on this line are ignored.Continuation lines (starting with a `>') are also ignored, i.e., onlythe initial offset lines are used.

Using-magicmay significantly increase processing time as each file has to openedand read to find its magic number.

In summary, for all files, the default CREATOR isUnixand the default TYPE isTEXT.These can be changed by using entries in the.genisoimagercfile or by using-hfs-creatorand/or-hfs-type.

If the a file is in one of the known Apple/Unix formats (and the formathas been selected), the CREATOR and TYPE are taken from the valuesstored in the Apple/Unix file.

Other files can have their CREATOR and TYPE set from their filenameextension (with-map),or their magic number (with-magic).If the default match is used in themappingfile, these values override the default CREATOR and TYPE.

A full CREATOR/TYPE database can be found at http://www.angelfire.com/il/szekely/.

HFS MACINTOSH FILE FORMATS

Macintosh files have two parts called theDataandResource fork.Either may be empty. Unix (and many other OSs) can onlycope with files having one part (or fork). To add to this, Macintosh fileshave a number of attributes associated with them --- probably the mostimportant are the TYPE and CREATOR. Again, Unix has no concept of thesetypes of attributes.

E.g., a Macintosh file may be a JPEG image where the image is stored in theData fork and a desktop thumbnail stored in the Resource fork. It is usuallythe information in the data fork that is useful across platforms.

Therefore to store a Macintosh file on a Unix filesystem, a way has to befound to cope with the two forks and the extra attributes (which arereferred to as theFinder info).Unfortunately, it seems that every software package that stores Macintoshfiles on Unix has chosen a completely different storage method.

The Apple/Unix formats thatgenisoimage(partially) supports are:

CAP AUFS format: Data fork stored in a file. Resource fork in subdirectory.resourcewith same filename as data fork. Finder info in subdirectory.finderinfowith same filename.
AppleDouble/Netatalk: Data fork stored in a file. Resource fork stored in a file withsame name prefixed with `%'. Finder info also stored in same`%' file. Netatalk uses the same format, but the resourcefork/Finder info stored in subdirectory.AppleDoublewith same filename as data fork.
AppleSingle: Data structures similar to above, except both forks and Finderinfo are stored in one file.
Helios EtherShare: Data fork stored in a file. Resource fork and Finder info together insubdirectory.rsrcwith same filename as data fork.
IPT UShare: Like the EtherShare format, but the Finder infois stored slightly differently.
MacBinary: Both forks and Finder info stored in one file.
Apple PC Exchange: Used by Macintoshes to store Apple files on DOS (FAT) disks.Data fork stored in a file. Resource fork in subdirectoryresource.frk (or RESOURCE.FRK).Finder info as one record in filefinder.dat (or FINDER.DAT).Separatefinder.datfor each data fork directory.
: Note: genisoimageneeds to know the native FAT cluster size of the disk that the PC Exchangefiles are on (or have been copied from). This size is given by-cluster-size.The cluster or allocation size can be found by using the DOS utilitychkdsk.
: 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 typemsdos(notvfat)when using Linux.
SGI/XINET: Used by SGI machines when they mount HFS disks. Data fork storedin a file. Resource fork in subdirectory.HSResourcewith same filename. Finder info as one record in file.HSancillary. Separate .HSancillaryfor each data fork directory.
Thursby Software Systems DAVE: Allows Macintoshes to store Apple files on SMB servers.Data fork stored in a file. Resource fork in subdirectoryresource.frk.Uses the AppleDouble format to store resource fork.
Services for Macintosh: Format of files stored by NT Servers on NTFS filesystems. Data fork isstored asfilename.Resource fork stored as a NTFS stream calledfilename:AFP_Resource.The Finder info is stored as a NTFS stream calledfilename:Afp_AfpInfo.NTFS streams are normally invisible to the user.
: Warning:genisoimageonly partially supports the SFM format. If an HFS fileor folder stored on the NT server contains an illegalNT character in its name, NT converts these characters toPrivate Use Unicodecharacters. The characters are: " * / < > ? \ | and a space orperiod if it is the last character of the filename, character codes 0x01to 0x1f (control characters) and Apple's apple logo.
: Unfortunately, these private Unicode characters are not readable by thegenisoimageNT executable. Therefore any file or directoryname containing these characters will be ignored --- including the contents ofany such directory.
Mac OS X AppleDouble: When HFS/HFS+ files are copied or saved by Mac OS X on to a non-HFSfilesystem (e.g. UFS, NFS etc.), the files are stored in AppleDouble format.Data fork stored in a file. Resource fork stored in a file withsame name prefixed with `._'. Finder info also stored in same `._' file.
Mac OS X HFS (Alpha): Not really an Apple/Unix encoding, but actual HFS/HFS+ files on a Mac OS Xsystem. Data fork stored in a file. Resource fork stored in a pseudo filewith the same name with the suffix/rsrc.The Finder info is only available via a Mac OS X library call.
: See alsoREADME.macosx.
: Only works when used on Mac OS X.
: If a file is found with a zerolength resource fork and empty finderinfo, it is assumed not to haveany Apple/Unix encoding --- therefore a TYPE and CREATOR can be set usingother methods.

genisoimagewill attempt to set the CREATOR, TYPE, date and possibly other flags fromthe finder info. Additionally, if it exists, the Macintosh filename is setfrom the finder info, otherwise the Macintosh name is based on the Unixfilename --- see theHFS MACINTOSH FILENAMESsection below.

When using-apple,the TYPE and CREATOR are stored in the optional System Use orSUSPfieldin the ISO9660 Directory Record --- in much the same way as the Rock Ridgeattributes are. In fact to make life easy, the Apple extensions are addedat the beginning of the existing Rock Ridge attributes (i.e., to get the Appleextensions you get the Rock Ridge extensions as well).

The Apple extensions require the resource fork to be stored as an ISO9660associatedfile. This is just like any normal file stored in the ISO9660 filesystemexcept that the associated file flag is set in the Directory Record (bit2). This file has the same name as the data fork (the file seen bynon-Apple machines). Associated files are normally ignored by other OSs

When using-hfs,the TYPE and CREATOR plus other finder info, are stored in a separateHFS directory, not visible on the ISO9660 volume. The HFS directory referencesthe same data and resource fork files described above.

In most cases, it is better to use-hfsinstead of-apple,as the latter imposes the limited ISO9660 characters allowed infilenames. However, the Apple extensions do give the advantage that thefiles are packed on the disk more efficiently and it may be possible to fit more files on a CD.

HFS MACINTOSH FILENAMES

Where possible, the HFS filename that is stored with an Apple/Unix fileis used for the HFS part of the CD. However, not all the Apple/Unixencodings store the HFS filename with the finderinfo. In these cases,the Unix filename is used --- with escaped special characters. Specialcharacters include `/' and characters with codes over 127.

AUFS escapes these characters by using `:' followed by the character codeas two hex digits. Netatalk and EtherShare have a similar scheme, but uses`%' instead of a `:'.

Ifgenisoimagecannot find an HFS filename, it uses the Unix name, with any%xx or :xxcharacters(xxare two hex digits) converted to a single character code. Ifxxare not hex digits ([0-9a-fA-F]), they areleft alone --- although any remaining `:' is converted to `%', as `:'is the HFS directory separator. Care must be taken, as an ordinary Unixfile with%xxor:xxwill 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 uppercase and lowercase letters,the filesystem is case-insensitive, i.e., the filenamesaBc and AbCare the same. If a file is found in a directory with the same HFS name,genisoimagewill attempt to make a unique name by adding `_' charactersto one of the filenames.

If an HFS filename exists for a file,genisoimagecan use this name as the starting point for the ISO9660, Joliet andRock Ridge filenames using-mac-name.Normal Unix files without an HFS name will still use their Unix name.e.g.

If a MacBinary (or PC Exchange) file is stored assomeimage.gif.binon the Unix filesystem, but contains a HFS file calledsomeimage.gif,this is the name that would appear on the HFS part of the CD. However, asgenisoimageuses the Unix name as the starting point for the other names,the ISO9660 name generated will probably be SOMEIMAG.BINand the Joliet/Rock Ridge would besomeimage.gif.bin.This option will usethe HFS filename as the starting point and the ISO9660 name will probably beSOMEIMAG.GIFand the Joliet/Rock Ridge would besomeimage.gif.

-mac-namewill not currently work with-T--- the Unix name will be used in theTRANS.TBLfile, not the Macintosh name.

The character set used to convert any HFS filename to a Joliet/Rock Ridgefilename defaults tocp10000(Mac Roman).The character set used can be specified using-input-hfs-charset.Other built-in HFS character sets are:cp10006(MacGreek),cp10007(MacCyrillic),cp10029(MacLatin2),cp10079(MacIcelandandic) andcp10081(MacTurkish).

Note: the character codes used by HFS filenames taken from the variousApple/Unix formats will not be converted as they are assumed to be in thecorrect Apple character set. Only the Joliet/Rock Ridge names derived fromthe HFS filenames will be converted.

The existinggenisoimagecode will filter out any illegal characters for the ISO9660 and Jolietfilenames, but asgenisoimageexpects to be dealing directly with Unix names, it leaves the RockRidge names as is. But as `/' is a legal HFS filename character,-mac-nameconverts `/' to a `_' in Rock Ridge filenames.

If the Apple extensions are used, only the ISO9660 filenames willappear on the Macintosh. However, as the Macintosh ISO9660 drivers can useLevel 2filenames, you can use options like-allow-multidotwithout problems ona Macintosh --- still take care over the names, for examplethis.file.namewill be converted toTHIS.FILEi.e. only have one `.', also filenameabcdefghwill be seen asABCDEFGHbutabcdefghiwill be seen asABCDEFGHI.i.e. with a `.' at the end --- don't know if this is a Macintoshproblem or agenisoimage/mkhybridproblem. All filenames will be in uppercasewhen viewed on a Macintosh. Of course, DOS/Win3.X machines will not be ableto see Level 2 filenames...

HFS CUSTOM VOLUME/FOLDER ICONS

To give a HFS CD a custom icon, make sure the root (top level) folder includesa standard Macintosh volume icon file. To give a volume a custom icon ona 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 calledIcon\r(`\r' is the carriage return character) in the root folder.

A custom folder icon is very similar --- an invisible file calledIcon\rexists in the folder itself.

HFS BOOT DRIVER

It maybe possible to make the hybrid CD bootable on a Macintosh.

A bootable HFS CD requires an Apple CD-ROM (or compatible) driver, a bootableHFS partition and the necessary System, Finder, etc. files.

A driver can be obtained from any other Macintosh bootable CD-ROM using theapple_driverutility. This file can then be used with-boot-hfs-file.

The HFS partition (i.e. the hybrid disk in our case) must contain asuitable System Folder, again from another CD-ROM or disk.

For a partition to be bootable, it must have its boot blockset. The bootblock is in the first two blocks of a partition. For a non-bootable partitionthe boot block is full of zeros. Normally, when a System file is copied topartition on a Macintosh disk, the boot block is filled with a number ofrequired settings --- unfortunately I don't know the full spec for the bootblock, so I'm guessing that the following will work.

Therefore, the utilityapple_driveralso extracts the boot block from thefirst HFS partition it finds on the given CD-ROM and this is used for theHFS partition created bygenisoimage.

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.

EL TORITO BOOT INFORMATION TABLE

When-boot-info-tableis given,genisoimagewill modify the boot file specified by-bby inserting a 56-byteboot information tableat offset 8 inthe file. This modification is done in the source filesystem, so makesure you use a copy if this file is not easily recreated! This filecontains pointers which may not be easily or reliably obtained at boottime.

The format of this table is as follows; all integers are insection 7.3.1 ("little endian") format.

Offset Name Size Meaning 8 bi_pvd 4 bytes LBA of primary volume descriptor12 bi_file 4 bytes LBA of boot file16 bi_length 4 bytes Boot file length in bytes20 bi_csum 4 bytes 32-bit checksum24 bi_reserved 40 bytes Reserved

: The 32-bit checksum is the sum of all the 32-bit words in the bootfile starting at byte offset 64. All linear block addresses (LBAs)are given in CD sectors (normally 2048 bytes).

HPPA NOTES

To make a bootable CD for HPPA, at the very least a boot loader file(-hppa-bootloader),a kernel image file (32-bit, 64-bit, or both, depending on hardware)and a boot command line(-hppa-cmdline)must be specified. Some systems can boot either a 32- or a 64-bitkernel, and the firmware will choose one if both are present.Optionally, a ramdisk can be used for the root filesystem using-hppa-cmdline.

JIGDO NOTES

Jigdo is a tool to help in the distribution of large files like CD andDVD images; seehttp://atterer.org/jigdo/for more details. Debian CDs and DVD ISOimages are published on the web in jigdo format to allow end users to downloadthem more efficiently.

To create jigdo and template files alongside the ISO image fromgenisoimage,you must first generate a list of the files that will beused, in the following format:

MD5sum File size Path32 chars 12 chars to end of line

The MD5sum must be written in standard hexadecimal notation, thefile size must list the size of the file in bytes, and the pathmust list the absolute path to the file. For example:

00006dcd58ff0756c36d2efae21be376 14736 /mirror/debian/file1000635c69b254a1be8badcec3a8d05c1 211822 /mirror/debian/file200083436a3899a09633fc1026ef1e66e 22762 /mirror/debian/file3

Once you have this file, callgenisoimagewith all of your normal command-line parameters. Specify the outputfilenames for the jigdo and template files using-jigdo-jigdo and -jigdo-template,and pass in the location of your MD5 list with-md5-list.

If there are files that you do NOT want to be added into the jigdofile (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 arewritten into the image, specify them using -jigdo-force-md5. If anyfiles don't match,genisoimagewill then abort. Both of these options takeregular expressions as input. It is possible to restrict the set offiles that will be used further based on size --- use the-jigdo-min-file-size option.

Finally, the jigdo code needs to know how to map the files it is givenonto a mirror-style configuration. Specify how to map paths using-jigdo-map.UsingDebian=/mirror/debianwill cause allpaths starting with/mirror/debianto be mapped toDebian:<file>in the output jigdo file.

EXAMPLES

To create a vanilla ISO9660 filesystem image in the file cd.iso,where the directorycd_dirwill become the root directory of the CD, call:

: % genisoimage -o cd.iso cd_dir

To create a CD with Rock Ridge extensions ofthe source directorycd_dir:

: % genisoimage -o cd.iso -R cd_dir

To create a CD with Rock Ridge extensions ofthe source directorycd_dirwhere all files have at least read permission and all filesare owned byroot,call:

: % genisoimage -o cd.iso -r cd_dir

To write a tar archive directly to a CD that will later contain a simpleISO9660 filesystem with the tar archive call:

: % tar cf - . | genisoimage -stream-media-size 333000 | \
wodim dev=b,t,l -dao tsize=333000s -

To create a HFS hybrid CD with the Joliet and Rock Ridge extensions ofthe source directorycd_dir:

: % genisoimage -o cd.iso -R -J -hfs cd_dir

To create a HFS hybrid CD from the source directory cd_dirthat containsNetatalk Apple/Unix files:

: % genisoimage -o cd.iso --netatalk cd_dir

To create a HFS hybrid CD from the source directorycd_dir,giving all filesCREATOR and TYPES based on just their filename extensions listed in the file "mapping".:

: % genisoimage -o cd.iso -map mapping cd_dir

To create a CD with the Apple Extensions to ISO9660, from the sourcedirectoriescd_dirandanother_dir.Files in all the known Apple/Unix formatare decoded and any other files are given CREATOR and TYPE based on theirmagic number given in the filemagic:

: % genisoimage -o cd.iso -apple -magic magic -probe \
cd_dir another_dir

The following example puts different files on the CD that all havethe name README, but have different contents when seen as aISO9660/Rock Ridge, 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 directorycd_diron theCD along with the three README files --- but only one will be seen fromeach of the three filesystems:

% genisoimage -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 theother two README files will be hidden. Similarly for the Joliet andISO9660/Rock Ridge CD.

There are probably all sorts of strange results possible withcombinations of the hide options ...

NOTES

genisoimagemay safely be installed suid root. This may be needed to allowgenisoimageto read the previous session when creating a multisession image.

If genisoimage is creating a filesystem image with Rock Ridge attributes and thedirectory nesting level of the source directory tree is too muchfor ISO9660, genisoimage will do deep directory relocation.This results in a directory calledRR_MOVEDin the root directory of the CD. You cannot avoid this directory.

Many boot code options for different platforms are mutualy exclusive becausethe boot blocks cannot coexist, ie. different platforms share the same datalocations in the image. Seehttp://lists.debian.org/debian-cd/2006/12/msg00109.html for details.

BUGS

Any files that have hard links to files not in the tree being copied to theISO9660 filesystem will have an incorrect file reference count.

Does not check for SUSP record(s) in `.' entry of theroot directory to verify the existence of Rock Ridgeenhancements.This problem is present when reading old sessions whileadding data in multisession mode.

Does not properly read relocated directories in multisessionmode when adding data.Any relocated deep directory is lost if the new session does notinclude the deep directory.

Does not re-useRR_MOVEDwhen doing multisession fromTRANS.TBL.

Does not create whole_name entry forRR_MOVEDin multisession mode.

There may be other bugs. Please, report them to the maintainers.

HFS PROBLEMS/LIMITATIONS

I have had to make several assumptions on how I expect the modifiedlibhfs routines to work, however there may be situations that eitherI haven't thought of, or come across when these assumptions fail.Therefore I can't guarantee thatgenisoimagewill work as expected(although I haven't had a major problem yet). Most of the HFS features workfine, but some are not fully tested. These are marked asAlphaabove.

Although HFS filenames appear to support uppercase and lowercase letters,the filesystem is case-insensitive, i.e., the filenamesaBc and AbCare the same. If a file is found in a directory with the same HFS name,genisoimagewill attempt to make a unique name by adding `_' charactersto one of the filenames.

HFS file/directory names that share the first 31 characters have`_N' (a decimal number) substituted for the last few charactersto generate unique names.

Care must be taken when "grafting" Apple/Unix files or directories (seeabove for the method and syntax involved). It is not possible to use anew name for an Apple/Unix encoded file/directory. e.g. If a Apple/Unixencoded file calledoldnameis to added to the CD, you cannot use the command line:

: genisoimage -o output.raw -hfs -graft-points newname=oldname cd_dir

genisoimagewill be unable to decodeoldname.However, you can graftApple/Unix encoded files or directories as long as you do not attempt togive them new names as above.

When creating an HFS volume with the multisession options,-Mand-C,only files in the last session will be in the HFS volume. i.e.genisoimagecannotaddexisting files from previous sessions to the HFS volume.

However, if each session is created with-part,each session will appear as separate volumes when mounted on a Mac. In this case, it is worth using-V or -hfs-volidto give each session a unique volume name,otherwise each "volume" will appear on the Desktop with the same name.

Symbolic links (as with all other non-regular files) are not added tothe HFS directory.

Hybrid volumes may be larger than pure ISO9660 volumescontaining the same data. In some cases (e.g. DVD sized volumes) thedifference can be significant. As an HFS volume gets bigger, so does theallocation 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 beabout 70kB.

The maximum number of files in an HFS volume is about 65500 --- althoughthe real limit will be somewhat less than this.

The resulting hybrid volume can be accessed on a Unix machine by usingthe hfsutils routines. However, no changes can be made to the volume as itis set aslocked.The option-hfs-unlockwill create an output image that is unlocked --- however no changes should bemade to the contents of the volume (unless you really know what you aredoing) as it's not a "real" HFS volume.

-mac-namewill not currently work with-T--- the Unix name will be used in theTRANS.TBLfile, not the Macintosh name.

Although genisoimagedoes not alter the contents of a file, if a binary file has its TYPEset asTEXT, it maybe read incorrectly on a Macintosh. Therefore a better choice for thedefault TYPE may be????.

-mac-boot-filemay 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 typemsdos(notvfat)when using Linux.

The SFM format is only partially supported --- seeHFS MACINTOSH FILE FORMATSsection above.

It is not possible to use-sparc-boot or -generic-boot with-boot-hfs-file or -prep-boot.

genisoimageshould be able to create HFS hybrid images over 4Gb, although this has notbeen fully tested.

AUTHORS

genisoimageis derived frommkisofsfrom thecdrtools 2.01.01a08package from May 2006 (with few updates extracted from cdrtools 2.01.01a24 fromMarch 2007) from .IR http://cdrecord.berlios.de/ ,but is now part of thecdrkitsuite, maintained by Joerg Jaspert, Eduard Bloch, Steve McIntyre, PeterSamuelson, Christian Fromme, Ben Hutchings, and other contributors.The maintainers can be contacted atdebburn-devel [at] lists.alioth.debian.org,or see thecdrkitproject web site athttp://www.cdrkit.org/.

Eric Youngdale wrote the first versions (1993-1998) ofmkisofs.Jörg Schilling wrote the SCSI transport library and itsinterface, and has maintainedmkisofssince 1999. James Pearson wrote the HFS hybrid code, usinglibhfsby Robert Leslie. Pearson, Schilling, Jungshik Shin and JaakkoHeinonen contributed to the character set conversion code. Thecdrkitmaintainers have maintainedgenisoimagesince 2006.

Copyright 1993-1998 by Yggdrasil Computing, Inc.Copyright 1996-1997 by Robert LeslieCopyright 1997-2001 by James PearsonCopyright 1999-2006 by Jörg SchillingCopyright 2007 by Jörg Schilling (originating few updates)Copyright 2002-2003 by Jungshik ShinCopyright 2003 by Jaakko HeinonenCopyright 2006 by the Cdrkit maintainers

If you want to take part in the development ofgenisoimage,you may join thecdrkitdeveloper mailing list by following the instructions onhttp://alioth.debian.org/mail/?group_id=31006.The email address of the list isdebburn-devel [at] lists.alioth.debian.org.This is also the address for user support questions. Note thatcdrkit and cdrtoolsare not affiliated.

ACKNOWLEDGEMENTS

UNIX is a registered trademark of The Open Group in the US and other countries.

Pages related to mkisofs

mkimage (1) - Generate image for U-Boot
mkindex (1)
mkSimNodeDir (1) - Create a /proc like files for a simulated node
mkaf (1) - create a Performance Co-Pilot archive folio
mkafmmap (1) - creates font map for AFM files
mkbindic (1) - Convert a text-form dictionary into a binary-form dictionary
mkbitmap (1) - transform images into bitmaps with scaling and filtering

mkisofs: create ISO9660/Joliet/HFS filesystem with optional Rock Ridge attributes - Linux Manuals (1) (2024)

FAQs

What is ISO 9660 file system in Linux? ›

This industry standard media format was originally designed to specify the volume and file structures of compact-disk read-only memory (CD-ROM) optical disks, and is a read-only media format.

What is the maximum size of mkisofs? ›

isofs has the limit of 4.0GB max per file...

Learn More ›

How to create a custom RHEL ISO? ›

Creating a Custom Kickstart ISO for CentOS Stream and RHEL 8: A Step-by-Step Guide

Switch to the Root User sudo -i.
Mount the ISO mount -o loop /PATH/TP/DOWNLOADED/<iso>.iso /mnt/iso.
Copy ISO Contents to Temporary Directory. ...
Unmounting the ISO Image umount /mnt/iso.

More items...

May 16, 2024

View Details ›

What does Binwalk do in Linux? ›

Binwalk is a tool for searching a given binary image for embedded files and executable code. Specifically, it is designed for identifying files and code embedded inside of firmware images.

Explore More ›

What is Netdiscover in Linux? ›

Netdiscover is a network address discovering tool, developed mainly for those wireless networks without dhcp server, it also works on hub/switched networks. Its based on arp packets, it will send arp requests and sniff for replies.

Discover More ›

What is OverlayFS in Linux? ›

OverlayFS is a union mount filesystem implementation for Linux. It allows a virtual merge of two partitions, while keeping their actual contents separate. One partition is the rootfs partition and the other is the data partition.

Show Me More ›

What is the ISO file system in Linux? ›

ISO image files typically have a file extension of . ISO. The name “ISO” comes from the ISO 9660 file system used with CD-ROM or DVD media, but an ISO image can also contain UDF file system because UDF is backward-compatible to ISO 9660. You can mount an ISO file or images via the loop device under Linux.

Get More Info ›

Is ISO 9660 bootable? ›

A 32-bit PC BIOS will search for boot code on an ISO 9660 CD-ROM. The standard allows for booting in two different modes.

Read The Full Story ›

What file system does ISO use? ›

Other than ISO 9660 media, an ISO image might also contain a UDF (ISO/IEC 13346) file system (commonly used by DVDs and Blu-ray Discs), including the data in its files in binary format, copied exactly as they were stored on the disc.

Get More Info ›

Which file system is a technical standard that is referred to as ISO 9660? ›

The ISO 9660 format is the original standard file system for CD data discs. The format is recognized on several operating systems, including MSDOS, the Mac OS, UNIX, and the Windows operating system. The ISO 9660 format is published by the International Organization for Standardization (ISO).

mkisofs: create ISO9660/Joliet/HFS filesystem with optional Rock Ridge attributes - Linux Manuals (1) (2024)