MKISOFS(8)

✨ NAME ✨

Bestie, welcome to MKISOFS(8) from the System Manager's Manual — part 1, and it’s giving “make a whole hybrid filesystem image” energy 💿✨

• mkisofs — create an hybrid ISO-9660/JOLIET/HFS/UDF filesystem-image with optional Rock Ridge attributes.

---

🌸 SYNOPSIS 🌸

The shape of it is literally this, no cap:

mkisofs [ options ] [ -o filename ] pathspec [pathspec ...]
mkisofs [ options ] [ -o filename ] -find [find expression]

---

🎀 DESCRIPTION 🎀

Okay so mkisofs is effectively a pre-mastering program to generate an ISO-9660/JOLIET/HFS/UDF hybrid filesystem. She’s not burning the disc herself, she’s making the image first — main character prep work 💅

ISO-9660/JOLIET/UDF filesystems are limited to a maximum size of 8 TB. The maximum size of a single file is 8 TB — single files in UDF are currently limited to aprox. 200 GB. If you like to have files larger than 2 GB, you need to specify -iso-level 3 or above. If a HFS hybrid is created, the maximum file size for files in the HFS hybrid is 2 GB in any case. Not me knowing the limits by heart 😭

🦋 Hybrid filesystem support 🦋

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 ISO-9660 filesystem to a UNIX host, and provides information such as longer filenames, uid/gid, posix permissions, symbolic links, hard links, block and character devices. Iconic behavior, honestly 🌈

If Joliet, HFS or UDF hybrid command line options are specified, mkisofs will create additional separate filesystem meta data for Joliet, HFS or UDF. The file content in this case refers to the same data blocks on the media. It will generate a pure ISO-9660 filesystem unless the Joliet, HFS or UDF hybrid command line options are given. Slay, but make it standards-compliant ✨

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 ISO-9660 files when accessed from other machines. HFS stands for Hierarchical File System and is the native file system used on Macintosh computers up to Mac OS 9. That’s her vintage era, bestie 🍓

As an alternative, mkisofs can generate the Apple Extensions to ISO-9660 or UDF 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. Iykyk 👑

💜 Functional description 💜

mkisofs takes a snapshot of a given directory tree, and generates a binary image which will correspond to an ISO-9660 or Joliet/HFS/UDF filesystem when written to a block device.

Each file written to the ISO-9660 filesystem must have a filename in the 8.3 format (8 characters, period, 3 characters, all upper case), even if Rock Ridge attributes are 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. The way the 8.3 naming drama unfolds is lowkey fascinating 😭

When used with various HFS or UDF 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 writers for optical media directly. Most writers have proprietary command sets which vary from one manufacturer to another, and you need a specialized tool like cdrecord to actually burn the disk. She makes the image; cdrecord does the fiery part 🔥

The cdrecord utility is a utility capable of burning an actual disc. The latest version of cdrecord is available from:

https://sourceforge.net/projects/cdrtools/files/
https://sourceforge.net/projects/cdrtools/files/alpha/

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. Like, do not let the vibe check fail mid-burn 💀

🧚 Dealing with path names 🧚

pathspec is the path of the directory tree to be copied into the ISO-9660 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. Grafting is giving “build the tree exactly where I want it” energy 🌸

mkisofs will also run on Win9x/NTx machines when compiled with Cygnus’ cygwin (available from http://sourceware.cygnus.com/cygwin/). Therefore most references in this man page to Unix also apply to Win32 or Win64. Cross-platform queen 🫶

---

✨ OPTIONS ✨

Okay bestie, here come the flags — every single one, no skipping, because we don’t gatekeep 👑

• -abstract FILE — specifies the abstract file name in the primary volume descriptor. There is space on the disc for 37 characters of information. The related Joliet entry is limited to 18 characters. This parameter can also be set in the file .mkisofsrc with ABST=filename. If specified in both places, the command line version is used. It is up to the user of mkisofs to include a file with the apropriate name in the created filesystem tree.
• -A application_id, -appid 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. There is space on the disc for 128 characters of information. The related Joliet entry is limited to 64 characters. This parameter can also be set in the file .mkisofsrc with APPI=id. If specified in both places, the command line version is used.
• -allow-leading-dots, -ldots — allow ISO-9660 filenames to begin with a period. Usually, a leading dot is replaced with an underscore in order to maintain MS-DOS compatibility. This violates the ISO-9660 standard, but it happens to work on many systems. Use with caution. She’s a little rebellious, but we love her for it 💅
• -allow-lowercase — this options allows lower case characters to appear in ISO-9660 filenames. This violates the ISO-9660 standard, but it happens to work on some systems. Use with caution.
• -no-allow-lowercase — this resets the effect of -allow-lowercase and even works when -U, -untranslated-filenames or -iso-level 4 have been used to allow lowercase filenames.
• -allow-multidot — this options allows more than one dot to appear in ISO-9660 filenames. A leading dot is not affected by this option, it may be allowed separately using the -allow-leading-dots option. This violates the ISO-9660 standard, but it happens to work on many systems. Use with caution. Dots on dots on dots — she said “more is more” 🎀
• -biblio FILE — specifies the bibliographic file name in the primary volume descriptor. There is space on the disc for 37 characters of information. The related Joliet entry is limited to 18 characters. This parameter can also be set in the file .mkisofsrc with BIBLO=filename. If specified in both places, the command line version is used. It is up to the user of mkisofs to include a file with the apropriate name in the created filesystem tree.
• -cache-inodes — cache inode and device numbers to find hard links to files. If mkisofs finds a hard link (a file with multiple names), then the file will only appear once on the CD. This helps to save space on the CD. The option -cache-inodes is default on UNIX like operating systems. Be careful when using this option on a filesystem without unique inode numbers as it may result in files containing the wrong content on CD. See the option -duplicates-once for a method that works on filesystems without unique inode numbers. If inodes are not cached, mkisofs will revert to the old Rrip Version-1.10 (see -rrip110) and mkisofs will not be able to create correct inode numbers for zero sized files.
• -no-cache-inodes — do not cache inode and device numbers. This option is needed whenever a filesystem does not have unique inode numbers. It is the default on old Cygwin versions. As the Microsoft operating system that runs below Cygwin uses 64 bit inode numbers for NTFS, it does not have unique inode numbers in the 32 bit range. Old Cygwin versions create fake 32-bit inode numbers from a hash algorithm and thus create non-unique numbers. If mkisofs would cache inodes on old Cygwin versions, it would believe that some files are identical although they are not. The result in this case are files that contain the wrong content if a significant amount of different files (> ~5000) is in inside the tree that is to be archived. This does not happen when the -no-cache-inodes is used, but the disadvantage is that mkisofs cannot detect hardlinks anymore and the resulting CD image may be larger than expected. If inodes are not cached, mkisofs will revert to the old Rrip Version-1.10 (see -rrip110) and mkisofs will not be able to create correct inode numbers for zero sized files. That Cygwin inode situation is lowkey a cautionary tale 😭
• -duplicates-once — tells mkisofs to use a message digest checksum to spot files that are identical and treat them like they were hard linked. Basically it lets mkisofs archive inode numbers and hard links even when it's running on non-POSIX platforms like DOS. slay for DOS honestly 💅
• -b eltorito_boot_image
• -eltorito-boot eltorito_boot_image — gives the path and filename of the boot image to use when you're making an "El Torito" bootable CD ✨ The pathname has to be relative to the source path and inside the source tree you gave to mkisofs. You need this option to make an "El Torito" bootable CD, no cap. The boot image must be exactly the size of a 1200, 1440, or 2880 kB floppy, and mkisofs uses that size when it creates the output ISO-9660 filesystem. It assumes the first 512 byte sector should be read from the boot image (it's basically emulating a normal floppy drive). This works if, like, the boot image is a boot floppy — for example.

If your boot image is not an image of a floppy, you gotta add one of these: -hard-disk-boot or -no-emul-boot. And if the system shouldn't boot off the emulated disk, use -no-boot.

You can have more than one boot entry, see -eltorito-platform and -eltorito-alt-boot for how to specify more boot entries. The first boot entry is the default boot entry, and additional boot entries are members for a multi boot configuration 🫶

If the -sort option hasn't been specified, the boot images get sorted with low priority (+2) to the beginning of the medium. Not a fan? Then you need to specify a sort weight of 0 for the boot images.

• -eltorito-alt-boot — starts a whole new set of "El Torito" boot parameters 🎀 this is how you get more than one El Torito boot entry on a CD. Max 63 El Torito boot entries per single CD, so don't get carried away.

The -eltorito-alt-boot option starts a new boot entry with the same platform id but no new boot section, except when it shows up past the first boot entry (which is the default boot entry).

• -eltorito-platform id — sets the "El Torito" platform id for a boot record or a section of boot records. The id parameter can be either:
  • x86 — this is the default platform id value, and it specifies entries for the PC platform. If no -eltorito-platform option appears before the first -eltorito-boot option, the default boot entry becomes an entry for the x86 PC platform.
  • PPC — boot entries for the Power PC platform.
  • Mac — boot entries for the Apple Mac platform.
  • efi — boot entries for EFI based PCs.
  • # — a numeric value specifying any platform id. 🔥

If the -eltorito-platform option appears before the first -eltorito-boot option, it sets the platform id for the default boot entry.

If the -eltorito-platform option appears after an -eltorito-boot option and sets the platform id to a value different from the previous value, it starts a new set of boot entries.

Heads up: the second boot entry and any new platform id creates a new section header and reduces the number of boot entries per CD by one. maths 💀

• errctl= name
• errctl= error control spec — adds the content from file name to the error control definitions, or adds error control spec to the error control definitions. You can have more than one error control file, more than one error control spec, and honestly a mixture of both forms is fine too ✨

So why would you even use error control? The whole point is to make mkisofs quiet about error conditions that are known to be irrelevant to the quality of the created filesystem, or to tell mkisofs to abort on certain error conditions instead of trying to keep going with the filesystem.

A typical reason to reach for error control is to suppress warnings about growing log files while you're doing a backup on a live file system. Another super typical reason is to tell mkisofs to abort if, like, a file couldn't be archived, instead of continuing to archive other files from a list.

The error control file contains a set of lines, each starting with a list of error conditions to be ignored, followed by white space, followed by a file name pattern (peep match(1) or patmatch(3) for more info). The error control spec uses the same syntax as a single line from the error control file. If the file name pattern needs to start with white space, use a backslash to escape the start of the file name. Also, you literally cannot have new line characters in the file name pattern. Whenever an error situation is encountered, mkisofs checks the lines in the error control file starting from the top. If the current error condition is listed on a line in the error control file, then mkisofs checks whether the pattern on the rest of the line matches the current file name. If it does, mkisofs uses the current error control specification to control the current error condition 👑

The list of error conditions to be handled may use one or more identifiers from the list below (and if you're using more than one, separate them with a | character):

• ABORT — if this meta condition is included in an error condition, mkisofs aborts (exits) as soon as possible after this error condition has been seen, instead of making mkisofs quiet about the condition. This error condition flag may only be used together with another error condition or a list of error conditions (separated by a | character).
• WARN — if this meta condition is included in an error condition, mkisofs prints the warning about the error condition, but the error condition does not affect the exit code of mkisofs, and the error statistics (which are printed at the end) don't include the related errors. This error condition flag may only be used together with another error condition or a list of error conditions (separated by a | character). The WARN meta condition has a lower precedence than ABORT.
• ALL — shortcut for all error conditions below. iconic.
• STAT — suppress warnings that mkisofs couldn't stat(2) a file.
• GETACL — suppress warnings about files where mkisofs had problems retrieving the ACL information.
• OPEN — suppress warnings about files that couldn't be opened.
• READ — suppress warnings about read errors on files.
• WRITE — suppress warnings about write errors on files.
• READLINK — suppress warnings about readlink(2) errors on symbolic links.
• GROW — suppress warnings about files that did grow while they were being archived.
• SHRINK — suppress warnings about files that did shrink while they were being archived.
• MISSLINK — suppress warnings about files for which mkisofs was unable to archive all hard links.
• NAMETOOLONG — suppress warnings about files that couldn't be archived because the name of the file is too long for the archive format.
• FILETOOBIG — suppress warnings about files that couldn't be archived because the size of the file is too big for the archive format.
• SPECIALFILE — suppress warnings about files that couldn't be archived because the file type isn't supported by the archive format.
• GETXATTR — suppress warnings about files where mkisofs couldn't retrieve the extended file attribute information.
• SETTIME — suppress warnings about files where mkisofs couldn't set the time information during extraction.
• SETMODE — suppress warnings about files where mkisofs couldn't set the access modes during extraction.
• SECURITY — suppress warnings about files that have been skipped on extraction because they were considered to be a security risk. This currently applies to all files that have a '/../' sequence inside when -.. has not been specified.
• LSECURITY — suppress warnings about links that have been skipped on extraction because they were considered to be a security risk. This currently applies to all link names that start with '/' or have a '/../' sequence inside when -secure-links has been specified. In this case, mkisofs tries to match the link name against the pattern in the error control file.
• SAMEFILE — suppress warnings about links that have been skipped on extraction because source and target of the link are pointing to the same file. If mkisofs didn't skip these files, it would end up removing the file completely 😭 In this case, mkisofs tries to match the link name against the pattern in the error control file.
• BADACL — suppress warnings about access control list conversion problems.
• SETACL — suppress warnings about files where mkisofs couldn't set the ACL information during extraction.
• SETXATTR — suppress warnings about files where mkisofs couldn't set the extended file attribute information during extraction.

If a specific error condition is ignored, then that error condition isn't just handled in a silent way — it's also excluded from the error statistics that get printed at the end of the mkisofs run. 🦋

Be very careful when using error control, because you may ignore any error condition. If you ignore the wrong error conditions, you may not be able to see real problems anymore. fr fr, don't do this to yourself.

Note that currently only the tags OPEN, READ, GROW, SHRINK, are checked from mkisofs. iykyk 🙈

• -B img_sun4,img_sun4c,img_sun4m,img_sun4d,img_sun4e
• -sparc-boot img_sun4,img_sun4c,img_sun4m,img_sun4d,img_sun4e — bestie, this takes a comma-separated list of boot images you need to make a bootable CD for sparc systems. Partition 0 is used for the ISO-9660 image, and the first image file is mapped to partition 1. There may be empty fields in the comma-separated list. The maximum number of possible partitions is 8, so it is impossible to specify more than 7 partition images. This option is required to make a bootable CD for Sun sparc systems. If the -B or -sparc-boot option has been specified, the first sector of the resulting image will contain a Sun disk label. This disk label specifies slice 0 for the ISO-9660 image and slice 1 … slice 7 for the boot images that have been specified with this option. Byte offset 512 … 8191 within each of the additional boot images must contain a primary boot that works for the appropriate sparc architecture. The rest of each of the images usually contains an ufs filesystem that is used primary kernel boot stage.

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.

For more information also see the NOTES section below.

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 ISO-9660 filesystem image and the generic boot image that is located in the first 16 sectors of the disk is used for all architectures.

• -G generic_boot_image — specifies the path and filename of the generic boot image to be used when making a generic bootable CD. The generic_boot_image will be placed on the first 16 sectors of the CD. The first 16 sectors are the sectors that are located before the ISO-9660 primary volume descriptor. If this option is used together with the -sparc-boot option, the Sun disk label will overlay the first 512 bytes of the generic boot image.
• -hard-disk-boot — says the boot image used to create “El Torito” bootable CDs is a hard disk image. The hard disk image must begin with a master boot record that contains a single partition.
• -ignore-error — ignore errors, bestie. mkisofs by default aborts on several errors, such as read errors. With this option in effect, mkisofs tries to continue. Use with care.
• -no-emul-boot — says the boot image used to create “El Torito” bootable CDs is a ‘no emulation’ image. The system will load and execute this image without performing any disk emulation.
• -no-boot — says the created “El Torito” CD should be marked as not bootable. The system will provide an emulated drive for the image, but will boot off a standard boot device.
• -boot-load-seg segment_address — specifies the load segment address of the boot image for no-emulation “El Torito” CDs.
• -boot-load-size load_sectors — specifies the number of “virtual” (512-byte) sectors to load in no-emulation mode. The default is to load the entire boot file. Some BIOSes 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 layout will be patched in at offset 8 in the boot file. If this option is given, the boot file is modified in the source filesystem, so make sure to make a copy if this file cannot be easily regenerated! See the EL TORITO BOOT INFO TABLE section for a description of this table.
• -C last_sess_start,next_sess_start, -cdrecord-params last_sess_start,next_sess_start — this option is needed when mkisofs is used to create a CDextra or the image of a second session or a higher level session for a multi session disk. The option -C takes a pair of two numbers separated by a comma. The first number is the sector number of the first sector in the last session of the disk that should be appended to. The second number is the starting sector number of the new session. The expected pair of numbers may be retrieved by calling cdrecord -msinfo .... If the -C option is used in conjunction with the -M option, mkisofs will create a filesystem image that is intended to be a continuation of the previous session. If the -C option is used without the -M option, mkisofs will create a filesystem image that is intended to be used for a second session on a CDextra. This is a multi session CD that holds audio data in the first session and a ISO-9660 filesystem in the second session.
• -c boot_catalog, -eltorito-catalog boot_catalog — specifies the path and filename of the boot catalog to be used when making an “El Torito” bootable CD. The pathname must be relative to the source path specified to mkisofs. This option is required to make a bootable CD. This file will be inserted into the output tree and not created in the source filesystem, so be sure the specified filename does not conflict with an existing file, as it will be excluded. Usually a name like boot.catalog is chosen.

If the -sort option has not been specified, the boot catalog sorted with 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 old session for compliance with actual mkisofs ISO-9660 file naming rules. If this option is not present, only names with a length > 31 are checked as these files are a hard violation of the ISO-9660 standard.
• -check-session FILE — check all old sessions for compliance with actual mkisofs ISO-9660 file naming rules. This is a high level option that is a combination of the options: -M FILE -C 0,0 -check-oldnames. For the parameter FILE see description of -M option.
• -copyright FILE — specifies the Copyright file name in the primary volume descriptor. There is space on the disc for 37 characters of information. The related Joliet entry is limited to 18 characters. This parameter can also be set in the file .mkisofsrc with COPY=filename. If specified in both places, the command line version is used.

It is up to the user of mkisofs to include a file with the appropriate name in the created filesystem tree.

• -d, -omit-period — omit trailing period from files that do not have a period. This violates the ISO-9660 standard, but it happens to work on many systems. Use with caution.
• -D, -disable-deep-relocation — do not use Rock Ridge deep directory relocation, and instead just pack directories in the way they are in the master directory tree.

This option was needed with old mkisofs versions to avoid a visible directory rr_moved. Since August 2006, mkisofs correctly hides the rr_moved directory from the Rock Ridge filesystem.

If ISO-9660:1999 has not been selected, this violates the ISO-9660 standard, but it happens to work on many systems. Use with caution.

• -data-change-warn — if the size of a file changes while the file is being archived, treat this condition as a warning only that does not cause mkisofs to abort. A warning message is still written if the condition is not otherwise ignored by another rule from an errctl= option. The -data-change-warn option works as if the last error control option was

errctl="WARN|GROW|SHRINK *"

• -debug — increment debug value by one.
• -dir-mode mode — overrides the mode of directories used to create the image to mode. See -new-dir-mode on how to specify a different mode that is used for directories that do not exist in the tree specified by the source-path. Specifying the -dir-mode option automatically enables Rock Ridge extensions.
• -dvd-audio — generate DVD-Audio compliant UDF file system. This is done by sorting the order of the content of the appropriate files. Sorting only works if the DVD-Audio filenames include upper case characters only.

Note that in order to get a DVD-Audio compliant filesystem image, you need to prepare a DVD-Audio compliant directory tree. This means you need to have a directory AUDIO_TS (all caps) in the root directory of the resulting DVD and you should have a directory VIDEO_TS. The directory AUDIO_TS needs to include all needed files (file names must be all caps) for a compliant DVD-Audio filesystem.

• -dvd-hybrid — equivalent to selecting both -dvd-audio and -dvd-video.
• -dvd-video — generate DVD-Video compliant UDF file system. This is done by sorting the order of the content of the appropriate files and by adding padding between the files if needed. Sorting only works if the DVD-Video filenames include upper case characters only.

Note that in order to get a DVD-Video compliant filesystem image, you need to prepare a DVD-Video compliant directory tree. This means you need to have a directory VIDEO_TS (all caps) in the root directory of the resulting DVD and you should have a directory AUDIO_TS. The directory VIDEO_TS needs to include all needed files (file names must be all caps) for a compliant DVD-Video filesystem.

• -f, -follow-links — follow all symbolic links when generating the filesystem. When this option is not in use, symbolic links will be entered using Rock Ridge if enabled, otherwise the file will be ignored.

See also -posix-L option.

• -file-mode mode — overrides the mode of regular files used to create the image to mode. Specifying this option automatically enables Rock Ridge extensions.
• -find — this option acts a separator. If it is used, all mkisofs options must be to the left of the -find option. To the right of the -find option, mkisofs accepts the find command line syntax only.

the find expression</p> is literally a filter bestie — it sits between where the file names come from and the thing that actually consumes them (that's the archiving engine). If the find expression evaluates as TRUE, the file gets picked for processing. If not, it's omitted. That's it, that's the vibe check. 💅

And to make life easier, mkisofs has some extra find primaries that have side effects on your file metadata. Here's the whole lineup:

• -help — lists the available find(1) syntax for you.
• -chgrp gname — always evaluates true; sets the group of the file to gname.
• -chmod mode — always evaluates true; sets the permissions of the file to mode. Octal and symbolic permissions are both accepted for mode, just like with chmod(1).
• -chown uname — always evaluates true; sets the owner of the file to uname.
• -false — always evaluates false; this lets you make the result of the full expression different from the result of one part of the expression.
• -true — always evaluates true; same deal, lets you make the full expression's result different from a part's result.

Okay so like, example time, because this is where it clicks ✨. This command line:

mkisofs -o o.iso -find . ( -type d -ls -o false ) -o ! -type d

lists all the directories and puts all the non-directories into the image o.iso. Slay.

And this one:

mkisofs -o o.iso -find . ( -type d -chown root -o true )

archives all directories so they appear to be owned by root in the archive, while all the non-directories get archived exactly as they are in the file system. Iconic. 👑

⚠️ Heads up bestie: the -ls, -exec and the -ok primary cannot be used if stdin or stdout has not been redirected. No cap.

• -gid gid — overrides the gid read from the source files with the value of gid. Specifying this option automatically enables Rock Ridge extensions. 🎀
• -gui — switches the behaviour for a GUI. Right now this just makes the output more verbose, but it may have other effects in the future. Foreshadowing, iykyk.
• -graft-points — allows you to use graft points for filenames. If this option is used, all filenames get checked for graft points. The filename is divided at the first unescaped equal sign. All occurrences of '\\' and '=' characters must be escaped with '\\' if -graft-points has been specified.
• -hide glob — hides glob from being seen on the ISO-9660 or Rock Ridge directory. glob is a shell wild-card-style pattern that must match any part of the filename or path. Multiple globs may be hidden. If glob matches a directory, then the contents of that directory will be hidden. In order to match a directory name, make sure the pathname does not include a trailing / character. All the hidden files will still be written to the output CD image file. Should be used with the -hide-joliet option. See README.hide for more details. 🫣
• -hide-list file — a file containing a list of globs to be hidden, as above.
• -hidden glob — adds the hidden (existence) ISO-9660 directory attribute for glob. This attribute will prevent glob from being listed on DOS based systems if the /A flag is not used for the listing. glob is a shell wild-card-style pattern that must match any part of the filename or path. In order to match a directory name, make sure the pathname does not include a trailing / character. Multiple globs may be hidden.
• -hidden-list file — a file containing a list of globs to get the hidden attribute, as above.
• -hide-joliet glob — hides glob from being seen on the Joliet directory. glob is a shell wild-card-style pattern that must match any part of the filename or path. Multiple globs may be hidden. If glob matches a directory, then the contents of that directory will be hidden. In order to match a directory name, make sure the pathname does not include a trailing / character. All the hidden files will still be written to the output CD image file. Should be used with the -hide option. See README.hide for more details.
• -hide-joliet-list file — a file containing a list of globs to be hidden, as above.
• -hide-joliet-trans-tbl — hides the TRANS.TBL files from the Joliet tree. These files usually don't make sense in the Joliet World, since they list the real name and the ISO-9660 name, which may both be different from the Joliet name. 🦋
• -hide-rr-moved — renames the directory RR_MOVED to .rr_moved in the Rock Ridge tree. This option was introduced back when mkisofs wasn't able to hide the directory in the Rock Ridge tree. This version of mkisofs always automatically hides the RR_MOVED directory in the Rock Ridge tree. If you need to have no RR_MOVED directory at all (even in the ISO-9660 tree), you should use the -D option. Note that in case the -D option has been specified, the resulting filesystem is not ISO-9660 level-1 compliant and will not be readable on MS-DOS. See also the NOTES section for more information on the RR_MOVED directory.
• -hide-udf glob — hides glob from being seen on the UDF directory. glob is a shell wild-card-style pattern that must match any part of the filename or path. Multiple globs may be hidden. If glob matches a directory, then the contents of that directory will be hidden. In order to match a directory name, make sure the pathname does not include a trailing / character. All the hidden files will still be written to the output CD image file. Should be used with the -hide option. See README.hide for more details.
• -hide-udf-list file — a file containing a list of globs to be hidden, as above.
• -hide-ignorecase, -exclude-ignorecase — ignore the case of the filenames with the -hide* options and with the -exclude-list option.
• -input-charset charset — sets up the input charset, which defines the characters used in local file names. To get a list of valid charset names, call mkisofs -input-charset help. To get a 1:1 mapping, you may use default as the charset name. If the input charset has not been set up from the locale in the environment, the default initial values are cp437 on DOS based systems and iso8859-1 on all other systems. See the CHARACTER SETS section below for more details.

If -input-charset has not been specified, it will be set up from the locale in the environment. If you'd like to disable this automatic setup, use the empty string as the locale name. 🌸

• -output-charset charset — sets up the output charset, which defines the characters that will be used in Rock Ridge file names. Defaults to the input charset. See the CHARACTER SETS section below for more details.
• -iso-level level — sets the ISO-9660 conformance level. Valid numbers are 1..3 and 4.
  • 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 (other than ISO-9660:1988) apply. Starting with this level, mkisofs also allows files to be larger than 4 GB by implementing ISO-9660 multi-extent files.
  • With all ISO-9660 levels from 1..3, 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.
  • Level 4 officially does not exist, but mkisofs maps it to ISO-9660:1999, which is ISO-9660 version 2.
  • With level 4, an enhanced volume descriptor with version number and file structure version number set to 2 is emitted. There may be more than 8 levels of directory nesting, there is no need for a file to contain a dot, and the dot has no more special meaning. File names do not have version numbers, the maximum length for files and directories is raised to 207. If Rock Ridge is used, the maximum ISO-9660 name length is reduced to 197.

🫶 When creating Version 2 images, mkisofs emits an enhanced volume descriptor which looks similar to a primary volume descriptor but is slightly different. Be careful not to use broken software to make ISO-9660 images bootable by assuming a second PVD copy and patching this putative PVD copy into an El Torito VD. Like, don't do that. 💀

• -J — generates Joliet directory records in addition to regular ISO-9660 file names. This is primarily useful when the discs are going to be used on Windows-NT or Windows-95 machines. The Joliet filenames are specified in Unicode and each path component can be up to 64 Unicode characters long. Note that Joliet is no standard — CDs that use only Joliet extensions but no standard Rock Ridge extensions may usually only be used on Microsoft Win32 systems. Furthermore, the fact that the filenames are limited to 64 characters and the fact that Joliet uses the UTF-16 coding for Unicode characters causes interoperability problems. 😭
• -joliet-long — allows Joliet filenames to be up to 103 Unicode characters. This breaks the Joliet specification — but it appears to work. Use with caution. The number 103 is derived from: the maximum Directory Record Length (254), minus the length of Directory Record (33), minus CD-ROM XA System Use Extension Information (14), divided by the UTF-16 character size (2). Math ate, honestly. 🧮✨
• -jcharset charset — same as using the -input-charset charset and -J options together. See the CHARACTER SETS section below for more details.
• -l, -full-iso9660-filenames — allow full 31 character filenames. Normally the ISO-9660 filename will be in an 8.3 format which is compatible with MS-DOS, even though the ISO-9660 standard allows filenames of up to 31 characters. If you use this option, the disc may be difficult to use on a MS-DOS system, but this comes in handy on some other systems (such as the Amiga). Use with caution. 💜
• -L — okay bestie this one's a fossil 🦕 it's an outdated option reserved by POSIX.1-2001, and you should use -allow-leading-dots instead. This option will get POSIX.1-2001 semantics with mkisofs-3.02. iykyk, just don't.
• -log-file log_file — redirects all the error, warning AND informational messages to log_file instead of the standard error. so your terminal stays cute and unbothered while the receipts go in the file 💅
• -long-rr-time — uses the long ISO-9660 time format for the file time stamps used in Rock Ridge. This time format allows to represent year 0 .. year 9999 with a granularity of 10ms. ✨

The short ISO-9660 time format only allows to represent year 1900 .. year 2155 with a granularity of 1s. so yeah, if you need year 9999 energy, this is your girl.

• -m glob — excludes glob from being written to CDROM. glob is a shell wildcard-style pattern that must match part of the filename (not the path as with option -x). Technically glob is matched against the d->d_name part of the directory entry. Multiple globs may be excluded. Example:

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. sneaky little recursive exclusion, love that for us 🙈

⚠️ 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. the docs are lying to you bestie, this is the real tea 🫖

• -exclude-list file — a file containing a list of globs to be excluded as above. batch exclusion, we stan efficiency 💖
• -max-iso9660-filenames — allows 37 chars in ISO-9660 filenames. This option forces the -N option as the extra name space is taken from the space reserved for ISO-9660 version numbers.

This violates the ISO-9660 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. 😭

💀 not me warning you about a literal buffer overflow — this is the dangerous one, bestie. be so serious with it.

• -M path — or -M device — or -dev device — specifies path to existing ISO-9660 image to be merged. The alternate form takes a SCSI device specifier that uses the same syntax as the dev= parameter of cdrecord. The output of mkisofs will be a new session which should get written to the end of the image specified in -M. Typically this requires multi-session capability for the recorder and cdrom drive that you are attempting to write this image to. This option may only be used in conjunction with the -C option. 👑
• -modification-date date-spec — sets the modification date in the primary volume descriptor (PVD) to a value different from the current time. This allows e.g. to set up an intentional UUID for grub. custom timestamps, main character energy ⭐

The format of date-spec is:

yyyy[mm[dd[hh[mm[ss]]]]][.hh][+-ghgm]

The fields are year, month, day of month, hour, minute, second, hundreds of a second, GMT offset in hours and minutes. The time is interpreted as local time. 🕰️

Year and the GMT offset are four digit fields, all other fields take two digits. The GMT offset may be between -12 and +13 hours in 15 minute steps. Locations east to Greenwich have positive values. The value is the sum of the time zone offset and the effects from daylight saving time. Omited values are replaced by the minimal possible values. If the GMT offset is omited, it is computed from the local time value that has been supplied. (yes it says "omited" — we're keeping it, no editing the source, periodt) 💅

Between year and month as well as between month and day of month, a separator chosen from '/' and '-' may appear. In this case, the year may be a two digit number with values 69..99 representing 1969..1999 and values 00..68 representing 2000..2068. Between date and time spec, an optional space is permitted. Between hours and minutes as well as between minutes and seconds, an optional ':' separator is permitted. This allows mkisofs to parse the popular POSIX date format created by: 🦋

date "+%Y-%m-%d %H:%M:%S %z"

💀 Note that the possible range for date-spec for 32 bit programs is limited to values up to 2038 Jan 19 04:14:07 GMT. the classic 2038 problem says hi, bestie 😭

• -N — or -omit-version-number — omits version numbers from ISO-9660 file names. This violates the ISO-9660 standard, but no one really uses the version numbers anyway. Use with caution. honestly? fair. nobody was checking those version numbers fr fr 🎀
• -new-dir-mode mode — mode to use when creating new directories in the iso fs image. The default mode in the absence of a -dir-mode option is 0555. permissions, but make it directories 💜
• -nobak — or -no-bak — do not include backup files files on the ISO-9660 filesystem. If the -no-bak option is specified, files that contain the characters '~' or '#' or end in '.bak' will not be included (these are typically backup files for editors under UNIX). bye bye editor leftovers, we don't want you on the disc 🌸

(yep, "files files" — the original said it twice and so am I, iconic typo behavior)

• -no-limit-pathtables — a ISO-9660 filesystem contains path tables that contain a list of directories. This list may contain many directories but only 65535 of them may be parent directories. When -no-limit-pathtables is in use, further parent directories will be folded to the root directory and the resulting filesystem will no longer be usable on DOS. 🙈

⚠️ trading DOS compatibility for headroom — know the tradeoff before you commit, bestie.

• -no-long-rr-time — uses the short ISO-9660 time format for the file time stamps used in Rock Ridge. This time format allows to represent year 1990 .. year 2155 with a granularity of one second. ⏳
• -force-rr — do not use the automatic Rock Ridge attributes recognition for previous sessions. This helps to show rotten ISO-9660 extension records as e.g. created by NERO burning ROM. rotten records 😭 exposing the chaos so you can actually see it 🔥
• -no-rr — do not use the Rock Ridge attributes from previous sessions. This may help to avoid getting into trouble when mkisofs finds illegal Rock Ridge signatures on an old session. skip the drama entirely, we love a clean slate ✨
• -no-split-symlink-components — don't split the SL components, but begin a new Continuation Area (CE) instead. This may waste some space, but the SunOS 4.1.4 cdrom driver has a bug in reading split SL components (link_size = component_size instead of link_size += component_size). 😭

Note that this option has been introduced by Eric Youngdale in 1997. It is questionable whether it makes sense at all. When it has been introduced, mkisofs did have a serious bug that did create defective CE signatures if a symlink contained `/../'. This CE signature bug in mkisofs has been fixed in May 2003. so like... legacy workaround for a bug that's already dead. make of that what you will 💀

• -no-split-symlink-fields — don't split the SL fields, but begin a new Continuation Area (CE) instead. This may waste some space, but the SunOS 4.1.4 and Solaris 2.5.1 cdrom driver have a bug in reading split SL fields (a `/' can be dropped). 🫠

Note that this option has been introduced by Eric Youngdale in 1997. It is questionable whether it makes sense at all. When it has been introduced, mkisofs did have a serious bug that did create defective CE signatures if a symlink contained `/../'. This CE signature bug in mkisofs has been fixed in May 2003. same lore, different driver bug. slay for consistency i guess 👑

• -o filename — is the name of the file to which the ISO-9660 filesystem image should be written. This can be a disk file, a tape drive, or it can correspond directly to the device name of the optical disc writer. If not specified, stdout is used. Note that the output can also be a block special device for a regular disk drive, in which case the disk partition can be mounted and examined to ensure that the premastering was done correctly. output destination, choose your fighter 💖
• -pad — pad the end of the whole image by 150 sectors (300 kB). If the option -B is used, then there is a padding at the end of the ISO-9660 partition and before the beginning of the boot partitions. The size of this padding is chosen to make the first boot partition start on 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 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. so yes bestie, it's already doing this unless you tell it not to 🫶

• -no-pad — do not Pad the end by 150 sectors (300 kB) and do not make the the boot partitions start on a multiple of 16 sectors. opt out of the safety padding at your own risk, love 🙈
• -path-list file — a file containing a list of pathspec directories and filenames to be added to the ISO-9660 filesystem. This list of pathspecs are processed after any that appear on the command line. If the argument is -, then the list is read from the standard input. bulk adding, stdin edition — we love a piping moment 🦋
• -P — another fossil alert 🦕 outdated option reserved by POSIX.1-2001, use -publisher instead. This option will get POSIX.1-2001 semantics with mkisofs-3.02.
• -publisher publisher_id — specifies a text string that will be written into the volume header. This should describe the publisher of the CDROM, usually with a mailing address and phone number. There is space on the disc for 128 characters of information. The related Joliet entry is limited to 64 characters. This parameter can also be set in the file .mkisofsrc with PUBL=. If specified in both places, the command line version is used. 👑
• -p preparer_id — or -preparer preparer_id — specifies a text string that will be written into the volume header. This should describe the preparer of the CDROM, usually with a mailing address and phone number. There is space on the disc for 128 characters of information. The related Joliet entry is limited to 64 characters. This parameter can also be set in the file .mkisofsrc with PREP=. If specified in both places, the command line version is used. credits where credits are due ✨
• -posix-H — follow all symbolic links encountered on command line when generating the filesystem. just the ones on the command line, bestie — this is the careful version 🎀
• -posix-L — follow all symbolic links when generating the filesystem. When this option is not in use, symbolic links will be entered using Rock Ridge if enabled, otherwise the file will be ignored. the full send version, no symlink left behind 💅
• -posix-P — bestie, this says: do not follow symbolic links when generating the filesystem. And fun fact, that's literally the default already. If you drop -posix-P after -posix-H or -posix-L, it resets whatever those two just did. Undo button energy 💅
• -print-size — prints the estimated filesystem size in multiples of the sector size (2048 bytes) and then dips ✌️. You need this for Disk At Once mode, and with some CD-R drives when you're piping straight into cdrecord. Like, you gotta know how big the filesystem is before the actual CD-creation happens, y'know? So -print-size lets you get that number from a "dry-run" before the CD is actually written. Old versions of mkisofs wrote this info (among other stuff) to stderr — but that turned out to be hard to parse 😭, so now the bare number gets printed on stdout too. Writing a simple shell script? Redirect stderr and catch the number from stdout, like:

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

mkisofs ... | cdrecord ... tsize=${cdblocks}s -

• -quiet — makes mkisofs even less verbose. No progress output at all. Silent queen behavior 🤫
• -R
• -rock — generates SUSP and RR records using the Rock Ridge protocol to further describe the files on the ISO-9660 filesystem. Rock Ridge is the whole reason you can get POSIX-like file metadata in there: permissions, extended time stamps, user/group is'd, link counts, inode numbers and symbolic links. And the glow-up? Rock Ridge lets you archive hierarchy trees with unlimited depth 🔥
• -r
• -rational-rock — like -R but the file ownership and modes get set to way more useful values. The uid and gid are set to zero, because honestly they're usually only useful on the author's system and not useful to the client. All the file read bits get set true, so files and directories are globally readable on the client. If any execute bit is set for a file, set all of the execute bits, so executables are globally executable on the client. If any search bit is set for a directory, set all of the search bits, so directories are globally searchable on the client. All write bits get cleared, because the CD-Rom will be mounted read-only in any case, duh. And if any of the special mode bits are set, clear them — file locks aren't useful on a read-only filesystem, and set-id bits are not desirable for uid 0 or gid 0. On Win32, the execute bit gets set on all files — that's just a result of the lack of file permissions on Win32 and the Cygwin POSIX emulation layer, not a vibe choice. See also -uid -gid, -dir-mode, -file-mode and -new-dir-mode. 🫶
• -relaxed-filenames — lets ISO-9660 filenames include digits, upper case characters and all other 7 bit ASCII characters (resp. anything except lowercase characters). It violates the ISO-9660 standard, but it happens to work on many systems. Use with caution, babe ⚠️
• -root dir — moves all files and directories into dir in the image. Essentially the same as using -graft-points and adding dir in front of every pathspec, but easier to use. And dir may actually be several levels deep — it's created with the same permissions as other graft points. 🌸
• -rrip110 — creates ISO-9660 filesystem images that follow the old Rrip Version-1.10 standard from 1993. You may need this if you know of systems that don't implement the Rrip protocol correctly and you'd like the filesystem to be read by such a system. Currently no such system is known 😭. Also: if a filesystem has been created with -rrip110, the Rock Ridge attributes do not include inode number information. Vintage!
• -rrip112 — creates ISO-9660 filesystem images that follow the new Rrip Version-1.12 standard from 1994. This is the default. Fresh ✨
• -old-root dir — necessary when writing a multisession image and the previous (or even older) session was written with -root dir. Using a directory name not found in the previous session causes mkisofs to abort with an error. Without this option, mkisofs wouldn't be able to find unmodified files and would be forced to write their data into the image once more. Iconic for incremental backups — -root and -old-root are meant to be used together 💖

The initial session would e.g. use: mkisofs -root backup_1 dirs. The next incremental backup with mkisofs -root backup_2 -old-root backup_1 dirs. would take another snapshot of these directories. The first snapshot would be found in backup_1, the second one in backup_2, but only modified or new files need to be written into the second session.

Without these options, new files would be added and old ones would be preserved — but old ones would be overwritten if the file was modified. Recovering the files by copying the whole directory back from CD would also restore files that were deleted intentionally 🙈. And accessing several older versions of a file requires support by the operating system to choose which sessions are to be mounted.

• -short-rr-time — use the short ISO-9660 time format for the file time stamps used in Rock Ridge. This time format allows to represent year 1990 .. year 2155 with a granularity of one second. Time traveler chic ⏳
• -s sector type
• -sectype sector type — sets the sector type to be used for the output file with the ISO-9660 filesystem. The sector type may be one of:
  • data — this is the default. Results in standard CD-ROM data sectors with 2048 bytes per sector. 👑
  • xa1 — sets the sector type to CD-ROM XA mode 1 with 2056 bytes per sector. This sector type is the official sector type for multi-session CDs, and it should be used together with the -XA option of mkisofs. It's required to write Kodak Photo CDs and Kodak Picture CDs. Use the -xa1 option from cdrecord to tell cdrecord to write CD-ROM XA mode 1 sectors. Do not use for DVD or BluRay media. 🚫
  • raw — sets the sector type to raw audio sectors with 2352 bytes per sector. This is reserved for future enhancements. Do not use for DVD or BluRay media. 🚫
• -sort sort file — sorts file locations on the media. Sorting is controlled by a file containing pairs of filenames and sorting offset weighting. Higher weighting = the file lands closer to the beginning of the media; lower weighting = closer to the end. There must be only one space or tabs character between the filename and the weight, and the weight must be the last characters on a line. The filename is taken to include all the characters up to, but not including, the last space or tab character on a line — that's so space characters can be in, or at the end of, a filename. Ngl this option does not sort the order of the file names that appear in the ISO-9660 directory; it sorts the order in which the file data is written to the CD image, which may be useful to optimize the data layout on a CD. See README.sort for more details. 📚
• -isort sort file — similiar to -sort but the case of the filenames in the sort file is ignored. Case-blind and unbothered 💅
• -sparc-boot img_sun4,img_sun4c,img_sun4m,img_sun4d,img_sun4e — see the -B option above. (Yep, that's the whole thing, go look up 👀)
• -sparc-label label — sets the Sun disk label name for the Sun disk label that is created with the -sparc-boot option. Sun-baked branding ☀️
• -split-output — splits the output image into several files of approximately 1 GB. This helps to create DVD sized ISO-9660 images on operating systems without large file support. cdrecord will concatenate more than one file into a single track if writing to a DVD. To make -split-output work, the -o filename option must be specified. The resulting output images will be named: filename_00,filename_01,filename_02... ✂️
• -stream-media-size # — selects streaming operation and sets the media size to # sectors. This lets you pipe the output of the tar program into mkisofs and create an ISO-9660 filesystem without needing an intermediate tar archive file, which is honestly so slay. If this option has been specified, mkisofs reads from stdin and creates a file with the name STREAM.IMG. The maximum size of the file (with padding) is 200 sectors less than the specified media size. If -no-pad has been specified, the file size is 50 sectors less than the specified media size. If the file is smaller, then mkisofs will write padding — and that may take a while 😴

Heads up bestie: -stream-media-size creates simple ISO-9660 filesystems only, and may not be used together with multi-session or hybrid filesystem options.

• -stream-file-name name — sets the file name used with -stream-media-size # to a value different from STREAM.IMG. If this option is used, the filesystem is created as if -iso-level 4 has been specified. 🏷️
• -sunx86-boot UFS-img,,,AUX1-img — specifies a comma separated list of filesystem images that are needed to make a bootable CD for Solaris x86 systems. 🖥️

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

okay so if -sunx86-boot was the vibe you went with, here's what your first sector is giving: a PC fdisk label, and inside it a Solaris type 0x82 fdisk partition that starts at offset 512 and spans the whole entire CD. and that's not all — for that Solaris type 0x82 fdisk partition, there's also a SVr4 disk label chillin' at offset 1024 in the first sector of the CD. that disk label says slice 0 is for the first (usually UFS type) filesystem image that boots the PC, and slice 1 is for the ISO-9660 image. slice 2 spans the whole CD, and slice 3 ... slice 7 are up for grabs for any additional filesystem images you specified with this option 🫶

a Solaris x86 boot CD uses a 1024 byte sized primary boot that uses the El-Torito no-emulation boot mode, plus a secondary generic boot that lives in CD sectors 1..15. which is literally why you have to specify both -b bootimage -no-emul-boot and -G genboot, no cap. both. not one. both 💅

• -sunx86-label label — sets the SVr4 disk label name for the SVr4 disk label that gets created with the -sunx86-boot option. cute little name tag for your label 🎀
• -sysid ID — specifies the system ID. there's space on the disc for 32 characters of info. you can also set this in the .mkisofsrc file with SYSI=system_id. if you set it in both places, the command line wins, always ⭐
• -T
• -translation-table — generates a file TRANS.TBL in each directory on the CDROM, which helps establish the correct file names on systems that aren't Rock Ridge capable. there's also info in there showing the major and minor numbers for block and character devices, and every symlink gets the name of the link file given. it's giving ✨helpful✨
• -table-name TABLE_NAME — alternative translation table file name (see the one right above, bestie). this implies the -T option. and if you're creating a multi-session image you must use the same name as in the previous session, okay? no switching it up mid-way 🙈
• -ucs-level level — sets the Unicode conformance level in the Joliet SVD. default level is 3, and you can set it to 1..3 with this option 🦋
• -UDF — includes a UDF hybrid in the generated filesystem image. but like — since mkisofs always creates an ISO-9660 filesystem, it is not possible to create UDF only images. sad but true 😭. also heads up: UDF wastes the space from sector ~20 to sector 256 at the beginning of the disk, on top of the space needed for the real UDF data structures. it's lowkey greedy ngl
• -udf — rationalized UDF with user and group set to 0 and with simplified permissions. peep the -r option for more info 👑
• -udf-symlinks — supports symlinks in UDF filesystems. this is the default ✨
• -no-udf-symlinks — do not support symlinks in UDF filesystems. the opposite vibe 💀
• -uid uid — overrides the uid read from the source files to the value of uid. specifying this option automatically enables Rock Ridge extensions. it just comes with the package 🎁
• -use-fileversion — the option -use-fileversion lets mkisofs use file version numbers from the filesystem. if you don't specify it, mkisofs creates a version number of 1 for all files. file versions are strings in the range ;1 to ;32767. this option is the default on VMS 🌸
• -U
• -untranslated-filenames — allows "Untranslated" filenames, completely violating the ISO-9660 standards described above. it forces on the -d, -l, -N, -allow-leading-dots, -relaxed-filenames, -allow-lowercase, -allow-multidot and -no-iso-translate flags. it lets you have more than one . character in the filename, and mixed case filenames too. this is useful on HP-UX systems, where the built-in CDFS filesystem does not recognize ANY extensions. > use with extreme caution, bestie, i'm serious 🚨
• -no-iso-translate — does not translate the characters # and ~ which are invalid for ISO-9660 filenames. these characters are, though, invalid-often used by Microsoft systems 😬. this violates the ISO-9660 standard, but it happens to work on many systems. > use with caution 🫶
• -V volid — specifies the volume ID (that's the volume name or label, same thing) to be written into the master block. there's space on the disc for 32 characters of info. you can also set this in .mkisofsrc with VOLI=id, and if both are set, the command line wins. note: if you assign a volume ID, this is the name that'll be used as the mount point by the Solaris volume management system, and the name assigned to the disc on a Microsoft Win32 or Apple Mac platform. so basically it's the name everywhere, main character energy 👑
• -volset ID — specifies the volset ID. there's space on the disc for 128 characters of info. the related Joliet entry is limited to 64 characters though 🙃. you can also set this in .mkisofsrc with VOLS=volset_id, and if it's in both places, command line wins, as always ⭐
• -volset-size # — sets the volume set size to #. the volume set size is the number of CD's that are in a CD volume set. a volume set is a collection of one or more volumes, on which a set of files is recorded 📚

so like, Volume Sets are not intended to be used to create a set of numbered CD's that are part of, e.g., an Operation System installation set of CD's. Volume Sets are rather used to record a big directory tree that wouldn't fit on a single volume. each volume of a Volume Set contains a description of all the directories and files that are recorded on the volumes where the sequence numbers are less than, or equal to, the assigned Volume Set Size of the current volume. it's a whole ecosystem 🌀

mkisofs currently does not support a -volset-size that is larger than 1. 💀

the option -volset-size must be specified before -volset-seqno on each command line. order matters, bestie 🎯

• -volset-seqno # — sets the volume set sequence number to #. the volume set sequence number is the index number of the current CD in a CD set. and again: the option -volset-size must be specified before -volset-seqno on each command line. yes i'm repeating it, it's that important 🫶
• -v
• -verbose — verbose execution. and if you give it twice on the command line, extra debug information gets printed. double the flag, double the lore 🔥
• -x path — excludes path from being written to the CDROM. path must be the complete pathname that results from concatenating the pathname given as the command line argument and the path relative to this directory. you can exclude multiple paths. example, look:

mkisofs -o cd -x /local/dir1 -x /local/dir2 /local

NOTE: the -m and -x option descriptions 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. so yeah, the docs are lying to you a little, i'm just the messenger 😭

• -XA — generates XA iso-directory attributes with original owner and mode information. this option is required to create conforming multi-session CDs as used by the Kodak Photo CD and the Kodak Picture CD 📸. a conforming XA CD uses CD-ROM XA mode 1 sectors — see the -sector xa2 option for more info ✨
• -xa — generates XA iso-directory attributes with rationalized owner and mode information. user ID and group ID are set to 0. see -XA for more info (it's the glow-up version of the same thing basically) 🦋
• -z — generates special RRIP records for transparently compressed files. this is only of use and interest for hosts that support transparent decompression, such as Linux 2.4.14 or later 🐧. you must specify the -R or -r options to enable RockRidge, and generate compressed files using the mkzftree utility before running mkisofs. 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'll need to call mkzftree by hand to decompress the files. so like, it slays but only on one platform 🙈

✨ HFS OPTIONS ✨

Okay bestie, buckle up 💖 — this is the Mac-flavored part of mkisofs, like, the whole HFS/hybrid-disc situation. It's giving "vintage Apple chaos" and honestly? Iconic.

---

• -hfs — Create an ISO-9660/HFS hybrid CD. Bestie, this one wants friends: use it in conjunction with -map, -magic and/or the various double-dash options listed down below. It doesn't really slay on its own 🫶
• -no-hfs — Do not create an ISO-9660/HFS hybrid CD, even though other options might be out here implying that you should. It's the "no thank you, not today" of flags 💅
• -apple — Create an ISO-9660 CD with Apple's extensions. Similar to -hfs, except that the Apple Extensions to ISO-9660 are added instead of creating an HFS hybrid volume. Okay so important lore drop: former mkisofs versions did include Rock Ridge attributes by default if -apple was specified. This version of mkisofs does not do this anymore 😭 So if you like to have Rock Ridge attributes, you need to specify this separately. No freebies, periodt.
• -map mapping_file — Use the mapping_file to set the CREATOR and TYPE information for a file based on the filename's extension. A filename is mapped only if it is not one of the known Apple/Unix file formats. See the HFS CREATOR/TYPE section below, iykyk 🌸
• -magic magic_file — The CREATOR and TYPE information is set by using a file's magic number (usually the first few bytes of a file). The magic_file is only used if a file is not one of the known Apple/Unix file formats, or the filename extension has not been mapped using the -map option. See the HFS CREATOR/TYPE section below for more deets ✨
• -hfs-creator CREATOR — Set the default CREATOR for all files. Must be exactly 4 characters — no more, no less, she measures 🔥 See the HFS CREATOR/TYPE section below.
• -hfs-type TYPE — Set the default TYPE for all files. Must be exactly 4 characters. Same deal, same energy. See the HFS CREATOR/TYPE section below 💜
• -probe — Search the contents of files for all the known Apple/Unix file formats. See the HFS MACINTOSH FILE FORMATS section below for more about these formats. But okay, real talk 🙈 the only way to check for MacBinary and AppleSingle files is to open and read them — so this option may increase processing time. It is better to use one or more double-dash options given below if the Apple/Unix formats in use are known. Basically: don't brute-force when you can just tell her what to look for 💀
• -no-desktop — Do not create (empty) Desktop files. New HFS Desktop files will be created when the CD is used on a Macintosh (and stored in the System Folder). By default, empty Desktop files are added to the HFS volume — so this flag is you saying "not on my watch" 🎀
• -mac-name — Use the HFS filename as the starting point for the ISO-9660, Joliet and Rock Ridge file names. See the HFS MACINTOSH FILE NAMES section below for more info 🦋
• -boot-hfs-file driver_file — Installs the driver_file that may make the CD bootable on a Macintosh. See the HFS BOOT DRIVER section below. (Alpha) — yes, alpha, we're in experimental territory, bestie ⭐
• -part — Generate an HFS partition table. By default, no partition table is generated, but some older Macintosh CDROM drivers need an HFS partition table on the CDROM to be able to recognize a hybrid CDROM. Vintage tech being picky, classic 🙄
• -auto AutoStart_file — Make the HFS CD use the QuickTime 2.0 Autostart feature to launch an application or document. The given filename must be the name of a document or application located at the top level of the CD. The filename must be less than 12 characters. (Alpha). Short names only, she's old-school 🍓
• -cluster-size size — Set the size in bytes of the cluster or allocation units of PC Exchange files. Implies the --exchange option. See the HFS MACINTOSH FILE FORMATS section below.
• -hide-hfs glob — Hide glob from the HFS volume. Lowkey important: the file or directory will still exist in the ISO-9660 and/or Joliet directory. glob is a shell wild-card-style pattern that must match any part of the filename. Multiple globs may be excluded. Example:

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 — fr fr, no trailing slash, she WILL not match 😤 See README.hide for more details.

• -hide-hfs-list file — A file containing a list of globs to be hidden as above. Bulk hiding, we love efficiency 💖
• -hfs-volid hfs_volid — Volume name for the HFS partition. This is the name that is assigned to the disc on a Macintosh and replaces the volid used with the -V option. So like, she overrides. Main character behavior 👑
• -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 Macintosh desktop. Folder location and size on screen, its scroll positions, folder View (view as Icons, Small Icons, etc.) are also preserved. This option may become set by default in the future. (Alpha). Preserving your whole desktop vibe, we're obsessed 🌈
• -root-info file — Set the location, size on screen, scroll positions, folder View etc. for the root folder of an HFS volume. See README.rootinfo for more information. (Alpha)
• -prep-boot FILE — PReP boot image file. Up to 4 are allowed. See README.prep_boot (Alpha)
• -chrp-t — Create a CHRP boot in boot partition 1. See -prep-boot for further information.
• -input-hfs-charset charset — Input charset that defines the characters used in HFS file names when used with the -mac-name option. The default charset is cp10000 (Mac Roman) cp10000 (Mac Roman) — and yes bestie, the manpage literally says it twice, I'm just being faithful 😭💀 See the CHARACTER SETS and HFS MACINTOSH FILE NAMES sections below for more details.
• -output-hfs-charset charset — Output charset that defines the characters that will be used in the HFS file names. Defaults to the input charset. See the CHARACTER SETS section below for more details.
• -hfs-unlock — By default, mkisofs will 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 the HFS PROBLEMS/LIMITATIONS section below for warnings about using this option — like, read the warnings, bestie, please 🙏
• -hfs-bless folder_name — "Bless" the given directory (folder). This is usually the System Folder and is used in creating HFS bootable CDs. The name of the directory must be the whole path name as mkisofs sees it. e.g. if the given pathspec is ./cddata and the required folder is called System Folder, then the whole path name is "./cddata/System Folder" (remember to use quotes if the name contains spaces). Quotes are not optional, she has a space in her name 💅
• -hfs-parms PARAMETERS — Override certain parameters used to create the HFS file system. Unlikely to be used in normal circumstances. See the libhfs_iso/hybrid.h source file for details. Deep lore, only for the brave 🧚

---

🦋 the double-dash Apple/Unix format squad 🦋

• --cap — Look for AUFS CAP Macintosh files. Search for CAP Apple/Unix file formats only — searching for the other possible Apple/Unix file formats is disabled, unless other double-dash options 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 MacOS X AppleDouble Macintosh files.
• --osx-hfs — Look for MacOS X HFS Macintosh files.

That's the whole squad, bestie — pick your fighters wisely 💜🔥

🎀 CHARACTER SETS 🎀

okay so bestie, this is the part where things get spicy 🌶️ — mkisofs deals with file names the POSIX way, as strings of 8-bit characters. iconic of it. but here's the vibe check: 8-bit characters are absolutely not enough to represent all the codings for all the languages in the world 😭. Unicode, aka ISO-10646, defines character codings that need at least 21 bits to represent every known language. yeah. that many.

and those big-brain codings can show up as UTF-32, UTF-16 or UTF-8. quick rundown:

• UTF-32 is a plain 32-bit coding but honestly it seems kinda uncommon, ngl.
• UCS-2 is what Microsoft uses with Win32. it's similar to UTF-16 but with the L it that it only supports a 16 bit subset (except when surrogates are used) of all codes, and that 16-bit characters aren't compliant with the POSIX filesystem interface. not the flex it thinks it is 💀

Modern UNIX operating systems may use UTF-8 coding for filenames, and that's the slay option — it lets you 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) it maps 1:1 to a UTF-32 or UTF-16 coded Unicode character. and if a character is coded in 7-Bit ASCII (used in USA and other countries with limited character set) it maps 1:1 to a UTF-32, UTF-16 or UTF-8 coded Unicode character. character codes that can't 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. so it's giving ✨efficiency✨ but with a little extra.

lowkey the dream would be: if all operating systems used UTF-8 coding, mkisofs wouldn't need to recode characters in file names at all. but no 🙈. Apple uses completely nonstandard codings and Microsoft uses a Unicode coding that is not compatible with the POSIX filename interface. so here we are, recoding away.

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 Microsoft uses — that the local operating system in use is using. the characters in a character set will reflect the region or natural language used by the user. so it's very much a "your vibe, your region" situation 🌍.

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 doesn't follow ISO standards, which reserve the range 0x80-0x9f for control characters and only allow 0xa0-0xff for other characters. standards? never heard of her 💅.

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. the chaos 😭.

To make matters more complicated (because of course they do), 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 that 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. UNIX girlies stay winning 👑.

So as long as not all operating systems and applications 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. and that's where the four options below come in 🫶

---

🌸 -input-charset

Defines the local character set you are using on your host machine. any character set conversions that take place will use this character set as the starting point. the default input character sets are cp437 on DOS based systems and iso8859-1 on all other systems.

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. two-for-one deal, we love to see it ✨.

🌸 -output-charset

Defines the character set that will be used with for the Rock Ridge names on the CD. defaults to the input character set. only likely to be useful if used on a non-Unix platform. e.g. using mkisofs on a Microsoft Win32 machine to create Rock Ridge CDs. if you're using mkisofs on a Unix machine, it's likely that the output character set will be the same as the input character set. so like, don't stress about it on Unix, bestie 💜.

🌸 -input-hfs-charset

Defines the HFS character set used for HFS file names decoded from any of the various Apple/Unix file formats. only useful when used with -mac-name option. see the HFS MACINTOSH FILE NAMES for more information. defaults to cp10000 (Mac Roman). 🍎

🌸 -output-hfs-charset

Defines the HFS character set used to create HFS file names from the input character set in use. in most cases this will be from the character set given with the -input-charset option. defaults to the input HFS character set.

---

The default character set is built into mkisofs (iconic, self-sufficient queen 👑). a number of further character sets are read in from the filesystem by mkisofs from a directory relatively to the install path. to get a listing, use:

mkisofs -input-charset help

Additional character sets from iconv(1) may be used on systems that support iconv(1). in this case, call iconv -l to get a list of valid character sets from this coding method. to force an iconv(1) based coding, use iconv:name instead of name for the character set. the colon is doing all the heavy lifting tbh 💅.

If you're using non iconv(1) based character sets, 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. a given character set will be read from a file whenever the supplied name contains a /.

The format of the character set files is the same as the mapping files available from http://www.unicode.org/Public/MAPPINGS. the format of these files is:

Column #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. no drama, no complaints 🌈.

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. so like, UTF-16 and UTF-32 are simply not invited to the party 🙅‍♀️

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. vintage behaviour, retro vibes 🎀.

The ISO-9660 file names generated from the input filenames are not converted from the input character set. the ISO-9660 character set is a very limited subset of the ASCII characters, so any conversion would be pointless. periodt.

Any character that mkisofs can not convert will be replaced with a '_' character. simple as that 🦋.

🎀 HFS CREATOR/TYPE 🎀

Okay so bestie, a Macintosh file has two properties attached to it that define which application created the file — the CREATOR — and what data the file contains — the TYPE. Both are (exactly) 4-letter strings, no cap. Usually this lets a Macintosh user double-click on a file and launch the correct application etc. You can find the CREATOR and TYPE of a particular file 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:

# 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 column EXTN defines the Unix filename extension to be mapped. The default mapping for any filename extension that doesn't match is defined with the "*" character.
• The Xlate column defines the type of text translation between the Unix and Macintosh file; it is ignored by mkisofs, but is kept to be compatible with aufs(1). Although mkisofs does not alter the contents of a file, if a binary file has its TYPE set as 'TEXT', it may be read incorrectly on a Macintosh. Therefore a better choice for the default TYPE may be '????'.
• The CREATOR and TYPE keywords must be 4 characters long and enclosed in single quotes.
• The comment field is enclosed in double quotes — it is ignored by mkisofs, but is kept to be compatible with aufs.

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:

# 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 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, because each file has to be opened and read to find its magic number. 😭

In summary, bestie:

• 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 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

🍎 HFS MACINTOSH FILE FORMATS 🍎

Okay bestie, deep breath, because this is the part where Mac and Unix have to learn to coexist 💖

Macintosh files have two parts, called the Data fork and the Resource fork. Either one may be empty, no drama. But Unix (and honestly a bunch of other OSs too) can only cope with files that have one part — one fork. That's it. That's the whole skill set. 😭

And if that weren't already giving "incompatible besties," Macintosh files also have a bunch of attributes attached to them. The two that matter most are TYPE and CREATOR. Unix? No concept of those either. None. Zero. 💀

Like, picture this: a Macintosh file might be a JPEG image where the actual image is stored in the Data fork and a desktop thumbnail is stored in the Resource fork. Usually it's the info in the data fork that's actually useful across platforms, iykyk.

So to store a Macintosh file on a Unix filesystem, somebody had to find a way to cope with the two forks and the extra attributes (which we call the finder info). And here's the messy part: it seems that every software package that stores Macintosh files on Unix has chosen a completely different storage method. Every. Single. One. 🙈

The Apple/Unix formats that mkisofs (partially) supports are:

💅 CAP AUFS format

• Data fork stored in a file.
• Resource fork in subdirectory .resource with same filename as data fork.
• Finder info in .finderinfo subdirectory with same filename.

💅 AppleDouble/Netatalk

• Data fork stored in a file.
• Resource fork stored in a file with same name prefixed with %.
• Finder info also stored in same % file.
• Netatalk uses the same format, but the resource fork/finderinfo stored in subdirectory .AppleDouble with same name as data fork.

💅 AppleSingle

• Data structures similar to above, except both forks and finder info are stored in one file. One file! Efficient queen ✨

💅 Helios EtherShare

• Data fork stored in a file.
• Resource fork and finder info together in subdirectory .rsrc with same filename as data fork.

💅 IPT UShare

• Very similar to the EtherShare format, but the finder info is stored slightly differently. Slightly. 👀

💅 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 subdirectory resource.frk (or RESOURCE.FRK).
• Finder info as one record in file finder.dat (or FINDER.DAT).
• Separate finder.dat for each data fork directory.

Note: mkisofs needs to know the native FAT cluster size of the disk that the PC Exchange files are on (or have been copied from). This size is given by the -cluster-size option. The cluster or allocation size can be found by using the DOS utility CHKDSK.

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.

💅 SGI/XINET

Used by SGI machines when they mount HFS disks.

• Data fork stored in a file.
• Resource fork in subdirectory .HSResource with same name.
• Finder info as one record in file .HSancillary.
• Separate .HSancillary for each data fork directory.

💅 Thursby Software Systems DAVE

Allows Macintoshes to store Apple files on SMB servers.

• Data fork stored in a file.
• Resource fork in subdirectory resource.frk.
• Uses the AppleDouble format to store resource fork.

💅 Services for Macintosh

Format of files stored by NT Servers on NTFS filesystems.

• Data fork is stored as "filename".
• Resource fork stored as a NTFS stream called "filename:AFP_Resource".
• The finder info is stored as a NTFS stream called "filename:Afp_AfpInfo".
• These streams are normally invisible to the user.

Warning: mkisofs only partially supports the SFM format. If an HFS file or folder stored on the NT server contains an illegal NT character in its name, then NT converts these characters to Private Use Unicode characters. The characters are: " * / < > ? | also a space or period if it is the last character of the file name, character codes 0x01 to 0x1f (control characters) and Apple' apple logo.

Unfortunately, these private Unicode characters are not readable by the mkisofs NT executable. Therefore any file or directory name containing these characters will be ignored — including the contents of any such directory. 😭 That's rough, bestie.

💅 MacOS X AppleDouble

When HFS/HFS+ files are copied or saved by MacOS X on to a non-HFS file system (e.g. UFS, NFS etc.), the files are stored in AppleDouble format.

• Data fork stored in a file.
• Resource fork stored in a file with same name prefixed with ._.
• Finder info also stored in same ._ file.

💅 MacOS X HFS (Alpha)

Not really an Apple/Unix encoding, but actual HFS/HFS+ files on a MacOS X system.

• Data fork stored in a file.
• Resource fork stored in a pseudo file with the same name with the suffix /rsrc.
• The finderinfo is only available via a MacOS X library call.

Notes: (also see README.macosx) - Only works when used on MacOS X. - If a file is found with a zero length resource fork and empty finderinfo, it is assumed not to have any Apple/Unix encoding — therefore a TYPE and CREATOR can be set using other methods.

---

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. Peep the HFS MACINTOSH FILE NAMES section below for that whole situation 👀

When using the -apple option, the TYPE and CREATOR are stored in the optional System Use or SUSP field in the ISO-9660 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). Package deal, bestie 🎀

The Apple extensions require the resource fork to be stored as an ISO-9660 associated file. This is just like any normal file stored in the ISO-9660 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 ISO-9660 volume. The HFS directory references the same data and resource fork files described above. Sneaky but functional 💅

In most cases, it's better to use the -hfs option instead of the -apple option, as the latter imposes the limited ISO-9660 characters allowed in filenames. But plot twist — 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. That's important when the total size of the source files is approaching 650MB 👑🔥

🌸 HFS MACINTOSH FILE NAMES 🌸

Okay bestie, so here's the tea on how names get picked for the HFS side of your CD 💅 Where possible, the HFS filename that's stored along with an Apple/Unix file is what gets used for the HFS part of the CD. Slay. But — and this is the plot twist — not all the Apple/Unix encodings actually store the HFS filename with the finderinfo. In those cases, the Unix filename gets used instead, with escaped special characters. The special characters include / and any characters with codes over 127. 😭

Aufs escapes these characters by going ":" followed by the character code as two hex digits. Netatalk and EtherShare have a similar scheme, but they use "%" instead of a ":". Classic.

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. And if "xx" are not hex digits ([0-9a-fA-F]), then they're left alone — although any remaining ":" gets converted to "%", since colon is the HFS directory separator. Care must be taken here, because an ordinary Unix file with %xx or :xx will also get converted. e.g.

This:2fFile   converted to This/File

This:File     converted to This%File

This:t7File   converted to This%t7File

So even though 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. Little uniqueness hack, love that for it 🫶

If an HFS filename exists for a file, then mkisofs can use this name as the starting point for the ISO-9660, 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.

So picture this: 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 that's the name that would appear on the HFS part of the CD. However, since mkisofs uses the Unix name as the starting point for the other names, the ISO-9660 name generated will probably be SOMEIMAG.BIN and the Joliet/Rock Ridge would be someimage.gif.bin. Even though the actual data (in this case) is a GIF image. This option will use the HFS filename as the starting point and the ISO-9660 name will probably be SOMEIMAG.GIF and the Joliet/Rock Ridge would be someimage.gif. ✨

Quick heads up though: 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). You can specify the character set used with the -input-hfs-charset option. Other built in HFS character sets are: cp10006 (MacGreek), cp10007 (MacCyrillic), cp10029 (MacLatin2), cp10079 (MacIcelandic) and cp10081 (MacTurkish). Collect them all 💖

Note: the character codes used by HFS file names taken from the various Apple/Unix formats will not be converted, as they're 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 ISO-9660 and Joliet filenames, but since mkisofs expects to be dealing directly with Unix names, it leaves the Rock Ridge names as is. But because / is a legal HFS filename character, the -mac-name option converts / to _ in Rock Ridge filenames. Sneaky but necessary.

If the Apple extensions are used, then only the ISO-9660 filenames will appear on the Macintosh. However, since the Macintosh ISO-9660 drivers can use Level 2 filenames, you can use options like -allow-multidot without problems on a Macintosh — still take care over the names, though. 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 a mkisofs/mkhybrid problem 😭 All filenames will be in upper case when viewed on a Macintosh. And of course, DOS/Win3.X machines will not be able to see Level 2 filenames... 💀

---

🎀 HFS CUSTOM VOLUME/FOLDER ICONS 🎀

Want your HFS CD to have a cute custom icon? Obsessed. 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. Iconic. ✨

A custom folder icon is very similar — an invisible file called 'Icon\r' exists in the folder itself. Same energy, different location.

Probably the easiest way to create a custom icon that mkisofs can actually use is to format a blank HFS floppy disk on a Mac and paste an icon to its "Get Info" box. If you're using Linux with the HFS module installed, mount the floppy using something like:

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

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

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

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

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

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

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 ISO-9660 and Joliet trees. Fair.

To give a custom icon to a Joliet CD, follow the instructions found at: http://www.fadden.com/cdrfaq/faq03.html#[3-21]

---

👑 HFS BOOT DRIVER 👑

It may be possible to make the hybrid CD bootable on a Macintosh. Main character energy, frankly.

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

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. Okayyy 🔥

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 its 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 a 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. Fingers crossed bestie 🤞

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.

⚠️ 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. Don't say I didn't warn you 💀

---

🔥 EL TORITO BOOT INFORMATION TABLE 🔥

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. Like, seriously, use a copy. 😭

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). Math queen behavior 🧮💅

⚙️ CONFIGURATION ⚙️

So mkisofs has a whole little secret config file called .mkisofsrc, and it goes looking for it in a very specific order, bestie, so pay attention 💅:

1. the current working directory
2. the user's home directory
3. the directory where the mkisofs binary itself lives

That file is basically a list of lines shaped like TAG=value — and that's literally how you set some options without touching the command line. The case of the tag? Doesn't matter, APPI and appi are the same vibe ✨. Some fields in the volume header are not settable on the command line at all, but you can change them through this file, which is lowkey iconic of it. Wanna leave a comment? Easy — any line starting with a hash (#) character gets ignored. 🎀

• APPI — the application identifier, i.e. it should describe the application that will be on the disc. There's space on the disc for 128 characters of info, and the related Joliet entry is limited to 64 characters. You can override it with the -A command line option.
• COPY — the copyright information, often the name of a file on the disc containing the copyright notice. Space on the disc: 37 characters of info. Related Joliet entry: limited to 18 characters. Overridable with the -copyright command line option.
• ABST — the abstract information, often the name of a file on the disc containing an abstract. 37 characters of space on the disc. Joliet entry limited to 18 characters. Overridable with the -abstract command line option.
• BIBL — the bibliographic information, often the name of a file on the disc containing a bibliography. 37 characters on the disc. Joliet entry limited to 18 characters. Overridable with the -bilio command line option 👀 (yes, that's how it's spelled in the manpage, don't come for me).
• PREP — should describe the preparer of the CDROM, usually with a mailing address and phone number. Space on the disc: 128 characters of info, and the related Joliet entry is limited to 64 characters. Overridable with the -p command line option.
• PUBL — should describe the publisher of the CDROM, usually with a mailing address and phone number. 128 characters on the disc, Joliet entry limited to 64 characters. Overridable with the -publisher command line option.
• SYSI — the System Identifier. 32 characters of space on the disc. Overridable with the -sysid command line option.
• VOLI — the Volume Identifier. 32 characters of space on the disc. Overridable with the -V command line option.
• VOLS — the Volume Set Name. 128 characters of space on the disc, and the related Joliet entry is limited to 64 characters. Overridable with the -volset command line option.
• HFS_TYPE — the default TYPE for Macintosh files. Must be exactly 4 characters, no more no less, fr fr. Overridable with the -hfs-type command line option.
• HFS_CREATOR — the default CREATOR for Macintosh files. Must be exactly 4 characters. Overridable with the -hfs-creator command line option.

Also, mkisofs can be configured at compile time with defaults for many of these fields — check the file defaults.h for that 🫶.

---

🌈 EXAMPLES 🌈

Okay this is the fun part, actual copy-paste-able moments 💖.

Wanna make a plain, vanilla ISO-9660 filesystem image in the file cd.iso, where the directory cd_dir becomes the root directory of the CD ISO image? Say less:

% mkisofs -o cd.iso cd_dir

Want a CD with Rock Ridge extensions of the source directory cd_dir? Obsessed, here:

% mkisofs -o cd.iso -R cd_dir

Want that CD with Rock Ridge extensions of cd_dir but where all files have at least read permission and all files are owned by root? Slay:

% mkisofs -o cd.iso -r cd_dir

To write a tar archive directly to a CD that will later contain a simple ISO-9660 filesystem with the tar archive, call:

% star -c . | mkisofs -stream-media-size 333000 | \
        cdrecord dev=b,t,l -dao tsize=333000s -

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 ISO-9660', 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

---

Now THIS next one is the main character example, ok 😭 the way it's so clever. The following example puts different files on the CD that all have the name README, but have different contents when seen as a ISO-9660/RockRidge, Joliet or HFS CD.

The 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. Same deal for the Joliet and ISO-9660/RockRidge CD 💫.

There are probably all sorts of strange results possible with combinations of the hide options ... 💀 consider yourself warned bestie

To create a DVD-Audio of the DVD-Audio compliant source directory DVD:

% mkisofs -o dvda.iso -dvd-audio DVD

---

👑 AUTHOR 👑

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 its adaptation layer to mkisofs and newer parts (starting from 1997) of the utility. Joerg Schilling is the primary maintainer since 1999, this makes mkisofs Copyright (C) 1997-2014 Joerg Schilling.

HFS hybrid code Copyright (C) James Pearson 1997 ... 2001.

libhfs code Copyright (C) 1996, 1997 Robert Leslie.

libfile code Copyright (C) Ian F. Darwin 1986, 1987, 1989, 1990, 1991, 1992, 1994, 1995.

---

📝 NOTES 📝

Mkisofs may safely be installed suid root — which is lowkey needed sometimes, because it lets mkisofs read the previous session when creating a multi session image. 💅

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 ISO-9660 filesystem. Honestly the name mkisofs is probably a bit of a misnomer, since it not only creates the filesystem — it also populates it as well 🫠. But the "appropriate" tool name for a UNIX tool that creates populated filesystems — mkproto — is just not well known, so here we are.

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 in the directory tree that is visible with ISO-9660, but it is automatically hidden in the Rock Ridge tree ✨.

The sparc boot support that is implemented with the -sparc-boot options completely follows the official Sparc CD boot requirements from the Boot prom in Sun Sparc systems. Some Linux distributions for Sparc systems use a boot loader called SILO that unfortunately is not Sparc CD boot compliant 😭. It is annoyingly to see that the Authors of SILO don't fix SILO but instead provide a completely unneeded "patch" to mkisofs that incorporates far more source than the fix for SILO would need. 🍵

---

💀 BUGS 💀

• Does not properly read relocated directories in multi-session mode when adding data.

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.

• Does not re-use RR_MOVED when doing multi-session from TRANS.TBL

There may be some other ones. Please, report them to the author 🙏.

💀 HFS PROBLEMS/LIMITATIONS 💀

Okay so the HFS side had to make several assumptions about how the modified libhfs routines are supposed to work, and ngl there may be situations nobody thought of, or ran into when those assumptions fail. So there’s literally no guarantee that mkisofs will work as expected — although no major problem has shown up yet, fr fr. Most HFS features work fine, but some are not fully tested. Those are marked as Alpha above, iykyk.

• HFS filenames appear to support upper and lower case letters, but the filesystem is case insensitive — "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 an Apple/Unix encoded file called "oldname" is to added to the CD, then you can not use the command line:

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

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.
• However, if each session is created with the -part option, then each session will appear as separate volumes when mounted on a Mac. In this case, it is worth using the -V or -hfs-volid option to 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 to the HFS directory.
• Hybrid volumes may be larger than pure ISO-9660 volumes containing the same data. In some cases (e.g. DVD sized volumes) the hybrid volume may be significantly larger. As an HFS volume gets bigger, so does the allocation 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 be about 70Kb.
• The maximum number of files in an HFS volume is about 65500 — although the real limit will be somewhat less than this.
• 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.

🚨 Bestie, that -hfs-unlock caveat is not a vibe suggestion — no changes should be made to the contents of the volume unless you really know what you’re doing, because it’s not a “real” HFS volume. Periodt.

• 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 its 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 the -prep-boot or -chrp-boot options.
• mkisofs should be able to create HFS hybrid images over 4Gb, although this has not been fully tested.

---

👀 SEE ALSO 👀

• cdrecord(1), mkzftree(1), sfind(1), magic(5), apple_driver(8).

🔮 FUTURE IMPROVEMENTS 🔮

Some sort of gui interface. Lowkey iconic wishlist energy ✨

📦 AVAILABILITY 📦

• mkisofs is available as part of the cdrecord package from https://sourceforge.net/projects/cdrtools/files/
• hfsutils from ftp://ftp.mars.org/pub/hfs
• mkzftree is available as part of the zisofs-tools package from ftp://ftp.kernel.org/pub/linux/utils/fs/zisofs/

💌 MAILING LISTS 💌

If you want to actively take part on the development of mkisofs, you may join the developer mailing list via this URL:

https://lists.sourceforge.net/lists/listinfo/cdrtools-developers

👑 MAINTAINER 👑

Joerg Schilling
Seestr. 110
D-13353 Berlin
Germany

🧚 HFS MKHYBRID MAINTAINER 🧚

James Pearson

j.pearson@ge.ucl.ac.uk

If you have support questions, send them to:

cdrtools-support@lists.sourceforge.net

If you definitely found a bug, send a mail to:

cdrtools-developers@lists.sourceforge.net

or

joerg.schilling@fokus.fraunhofer.de

To subscribe, use:

https://lists.sourceforge.net/lists/listinfo/cdrtools-developers

or

https://lists.sourceforge.net/lists/listinfo/cdrtools-support

🛡️ INTERFACE STABILITY 🛡️

The interfaces provided by mkisofs are designed for long term stability. As mkisofs depends on interfaces provided by the underlying operating system, the stability of the interfaces offered by mkisofs depends on the interface stability of the OS interfaces. Modified interfaces in the OS may enforce modified interfaces in mkisofs.

---

That’s the whole MKISOFS(8) manual, bestie — Version 3.02, dated 2017/12/10. Go make something iconic 💖✨💅