


MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



NNNNAAAAMMMMEEEE
     mkisofs - create  an  hybrid  ISO9660/JOLIET/HFS  filesystem
     with optional Rock Ridge attributes.

SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
     mmmmkkkkiiiissssooooffffssss [ ----aaaabbbbssssttttrrrraaaacccctttt _F_I_L_E ] [ ----aaaalllllllloooowwww----lllloooowwwweeeerrrrccccaaaasssseeee ] [   ---- aaaalllllllloooowwww----
     mmmmuuuullllttttiiiiddddooootttt  ]  [ ----bbbbiiiibbbblllliiiioooo _F_I_L_E ] [ ----ccccaaaacccchhhheeee----iiiinnnnooooddddeeeessss ] [ ----nnnnoooo----ccccaaaacccchhhheeee----
     iiiinnnnooooddddeeeessss ] [ ----bbbb _e_l_t_o_r_i_t_o__b_o_o_t__i_m_a_g_e ] [ ----eeeellllttttoooorrrriiiittttoooo----aaaalllltttt----bbbbooooooootttt ] [
      ----BBBB _s_p_a_r_c__b_o_o_t__i_m_a_g_e__l_i_s_t ] [ ----GGGG _g_e_n_e_r_i_c__b_o_o_t__i_m_a_g_e ] [ ----gggguuuuiiii
     ] [ ----CCCC #,# ] [ ----hhhhaaaarrrrdddd----ddddiiiisssskkkk----bbbbooooooootttt ] [ ----nnnnoooo----eeeemmmmuuuullll----bbbbooooooootttt ] [   ---- nnnnoooo----
     bbbbooooooootttt  ] [ ----bbbbooooooootttt----llllooooaaaadddd----sssseeeegggg ] [ ----bbbbooooooootttt----llllooooaaaadddd----ssssiiiizzzzeeee ] [ ----bbbbooooooootttt----iiiinnnnffffoooo----
     ttttaaaabbbblllleeee ] [ ----cccc _b_o_o_t__c_a_t_a_l_o_g ] [ ----cccchhhheeeecccckkkk----oooollllddddnnnnaaaammmmeeeessss ] [   ---- cccchhhheeeecccckkkk----
     sssseeeessssssssiiiioooonnnn _F_I_L_E ] [ ----ccccooooppppyyyyrrrriiiigggghhhhtttt _F_I_L_E ] [ ----AAAA _a_p_p_l_i_c_a_t_i_o_n__i_d ] [ ----
     ffff ] [ ----dddd ] [ ----DDDD ] [ ----ddddiiiirrrr----mmmmooooddddeeee _m_o_d_e ] [ ----ffffiiiilllleeee----mmmmooooddddeeee _m_o_d_e ] [ ----
     ggggiiiidddd  _g_i_d ] [ ----hhhhiiiiddddeeee _g_l_o_b ] [ ----hhhhiiiiddddeeee----lllliiiisssstttt _f_i_l_e ] [ ----hhhhiiiiddddddddeeeennnn _g_l_o_b
     ] [ ----hhhhiiiiddddddddeeeennnn----lllliiiisssstttt _f_i_l_e ] [ ----hhhhiiiiddddeeee----jjjjoooolllliiiieeeetttt  _g_l_o_b  ]  [   ---- hhhhiiiiddddeeee----
     jjjjoooolllliiiieeeetttt----lllliiiisssstttt  _f_i_l_e  ]  [ ----hhhhiiiiddddeeee----jjjjoooolllliiiieeeetttt----ttttrrrraaaannnnssss----ttttbbbbllll ] [ ----hhhhiiiiddddeeee----rrrrrrrr----
     mmmmoooovvvveeeedddd ] [ ----iiiissssoooo----lllleeeevvvveeeellll _l_e_v_e_l ] [ ----iiiinnnnppppuuuutttt----cccchhhhaaaarrrrsssseeeetttt _c_h_a_r_s_e_t ] [  ----
     oooouuuuttttppppuuuutttt----cccchhhhaaaarrrrsssseeeetttt _c_h_a_r_s_e_t ] [ ----JJJJ ] [ ----jjjjcccchhhhaaaarrrrsssseeeetttt _c_h_a_r_s_e_t ] [ ----llll ]
     [ ----LLLL ] [ ----lllloooogggg----ffffiiiilllleeee _l_o_g__f_i_l_e ] [ ----mmmmaaaaxxxx----iiiissssoooo9999666666660000----ffffiiiilllleeeennnnaaaammmmeeeessss ] [ ----
     MMMM  _p_a_t_h  | _d_e_v_i_c_e ] [ ----nnnneeeewwww----ddddiiiirrrr----mmmmooooddddeeee _m_o_d_e ] [ ----nnnnoooobbbbaaaakkkk ] [ ----nnnnoooo----
     bbbbaaaakkkk ] [ ----nnnnoooo----sssspppplllliiiitttt----ssssyyyymmmmlllliiiinnnnkkkk----ccccoooommmmppppoooonnnneeeennnnttttssss ] [ ---- nnnnoooo----sssspppplllliiiitttt----ssssyyyymmmmlllliiiinnnnkkkk----
     ffffiiiieeeellllddddssss  ]  [   ---- ppppaaaadddd  ] [ ----nnnnoooo----ppppaaaadddd ] [ ----ppppaaaatttthhhh----lllliiiisssstttt _f_i_l_e ] [ ----pppp
     _p_r_e_p_a_r_e_r ] [ ----pppprrrriiiinnnntttt----ssssiiiizzzzeeee ] [ ----PPPP _p_u_b_l_i_s_h_e_r ] [ ----qqqquuuuiiiieeeetttt ] [ ---- rrrr
     ] [ ----RRRR ] [ ----rrrreeeellllaaaaxxxxeeeedddd----ffffiiiilllleeeennnnaaaammmmeeeessss ] [ ----ssssoooorrrrtttt _s_o_r_t _f_i_l_e ] [ ----ssssyyyyssssiiiidddd
     _I_D ] [ ----TTTT | ----ttttaaaabbbblllleeee----nnnnaaaammmmeeee _T_A_B_L_E__N_A_M_E ] [ ----uuuuccccssss----lllleeeevvvveeeellll _l_e_v_e_l ] [
     ----uuuuiiiidddd _u_i_d ] [ ----uuuusssseeee----ffffiiiilllleeeevvvveeeerrrrssssiiiioooonnnn ] [ ----UUUU ] [ ----nnnnoooo----iiiissssoooo----ttttrrrraaaannnnssssllllaaaatttteeee ]
     [ ----vvvv ] [ ----VVVV _v_o_l_i_d ] [ ----vvvvoooollllsssseeeetttt _I_D ] [ ----vvvvoooollllsssseeeetttt----ssssiiiizzzzeeee # ]  [   ----
     vvvvoooollllsssseeeetttt----sssseeeeqqqqnnnnoooo # ] [ ----xxxx _p_a_t_h ] [ ----eeeexxxxcccclllluuuuddddeeee----lllliiiisssstttt _f_i_l_e ] [ ----zzzz ] [
     ----mmmm _g_l_o_b ] [ ----hhhhffffssss | ----aaaapppppppplllleeee ] [ ----mmmmaaaapppp _m_a_p_p_i_n_g__f_i_l_e ] [  ---- mmmmaaaaggggiiiicccc
     _m_a_g_i_c__f_i_l_e  ]  [  ----pppprrrroooobbbbeeee ] [ ----nnnnoooo----ddddeeeesssskkkkttttoooopppp ] [ ----mmmmaaaacccc----nnnnaaaammmmeeee ] [ ----
     bbbbooooooootttt----hhhhffffssss----ffffiiiilllleeee _d_r_i_v_e_r__f_i_l_e [ ----ppppaaaarrrrtttt ] [ ----aaaauuuuttttoooo _A_u_t_o_S_t_a_r_t__f_i_l_e ]
     [   ----cccclllluuuusssstttteeeerrrr----ssssiiiizzzzeeee _s_i_z_e ] [ ----hhhhiiiiddddeeee----hhhhffffssss _g_l_o_b ] [ ----hhhhiiiiddddeeee----hhhhffffssss----lllliiiisssstttt
     _f_i_l_e ] [ ----hhhhffffssss----vvvvoooolllliiiidddd _h_f_s__v_o_l_i_d ] [ ----iiiiccccoooonnnn----ppppoooossssiiiittttiiiioooonnnn ] [ ---- rrrrooooooootttt----
     iiiinnnnffffoooo  _F_I_L_E  [ ----pppprrrreeeepppp----bbbbooooooootttt _F_I_L_E ] [ ----hhhhffffssss----ccccrrrreeeeaaaattttoooorrrr _C_R_E_A_T_O_R ] [ ----
     hhhhffffssss----ttttyyyyppppeeee _T_Y_P_E ] [ ----iiiinnnnppppuuuutttt----hhhhffffssss----cccchhhhaaaarrrrsssseeeetttt _c_h_a_r_s_e_t ] [   ---- oooouuuuttttppppuuuutttt----
     hhhhffffssss----cccchhhhaaaarrrrsssseeeetttt  _c_h_a_r_s_e_t  ]  [   ---- hhhhffffssss----uuuunnnnlllloooocccckkkk  ]  [   ----hhhhffffssss----bbbblllleeeessssssss
     _f_o_l_d_e_r__n_a_m_e ] [ --------ccccaaaapppp ] [ --------nnnneeeettttaaaattttaaaallllkkkk ] [ --------ddddoooouuuubbbblllleeee ] [ --------eeeetttthhhh----
     eeeerrrrsssshhhhaaaarrrreeee  ] [ --------uuuusssshhhhaaaarrrreeee ] [ --------eeeexxxxcccchhhhaaaannnnggggeeee ] [ --------ssssggggiiii ] [ --------xxxxiiiinnnneeeetttt ]
     [ --------mmmmaaaaccccbbbbiiiinnnn ] [ --------ssssiiiinnnngggglllleeee ] [ --------ddddaaaavvvveeee ] [ --------ssssffffmmmm ] ---- oooo  _f_i_l_e_n_a_m_e
     _p_a_t_h_s_p_e_c [_p_a_t_h_s_p_e_c]

DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
     mmmmkkkkiiiissssooooffffssss is effectively a pre-mastering program  to  generate
     an ISO9660/JOLIET/HFS hybrid filesystem.

     mmmmkkkkiiiissssooooffffssss is capable of generating the SSSSyyyysssstttteeeemmmm UUUUsssseeee SSSShhhhaaaarrrriiiinnnngggg PPPPrrrroooo----
     ttttooooccccoooollll rrrreeeeccccoooorrrrddddssss ((((SSSSUUUUSSSSPPPP)))) specified by the RRRRoooocccckkkk RRRRiiiiddddggggeeee IIIInnnntttteeeerrrrcccchhhhaaaannnnggggeeee
     PPPPrrrroooottttooooccccoooollll.... This is used to further describe the files in  the
     iso9660  filesystem to a unix host, and provides information
     such as longer filenames, uid/gid, posix  permissions,  sym-
     bolic links, block and character devices.



Version 1.14        Last change: 21 Jan 2001                    1






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     If Joliet or HFS hybrid command line options are  specified,
     mmmmkkkkiiiissssooooffffssss  will  create  additional  filesystem  meta data for
     Joliet or HFS.  The file content in this case refers to  the
     same  data  blocks  on  the  media.  It will generate a pure
     ISO9660 filesystem unless the Joliet or HFS  hybrid  command
     line options are given.

     mmmmkkkkiiiissssooooffffssss can generate a _t_r_u_e (or _s_h_a_r_e_d) HFS hybrid  filesys-
     tem. The same files are seen as HFS files when accessed from
     a Macintosh and as ISO9660 files when  accessed  from  other
     machines. HFS stands for _H_i_e_r_a_r_c_h_i_c_a_l _F_i_l_e _S_y_s_t_e_m and is the
     native file system used on Macintosh computers.

     As an alternative, mmmmkkkkiiiissssooooffffssss can generate the _A_p_p_l_e _E_n_t_e_n_s_i_o_n_s
     _t_o _I_S_O_9_6_6_0 for each file. These extensions provide each file
     with CREATOR, TYPE and certain Finder  Flags  when  accessed
     from a Macintosh. See the HHHHFFFFSSSS MMMMAAAACCCCIIIINNNNTTTTOOOOSSSSHHHH FFFFIIIILLLLEEEE FFFFOOOORRRRMMMMAAAATTTTSSSS section
     below.

     mmmmkkkkiiiissssooooffffssss takes a snapshot of a given directory tree, and gen-
     erates a binary image which will correspond to an ISO9660 or
     HFS filesystem when written to a block device.

     Each file written to the  iso9660  filesystem  must  have  a
     filename  in the 8.3 format (8 characters, period, 3 charac-
     ters, all upper case), even if Rock Ridge is in  use.   This
     filename is used on systems that are not able to make use of
     the  Rock  Ridge  extensions  (such  as  MS-DOS),  and  each
     filename  in each directory must be different from the other
     filenames in the same directory.  mmmmkkkkiiiissssooooffffssss 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 trun-
     cated names are not all unique.  mmmmkkkkiiiissssooooffffssss assigns  weightings
     to  each  filename,  and if two names that are otherwise the
     same are found the name with the lower priority  is  renamed
     to  have  a 3 digit number as an extension (where the number
     is guaranteed to be unique).  An example of  this  would  be
     the  files  foo.bar  and  foo.bar.~1~ - the file foo.bar.~1~
     would be written as FOO000.BAR;1 and the file foo.bar  would
     be written as FOO.BAR;1

     When used with various HFS options, mmmmkkkkiiiissssooooffffssss will attempt  to
     recognise  files  stored in a number of Apple/Unix file for-
     mats and will copy the data and resource forks  as  well  as
     any  relevant finder information. See the HHHHFFFFSSSS MMMMAAAACCCCIIIINNNNTTTTOOOOSSSSHHHH FFFFIIIILLLLEEEE
     FFFFOOOORRRRMMMMAAAATTTTSSSS section below for more about  formats  mmmmkkkkiiiissssooooffffssss  sup-
     ports.

     Note that mmmmkkkkiiiissssooooffffssss is not designed to  communicate  with  the
     writer directly.  Most writers have proprietary command sets
     which vary from one manufacturer to another, and you need  a



Version 1.14        Last change: 21 Jan 2001                    2






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     specialized tool to actually burn the disk.

     The ccccddddrrrreeeeccccoooorrrrdddd utility is a  utility  capable  of  burning  an
     actual  disc.   The  latest version of ccccddddrrrreeeeccccoooorrrrdddd is available
     from ftp://ftp.fokus.gmd.de/pub/unix/cdrecord

     Also you should know that most cd writers are very  particu-
     lar 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.

     ppppaaaatttthhhhssssppppeeeecccc is the path of the directory tree to be copied into
     the  iso9660  filesystem.   Multiple paths can be specified,
     and mmmmkkkkiiiissssooooffffssss will merge the files found in all of the  speci-
     fied path components to form the cdrom image.

     If the option -_g_r_a_f_t-_p_o_i_n_t_s has been specified, it is possi-
     ble  to graft the paths at points other than the root direc-
     tory, 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.  mmmmkkkkiiiissssooooffffssss 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.

     mmmmkkkkiiiissssooooffffssss will also run on Win9X/NT4  machines  when  compiled
     with        Cygnus'       cygwin       (available       from
     http://sourceware.cygnus.com/cygwin/). Therefore most refer-
     ences in this man page to _U_n_i_x can be replaced with _W_i_n_3_2.





Version 1.14        Last change: 21 Jan 2001                    3






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



OOOOPPPPTTTTIIIIOOOONNNNSSSS
     ----aaaabbbbssssttttrrrraaaacccctttt _F_I_L_E
          Specifies the abstract file name.  This  parameter  can
          also  be set in the file ....mmmmkkkkiiiissssooooffffssssrrrrcccc with ABST=filename.
          If specified in both places, the command  line  version
          is used.

     ----AAAA _a_p_p_l_i_c_a_t_i_o_n__i_d
          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.  This parameter can
          also be set in the file ....mmmmkkkkiiiissssooooffffssssrrrrcccc  with  APPI=id.   If
          specified  in  both places, the command line version is
          used.

     ----aaaalllllllloooowwww----lllloooowwwweeeerrrrccccaaaasssseeee
          This options allows lower case characters to appear  in
          iso9660 filenames.
          This violates the ISO9660 standard, but it  happens  to
          work on some systems.  Use with caution.

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

     ----bbbbiiiibbbblllliiiioooo _F_I_L_E
          Specifies the bibliographic file name.  This  parameter
          can   also   be   set   in  the  file  ....mmmmkkkkiiiissssooooffffssssrrrrcccc  with
          BIBLO=filename.  If specified in both places, the  com-
          mand line version is used.

     ----ccccaaaacccchhhheeee----iiiinnnnooooddddeeeessss
          Cache inode and device numbers to find  hard  links  to
          files.   If mmmmkkkkiiiissssooooffffssss finds a hard link (a file with mul-
          tiple names), then the file will only  appear  once  on
          the CD. This helps to save space on the CD.  The option
          ----ccccaaaacccchhhheeee----iiiinnnnooooddddeeeessss is default on UNIX  like  operating  sys-
          tems.   Be careful when using this option on a filesys-
          tem without unique inode numbers as it  may  result  in
          files containing the wrong content on CD.

     ----nnnnoooo----ccccaaaacccchhhheeee----iiiinnnnooooddddeeeessss
          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 CCCCyyyyggggwwwwiiiinnnn.  As the Microsoft
          operating  system  that  runs below CCCCyyyyggggwwwwiiiinnnn is not POSIX
          compliant, it  does  not  have  unique  inode  numbers.



Version 1.14        Last change: 21 Jan 2001                    4






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



          Cygwin creates fake inode numbers from a hash algorithm
          that is not  100%  correct.   If  mmmmkkkkiiiissssooooffffssss  would  cache
          inodes  on Cygwin, 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 sig-
          nificant amount of different  files  (>  ~5000)  is  in
          inside  the tree that is to be archived.  This does not
          happen when the  ---- nnnnoooo----ccccaaaacccchhhheeee----iiiinnnnooooddddeeeessss  iiiissss  uuuusssseeeedddd,,,,  bbbbuuuutttt  tttthhhheeee
          ddddiiiissssaaaaddddvvvvaaaannnnttttaaaaggggeeee  mmmmkkkkiiiissssooooffffssss  cannot  detect hardlinks anymore
          and the resulting CD image may be larger than expected.

     ----bbbb _e_l_t_o_r_i_t_o__b_o_o_t__i_m_a_g_e
          Specifies the path and filename of the boot image to be
          used  when making an "El Torito" bootable CD. The path-
          name must be relative to the source path  specified  to
          mmmmkkkkiiiissssooooffffssss.... This option is required to make an "El Torito"
          bootable CD.  The boot image must be exactly  the  size
          of  either  a  1.2,  1.44,  or  a  2.88 meg floppy, and
          mmmmkkkkiiiissssooooffffssss will use this size  when  creating  the  output
          iso9660  filesystem.  It  is assumed that the first 512
          byte sector should be read from the boot image  (it  is
          essentially  emulating  a  normal  floppy drive).  This
          will work, for example, if the boot  image  is  a  LILO
          based boot floppy.

     ----eeeellllttttoooorrrriiiittttoooo----aaaalllltttt----bbbbooooooootttt
          Start with a new set of "El  Torito"  boot  parameters.
          This  allows  to have more than one El Torito boot on a
          CD.  A maximum of 63 El Torito boot entries may be  put
          on a single CD.

     ----BBBB _i_m_g__s_u_n_4,_i_m_g__s_u_n_4_c,_i_m_g__s_u_n_4_m,_i_m_g__s_u_n_4_d,_i_m_g__s_u_n_4_e
          Specifies a comma separated list of  boot  images  that
          are  needed  to  make  a bootable CD for sparc systems.
          There may be empty fields in the comma separated  list.
          This  option  is required to make a bootable CD for Sun
          sparc systems.  If the ----BBBB or  ---- ssssppppaaaarrrrcccc----bbbbooooooootttt  option  has
          been specified, the first sector of the resulting image
          will contain a Sun disk label. This disk  label  speci-
          fies  slice  0  for  the  iso9660 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.



Version 1.14        Last change: 21 Jan 2001                    5






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



          If the special filename ............ is used, the actual and all
          following  boot  partitions  are mapped to the previous
          partition. If mmmmkkkkiiiissssooooffffssss is called with ----GGGG _i_m_a_g_e  ---- BBBB  ...
          all  boot  partitions  are mapped to the partition that
          contains the iso9660 filesystem image and  the  generic
          boot  image  that is located in the first 16 sectors of
          the disk is used for all architectures.

     ----GGGG _g_e_n_e_r_i_c__b_o_o_t__i_m_a_g_e
          Specifies the path and filename  of  the  generic  boot
          image  to  be  used  when making a generic bootable CD.
          The ggggeeeennnneeeerrrriiiicccc____bbbbooooooootttt____iiiimmmmaaaaggggeeee will be placed on the  first  16
          sectors of the CD. The first 16 sectors are the sectors
          that are located  before  the  iso9660  primary  volume
          descriptor.  If this option is used together with the ----
          ssssppppaaaarrrrcccc----bbbbooooooootttt option, the Sun disk label will overlay  the
          first 512 bytes of the generic boot image.

     ----hhhhaaaarrrrdddd----ddddiiiisssskkkk----bbbbooooooootttt
          Specifies that the boot image used to create  "El  Tor-
          ito"  bootable  CDs is a hard disk image. The hard disk
          image must begin with a master boot  record  that  con-
          tains a single partition.

     ----nnnnoooo----eeeemmmmuuuullll----bbbbooooooootttt
          Specifies that the boot image used to create  "El  Tor-
          ito" bootable CDs is a 'no emulation' image. The system
          will load and execute this image without performing any
          disk emulation.

     ----nnnnoooo----bbbbooooooootttt
          Specifies that the created "El  Torito"  CD  should  be
          marked as not bootable. The system will provide an emu-
          lated drive for the image, but will boot off a standard
          boot device.

     ----bbbbooooooootttt----llllooooaaaadddd----sssseeeegggg _s_e_g_m_e_n_t__a_d_d_r_e_s_s
          Specifies the load segment address of  the  boot  image
          for no-emulation "El Torito" CDs.

     ----bbbbooooooootttt----llllooooaaaadddd----ssssiiiizzzzeeee _l_o_a_d__s_e_c_t_o_r_s
          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.

     ----bbbbooooooootttt----iiiinnnnffffoooo----ttttaaaabbbblllleeee
          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



Version 1.14        Last change: 21 Jan 2001                    6






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



          the EEEELLLL TTTTOOOORRRRIIIITTTTOOOO BBBBOOOOOOOOTTTT IIIINNNNFFFFOOOO TTTTAAAABBBBLLLLEEEE section for a description
          of this table.

     ----CCCC _l_a_s_t__s_e_s_s__s_t_a_r_t,_n_e_x_t__s_e_s_s__s_t_a_r_t
          This option is needed when mmmmkkkkiiiissssooooffffssss 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 ---- CCCC
          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 ccccddddrrrreeeeccccoooorrrrdddd ----mmmmssssiiiinnnnffffoooo ............ If  the   ---- CCCC
          option  is  used  in  conjunction  with  the ----MMMM option,
          mmmmkkkkiiiissssooooffffssss will create a filesystem image that is intended
          to be a continuation of the previous session.  If the ----
          CCCC option is used without the ----MMMM  option,  mmmmkkkkiiiissssooooffffssss  will
          create  a  filesystem image that is intended to be used
          for a second session on a CDextra. This is a multi ses-
          sion  CD that holds audio data in the first session and
          a ISO9660 filesystem in the second session.

     ----cccc _b_o_o_t__c_a_t_a_l_o_g
          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  mmmmkkkkiiiissssooooffffssss.... 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 exist-
          ing  file,  as it will be excluded. Usually a name like
          "boot.catalog" is chosen.

     ----cccchhhheeeecccckkkk----oooollllddddnnnnaaaammmmeeeessss
          Check all filenames imported from old session for  com-
          pliance  with actual mmmmkkkkiiiissssooooffffssss iso9660 file naming rules.
          It his option is not present, only names with a  length
          > 31 are checked as these files are a hard violation of
          the iso9660 standard.

     ----cccchhhheeeecccckkkk----sssseeeessssssssiiiioooonnnn _F_I_L_E
          Check all  old  sessions  for  compliance  with  actual
          mmmmkkkkiiiissssooooffffssss  iso9660  file  naming  rules.   This is a high
          level option that is a combination of the options:  ---- MMMM
          _F_I_L_E  ----CCCC 0000,,,,0000 ----cccchhhheeeecccckkkk----oooollllddddnnnnaaaammmmeeeessss For the parameter _F_I_L_E see
          desciption of ----MMMM option.

     ----ccccooooppppyyyyrrrriiiigggghhhhtttt _F_I_L_E
          Specifies the Copyright file name.  This parameter  can
          also  be set in the file ....mmmmkkkkiiiissssooooffffssssrrrrcccc with COPY=filename.
          If specified in both places, the command  line  version
          is used.



Version 1.14        Last change: 21 Jan 2001                    7






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     ----dddd    Omit trailing period from files that  do  not  have  a
          period.
          This violates the ISO9660 standard, but it  happens  to
          work on many systems.  Use with caution.

     ----DDDD    Do not use deep directory relocation, and instead just
          pack them in the way we see them.
          This violates the ISO9660 standard, but it  happens  to
          work on many systems.  Use with caution.

     ----ddddiiiirrrr----mmmmooooddddeeee _m_o_d_e
          Overrides the mode of directories used  to  create  the
          image  to  _m_o_d_e.   Specifying this option automatically
          enables Rock Ridge extensions.

     ----ffff    Follow 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.

     ----ffffiiiilllleeee----mmmmooooddddeeee _m_o_d_e
          Overrides the mode of regular files used to create  the
          image  to  _m_o_d_e.   Specifying this option automatically
          enables Rock Ridge extensions.

     ----ggggiiiidddd _g_i_d
          Overrides the gid read from the  source  files  to  the
          value  of  _g_i_d.   Specifying  this option automatically
          enables Rock Ridge extensions.

     ----gggguuuuiiii  Switch the behaviour for a GUI. This  currently  makes
          the  output  more verbose but may have other effects in
          future.

     ----ggggrrrraaaafffftttt----ppppooooiiiinnnnttttssss
          Allow to use graft points for filenames. If this option
          is  used,  all  filenames are checked for graft points.
          The filename is divided at the  first  unescaped  equal
          sign.  All  occurrences of '\\' and '=' characters must
          be escaped with '\\' if -_g_r_a_f_t-_p_o_i_n_t_s has  been  speci-
          fied.

     ----hhhhiiiiddddeeee _g_l_o_b
          Hide _g_l_o_b from being seen on the ISO9660 or Rock  Ridge
          directory.   _g_l_o_b  is  a  shell wild-card-style pattern
          that must match any part of the filename or path.  Mul-
          tiple  globs  may  be hidden.  If _g_l_o_b matches a direc-
          tory, then the contents of that directory will be  hid-
          den.  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 out-
          put CD image file.  Should be used  with  the   ---- hhhhiiiiddddeeee----



Version 1.14        Last change: 21 Jan 2001                    8






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



          jjjjoooolllliiiieeeetttt option.

     ----hhhhiiiiddddeeee----lllliiiisssstttt _f_i_l_e
          A file containing a list  of  _g_l_o_b_s  to  be  hidden  as
          above.

     ----hhhhiiiiddddddddeeeennnn _g_l_o_b
          Add the hidden (existence) ISO9660 directory  attribute
          for  _g_l_o_b.  This attribute will prevent _g_l_o_b from being
          listed on DOS based systems if the /A flag is not  used
          for  the listing.  _g_l_o_b is a shell wild-card-style pat-
          tern that must match any part of the filename or  path.
          In order to match a directory name, make sure the path-
          name does not include a trailing '/' character.  Multi-
          ple globs may be hidden.

     ----hhhhiiiiddddddddeeeennnn----lllliiiisssstttt _f_i_l_e
          A file containing a list of _g_l_o_b_s  to  get  the  hidden
          attribute as above.

     ----hhhhiiiiddddeeee----jjjjoooolllliiiieeeetttt _g_l_o_b
          Hide _g_l_o_b from being  seen  on  the  Joliet  directory.
          _g_l_o_b is a shell wild-card-style pattern that must match
          any part of the filename or path.  Multiple  globs  may
          be  hidden.  If _g_l_o_b matches a directory, then the con-
          tents 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 ----hhhhiiiiddddeeee option.

     ----hhhhiiiiddddeeee----jjjjoooolllliiiieeeetttt----lllliiiisssstttt _f_i_l_e
          A file containing a list  of  _g_l_o_b_s  to  be  hidden  as
          above.

     ----hhhhiiiiddddeeee----jjjjoooolllliiiieeeetttt----ttttrrrraaaannnnssss----ttttbbbbllll
          Hide the TTTTRRRRAAAANNNNSSSS....TTTTBBBBLLLL files from the Joliet  tree.   These
          files  usually  don't make sense in the Joliet World as
          they list the real name and the ISO9660 name which  may
          both be different from the Joliet name.

     ----hhhhiiiiddddeeee----rrrrrrrr----mmmmoooovvvveeeedddd
          Rename the directory RRRRRRRR____MMMMOOOOVVVVEEEEDDDD to ....rrrrrrrr____mmmmoooovvvveeeedddd in the  Rock
          Ridge  tree.   It  seems to be impossible to completely
          hide the RRRRRRRR____MMMMOOOOVVVVEEEEDDDD directory from the Rock  Ridge  tree.
          This  option  only  makes  the  visible  tree better to
          understand for people who don't know what  this  direc-
          tory is for.  If you need to have no RRRRRRRR____MMMMOOOOVVVVEEEEDDDD directory
          at all, you should use the ----DDDD option. Note that in case
          that  the   ----DDDD option has been specified, the resulting
          filesystem is not ISO9660 level-1  compliant  and  will
          not  be readable on MS-DOS.  See also NNNNOOOOTTTTEEEESSSS section for



Version 1.14        Last change: 21 Jan 2001                    9






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



          more information on the RRRRRRRR____MMMMOOOOVVVVEEEEDDDD directory.

     ----llll    Allow  full  31  character  filenames.   Normally  the
          ISO9660 filename will be in an 8.3 format which is com-
          patible with MS-DOS, even though the  ISO9660  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 sys-
          tems (such as the Amiga).  Use with caution.

     ----iiiinnnnppppuuuutttt----cccchhhhaaaarrrrsssseeeetttt _c_h_a_r_s_e_t
          Input charset that defines the characters used in local
          file names.  To get a list of valid charset names, call
          mmmmkkkkiiiissssooooffffssss ----iiiinnnnppppuuuutttt----cccchhhhaaaarrrrsssseeeetttt hhhheeeellllpppp.... To get a 1:1 mapping,  you
          may  use  ddddeeeeffffaaaauuuulllltttt  as charset name. The default initial
          values are _c_p_4_3_7 on DOS based systems and _i_s_o_8_8_5_9-_1  on
          all  other  systems.   See CCCCHHHHAAAARRRRAAAACCCCTTTTEEEERRRR SSSSEEEETTTTSSSS section below
          for more details.

     ----oooouuuuttttppppuuuutttt----cccchhhhaaaarrrrsssseeeetttt _c_h_a_r_s_e_t
          Output charset that defines the characters that will be
          used  in  Rock  Ridge file names. Defaults to the input
          charset. See CCCCHHHHAAAARRRRAAAACCCCTTTTEEEERRRR  SSSSEEEETTTTSSSS  section  below  for  more
          details.

     ----iiiissssoooo----lllleeeevvvveeeellll _l_e_v_e_l
          Set the iso9660 conformance level.  Valid  numbers  are
          1..3.

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

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

          With level 3, no restrictions apply.

          With all iso9660 levels all filenames are restricted to
          upper case letters, numbers and the underscore (_). The
          maximum filename length is restricted to 31 characters,
          the  directory nesting level is restricted to 8 and the
          maximum path length is limited to 255 characters.

     ----JJJJ    Generate Joliet directory records in addition to regu-
          lar  iso9660 file names.  This is primarily useful when
          the discs are 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 -
          CD's 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



Version 1.14        Last change: 21 Jan 2001                   10






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



          that Joliet uses the UTF-16 coding for Unicode  charac-
          ters causes interoperability problems.

     ----jjjjcccchhhhaaaarrrrsssseeeetttt _c_h_a_r_s_e_t
          Same as using ----iiiinnnnppppuuuutttt----cccchhhhaaaarrrrsssseeeetttt _c_h_a_r_s_e_t and  ---- JJJJ  options.
          See CCCCHHHHAAAARRRRAAAACCCCTTTTEEEERRRR SSSSEEEETTTTSSSS section below for more details.

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

     ----lllloooogggg----ffffiiiilllleeee _l_o_g__f_i_l_e
          Redirect all error, warning and informational  messages
          to _l_o_g__f_i_l_e instead of the standard error.

     ----mmmm _g_l_o_b
          Exclude _g_l_o_b from being written to CDROM.   _g_l_o_b  is  a
          shell  wild-card-style  pattern that must match part of
          the filename (not the path as with option ----xxxx).  Techni-
          cally _g_l_o_b is matched against the _d->_d__n_a_m_e 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.

          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.

     ----eeeexxxxcccclllluuuuddddeeee----lllliiiisssstttt _f_i_l_e
          A file containing a list of  _g_l_o_b_s  to  be  exclude  as
          above.

     ----mmmmaaaaxxxx----iiiissssoooo9999666666660000----ffffiiiilllleeeennnnaaaammmmeeeessss
          Allow 37  chars  in  iso9660  filenames.   This  option
          forces  the  ----NNNN option as the extra name space is taken
          from the space reserved for ISO-9660 version numbers.
          This violates the ISO9660 standard, but it  happens  to
          work  on  many systems.  Although a conforming applica-
          tion 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.




Version 1.14        Last change: 21 Jan 2001                   11






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     ----MMMM _p_a_t_h
          or

     ----MMMM _d_e_v_i_c_e
          Specifies path to existing iso9660 image to be  merged.
          The  alternate  form takes a SCSI device specifier that
          uses the same syntax as the ddddeeeevvvv==== parameter of ccccddddrrrreeeeccccoooorrrrdddd....
          The  output  of  mmmmkkkkiiiissssooooffffssss  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  attempt-
          ing  to  write  this image to.  This option may only be
          used in conjunction with the ----CCCC option.

     ----NNNN    Omit version numbers from ISO9660 file names.
          This violates the ISO9660 standard, but no  one  really
          uses the version numbers anyway.  Use with caution.

     ----nnnneeeewwww----ddddiiiirrrr----mmmmooooddddeeee _m_o_d_e
          Mode to use when creating new directories in the iso fs
          image.  The default mode is 0555.

     ----nnnnoooobbbbaaaakkkk

     ----nnnnoooo----bbbbaaaakkkk
          Do not  include  backup  files  files  on  the  iso9660
          filesystem.   If the ----nnnnoooo----bbbbaaaakkkk 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).

     ----ffffoooorrrrcccceeee----rrrrrrrr
          Do not use the automatic Rock Ridge attributes recogni-
          tion  for previous sessions.  This helps to show rotten
          iso9660 extension records as e.g. created by NERO burn-
          ing ROM.

     ----nnnnoooo----rrrrrrrr
          Do not use the Rock Ridge attributes from previous ses-
          sions.   This  may  help  to avoid getting into trouble
          when mmmmkkkkiiiissssooooffffssss finds illegal Rock Ridge signatures on  an
          old session.

     ----nnnnoooo----sssspppplllliiiitttt----ssssyyyymmmmlllliiiinnnnkkkk----ccccoooommmmppppoooonnnneeeennnnttttssss
          Don't split the SL components, but  begin  a  new  Con-
          tinuation 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).

     ----nnnnoooo----sssspppplllliiiitttt----ssssyyyymmmmlllliiiinnnnkkkk----ffffiiiieeeellllddddssss
          Don't split the SL fields, but begin a new Continuation



Version 1.14        Last change: 21 Jan 2001                   12






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



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

     ----oooo _f_i_l_e_n_a_m_e
          is the name of the file to which the iso9660 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.

     ----ppppaaaadddd  Pad the end of the ISO9660 by 16  sectors  (32kB).  If
          the  total  size  then is not a multiple of 16 sectors,
          the needed number of sectors is added.  If the option ----
          BBBB is used, then there is a second padding at the end of
          the boot partitions.

          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   ---- ppppaaaadddd  option has been made the
          default.

     ----nnnnoooo----ppppaaaadddd
          Do not Pad the end of the ISO9660 by 16 sectors (32kB).

     ----ppppaaaatttthhhh----lllliiiisssstttt _f_i_l_e
          A file containing a list of  _p_a_t_h_s_p_e_c  directories  and
          filenames  to  be added to the ISO9660 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. There must be  at
          least one _p_a_t_h_s_p_e_c given on the command line as well.

     ----PPPP _p_u_b_l_i_s_h_e_r__i_d
          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.  This parameter can also be set in  the
          file  ....mmmmkkkkiiiissssooooffffssssrrrrcccc  with  PUBL=.   If  specified  in both
          places, the command line version is used.




Version 1.14        Last change: 21 Jan 2001                   13






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     ----pppp _p_r_e_p_a_r_e_r__i_d
          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.  This parameter can also be set in  the
          file  ....mmmmkkkkiiiissssooooffffssssrrrrcccc  with  PREP=.   If  specified  in both
          places, the command line version is used.

     ----pppprrrriiiinnnntttt----ssssiiiizzzzeeee
          Print estimated filesystem size and exit.  This  option
          is  needed  for  Disk  At  Once mode and with some CD-R
          drives when piping directly into ccccddddrrrreeeeccccoooorrrrdddd.... In this case
          it  is needed to know the size of the filesystem before
          the actual CD-creation is done.  The option -print-size
          allows  to get this size from a "dry-run" before the CD
          is actually written.  Old versions of mmmmkkkkiiiissssooooffffssss did write
          this  information  (among other information) to _s_t_d_e_r_r.
          As this turns out to  be  hard  to  parse,  the  number
          without  any other information is now printed on ssssttttddddoooouuuutttt
          too.  If you like  to  write  a  simple  shell  script,
          redirect ssssttttddddeeeerrrrrrrr and catch the number from ssssttttddddoooouuuutttt.  This
          may be done with:

          ccccddddbbbblllloooocccckkkkssss====```` mmmmkkkkiiiissssooooffffssss ----pppprrrriiiinnnntttt----ssssiiiizzzzeeee ----qqqquuuuiiiieeeetttt ............ ````

          mmmmkkkkiiiissssooooffffssss ............ |||| ccccddddrrrreeeeccccoooorrrrdddd ............ ttttssssiiiizzzzeeee====$$$${{{{ccccddddbbbblllloooocccckkkkssss}}}}ssss ----

     ----qqqquuuuiiiieeeetttt
          This makes mmmmkkkkiiiissssooooffffssss even less verbose.  No progress out-
          put will be provided.

     ----RRRR    Generate SUSP and RR records using the Rock Ridge pro-
          tocol  to  further  describe  the  files on the iso9660
          filesystem.

     ----rrrr    This is like the -R option,  but  file  ownership  and
          modes  are  set to more useful values.  The uid and gid
          are set to zero, because they are usually  only  useful
          on  the  author's system, and not useful to the client.
          All the file read bits are set true, so that files  and
          directories  are  globally  readable on the client.  If
          any execute bit is set for a file, set all of the  exe-
          cute  bits, so that executables are globally executable
          on the client.  If any search bit is set for  a  direc-
          tory,  set  all of the search bits, so that directories
          are globally searchable on the client.  All write  bits
          are  cleared,  because the CD-Rom will be mounted read-
          only in any case.  If any of the special mode bits  are
          set, clear them, because file locks are not useful on a
          read-only file system, and set-id bits are  not  desir-
          able  for  uid  0  or  gid  0.  When used on Win32, the



Version 1.14        Last change: 21 Jan 2001                   14






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



          execute bit is set on _a_l_l files. This is  a  result  of
          the  lack  of  file permissions on Win32 and the Cygwin
          POSIX emulation layer.  See also -uid -gid, - dir-mode,
          -file-mode and -new-dir-mode.

     ----rrrreeeellllaaaaxxxxeeeedddd----ffffiiiilllleeeennnnaaaammmmeeeessss
          The option ----rrrreeeellllaaaaxxxxeeeedddd----ffffiiiilllleeeennnnaaaammmmeeeessss allows ISO9660  filenames
          to include digits, uppercase characters and all other 7
          bit ASCII characters (resp. anything  except  lowercase
          characters).
          This violates the ISO9660 standard, but it  happens  to
          work on many systems.  Use with caution.

     ----ssssoooorrrrtttt _s_o_r_t _f_i_l_e
          Sort file locations on the media. Sorting is controlled
          by  a file that contains pairs of filenames and sorting
          offset weighting.  If the weighting is higher, the file
          will  be  located closer to the beginning of the media,
          if the weighting is lower, the  file  will  be  located
          closer  to the end of the media. 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  charac-
          ters  up  to,  but  not including the last space or tab
          character on a line. This is to allow for space charac-
          ters  to  be  in,  or  at  the  end  of a filename. See
          README.sort for more details.

     ----ssssyyyyssssiiiidddd _I_D
          Specifies the system ID.  This parameter  can  also  be
          set  in  the  file  ....mmmmkkkkiiiissssooooffffssssrrrrcccc with SYSI=system_id.  If
          specified in both places, the command line  version  is
          used.

     ----TTTT    Generate a file TRANS.TBL in  each  directory  on  the
          CDROM, which can be used on non-Rock Ridge capable sys-
          tems to help establish the correct file  names.   There
          is  also information present in the file that indicates
          the major and minor numbers  for  block  and  character
          devices, and each symlink has the name of the link file
          given.

     ----ttttaaaabbbblllleeee----nnnnaaaammmmeeee _T_A_B_L_E__N_A_M_E
          Alternative translation table file  name  (see  above).
          Implies  the   ----TTTT option.  If you are creating a multi-
          session image you must use the same name as in the pre-
          vious session.

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



Version 1.14        Last change: 21 Jan 2001                   15






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     ----uuuuiiiidddd _u_i_d
          Overrides the uid read from the  source  files  to  the
          value  of  _u_i_d.   Specifying  this option automatically
          enables Rock Ridge extensions.

     ----uuuusssseeee----ffffiiiilllleeeevvvveeeerrrrssssiiiioooonnnn
          The option ----uuuusssseeee----ffffiiiilllleeeevvvveeeerrrrssssiiiioooonnnn allows mkisofs to use  file
          version  numbers from the filesystem.  If the option is
          not specified, mmmmkkkkiiiissssooooffffssss creates a version if 1  for  all
          files.   File  versions  are strings in the range ;_1 to
          ;_3_2_7_6_7 This option is the default on VMS.

     ----UUUU    Allows "Untranslated" filenames, completely  violating
          the  iso9660 standards described above. Forces on the -
          d, -l, -L, -N, -relaxed-filenames, -allow-lowercase,  -
          allow-multidot  and  -no-iso-translate flags. It allows
          more than one '.' character in the filename, as well as
          mixed  case filenames.  This is useful on HP-UX system,
          where the built-in CDFS filesystem does  not  recognize
          ANY extensions. Use with extreme caution.

     ----nnnnoooo----iiiissssoooo----ttttrrrraaaannnnssssllllaaaatttteeee
          Do not translate the characters '#' and '~'  which  are
          invalid  for  iso9660  filenames.  These characters are
          though invalid often used by Microsoft systems.
          This violates the ISO9660 standard, but it  happens  to
          work on many systems.  Use with caution.

     ----VVVV _v_o_l_i_d
          Specifies the volume ID (volume name or  label)  to  be
          written into the master block.  This parameter can also
          be set in the file ....mmmmkkkkiiiissssooooffffssssrrrrcccc with VOLI=id.  If  speci-
          fied  in both places, the command line version is used.
          Note that if you assign a volume ID, this is  the  name
          that  will  be  used  as  the  mount  point used by the
          Solaris volume management system and the name  that  is
          assigned  to the disc on a Microsoft Win32 or Apple Mac
          platform.

     ----vvvvoooollllsssseeeetttt _I_D
          Specifies the volset ID.  This parameter  can  also  be
          set  in  the  file  ....mmmmkkkkiiiissssooooffffssssrrrrcccc with VOLS=volset_id.  If
          specified in both places, the command line  version  is
          used.

     ----vvvvoooollllsssseeeetttt----ssssiiiizzzzeeee #
          Sets the volume set size to #.  The volume set size  is
          the  number of CD's that are in a CD set.  The ----vvvvoooollllsssseeeetttt----
          ssssiiiizzzzeeee option may be used to create CD's that are part of
          e.g.  a Operation System installation set of CD's.  The
          option ----vvvvoooollllsssseeeetttt----ssssiiiizzzzeeee must be specified before  ---- vvvvoooollllsssseeeetttt----
          sssseeeeqqqqnnnnoooo on each command line.



Version 1.14        Last change: 21 Jan 2001                   16






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     ----vvvvoooollllsssseeeetttt----sssseeeeqqqqnnnnoooo #
          Sets the volume set sequence number to #.   The  volume
          set  sequence number is the index number of the current
          CD in a CD set.  The option ----vvvvoooollllsssseeeetttt----ssssiiiizzzzeeee must be speci-
          fied before ----vvvvoooollllsssseeeetttt----sssseeeeqqqqnnnnoooo on each command line.

     ----vvvv    Verbose execution. If given twice on the command line,
          extra debug information will be printed.

     ----xxxx _p_a_t_h
          Exclude _p_a_t_h from being written to CDROM.  _p_a_t_h must be
          the  complete  pathname that results from concatenating
          the pathname given as command  line  argument  and  the
          path relative to this directory.  Multiple paths may be
          excluded.  Example:

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

          NOTE: The -m and -x option description should  both  be
          updated,  they  are wrong.  Both now work identical and
          use filename globbing. A file is excluded if either the
          last component matches or the whole path matches.

      ---- zzzz    Generate  special  SUSP  records  for  transparently
          compressed files.  This is only of use and interest for
          hosts that support transparent decompression.  This  is
          an experimental feature, and no hosts yet support this,
          but there are ALPHA patches for Linux that can make use
          of this feature.


HHHHFFFFSSSS OOOOPPPPTTTTIIIIOOOONNNNSSSS
     ----hhhhffffssss  Create an ISO9660/HFS hybrid CD. This option should be
          used  in  conjunction  with  the ----mmmmaaaapppp, (Reg.)and/or the
          various _d_o_u_b_l_e _d_a_s_h options given below.

     ----aaaapppppppplllleeee
          Create an ISO9660 CD with Apple's  extensions.  Similar
          to the ----hhhhffffssss option, except that the Apple Extensions to
          ISO9660 are added instead of  creating  an  HFS  hybrid
          volume.

     ----mmmmaaaapppp _m_a_p_p_i_n_g__f_i_l_e
          Use the _m_a_p_p_i_n_g__f_i_l_e to set the CREATOR and TYPE infor-
          mation  for a file based on the filename's extension. A
          filename is mapped only if it is not one  of  the  know
          Apple/Unix  file formats. See the HHHHFFFFSSSS CCCCRRRREEEEAAAATTTTOOOORRRR////TTTTYYYYPPPPEEEE sec-
          tion below.

     ----mmmmaaaaggggiiiicccc _m_a_g_i_c__f_i_l_e
          The CREATOR and TYPE information  is  set  by  using  a
          file's  _m_a_g_i_c  _n_u_m_b_e_r (usually the first few bytes of a



Version 1.14        Last change: 21 Jan 2001                   17






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



          file). The _m_a_g_i_c__f_i_l_e 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  ---- mmmmaaaapppp  option.
          See   the  HHHHFFFFSSSS  CCCCRRRREEEEAAAATTTTOOOORRRR////TTTTYYYYPPPPEEEE  section  below  for  more
          details.

     ----hhhhffffssss----ccccrrrreeeeaaaattttoooorrrr _C_R_E_A_T_O_R
          Set the default CREATOR for all files. Must be  exactly
          4  characters.  See  the HHHHFFFFSSSS CCCCRRRREEEEAAAATTTTOOOORRRR////TTTTYYYYPPPPEEEE section below
          for more details.

     ----hhhhffffssss----ttttyyyyppppeeee _T_Y_P_E
          Set the default TYPE for all files. Must be  exactly  4
          characters.  See the HHHHFFFFSSSS CCCCRRRREEEEAAAATTTTOOOORRRR////TTTTYYYYPPPPEEEE section below for
          more details.

     ----pppprrrroooobbbbeeee
          Search  the  contents  of  files  for  all  the   known
          Apple/Unix  file  formats.   See the HHHHFFFFSSSS MMMMAAAACCCCIIIINNNNTTTTOOOOSSSSHHHH FFFFIIIILLLLEEEE
          FFFFOOOORRRRMMMMAAAATTTTSSSS section below for  more  about  these  formats.
          However,  the  only  way  to  check  for  _M_a_c_B_i_n_a_r_y and
          _A_p_p_l_e_S_i_n_g_l_e files is to open and read  them.  Therefore
          this  option _m_a_y increase processing time. It is better
          to use one or more _d_o_u_b_l_e _d_a_s_h options given  below  if
          the Apple/Unix formats in use are known.

     ----nnnnoooo----ddddeeeesssskkkkttttoooopppp
          Do not create (empty) Desktop files.  New  HFS  Desktop
          files  will  be created when the CD is used on a Macin-
          tosh (and stored in the System  Folder).   By  default,
          empty Desktop files are added to the HFS volume.

     ----mmmmaaaacccc----nnnnaaaammmmeeee
          Use the HFS filename as  the  starting  point  for  the
          ISO9660,  Joliet and Rock Ridge file names. See the HHHHFFFFSSSS
          MMMMAAAACCCCIIIINNNNTTTTOOOOSSSSHHHH FFFFIIIILLLLEEEE NNNNAAAAMMMMEEEESSSS section below  for  more  informa-
          tion.

     ----bbbbooooooootttt----hhhhffffssss----ffffiiiilllleeee _d_r_i_v_e_r__f_i_l_e
          Installs the _d_r_i_v_e_r__f_i_l_e that _m_a_y make the CD  bootable
          on  a Macintosh. See the HHHHFFFFSSSS BBBBOOOOOOOOTTTT DDDDRRRRIIIIVVVVEEEERRRR section below.
          (Alpha).

     ----ppppaaaarrrrtttt
          Generate an HFS partition table. By default, no  parti-
          tion 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.

     ----aaaauuuuttttoooo _A_u_t_o_S_t_a_r_t__f_i_l_e
          Make the HFS CD use the QuickTime 2.0 Autostart feature
          to   launch  an  application  or  document.  The  given



Version 1.14        Last change: 21 Jan 2001                   18






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



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

     ----cccclllluuuusssstttteeeerrrr----ssssiiiizzzzeeee _s_i_z_e
          Set the size in bytes  of  the  cluster  or  allocation
          units  of  PC  Exchange  files.  Implies the --------eeeexxxxcccchhhhaaaannnnggggeeee
          option. See the  HHHHFFFFSSSS  MMMMAAAACCCCIIIINNNNTTTTOOOOSSSSHHHH  FFFFIIIILLLLEEEE  FFFFOOOORRRRMMMMAAAATTTTSSSS  section
          below.

     ----hhhhiiiiddddeeee----hhhhffffssss _g_l_o_b
          Hide _g_l_o_b from the HFS volume. The  file  or  directory
          will  still  exist  in the ISO9660 and/or Joliet direc-
          tory.  _g_l_o_b 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 _g_l_o_b 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 ----hhhhiiiiddddeeee and/or ----hhhhiiiiddddeeee----jjjjoooolllliiiieeeetttt options.  In
          order to match a directory name, make sure the pathname
          does not include a trailing '/' character.

     ----hhhhiiiiddddeeee----hhhhffffssss----lllliiiisssstttt _f_i_l_e
          A file containing a list  of  _g_l_o_b_s  to  be  hidden  as
          above.

     ----hhhhffffssss----vvvvoooolllliiiidddd _h_f_s__v_o_l_i_d
          Volume name for the HFS partition.  This  is  the  name
          that  is  assigned  to  the  disc  on  a  Macintosh and
          replaces the _v_o_l_i_d used with the ----VVVV option

     ----iiiiccccoooonnnn----ppppoooossssiiiittttiiiioooonnnn
          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).



Version 1.14        Last change: 21 Jan 2001                   19






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     ----rrrrooooooootttt----iiiinnnnffffoooo _f_i_l_e
          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)

     ----pppprrrreeeepppp----bbbbooooooootttt _F_I_L_E
          PReP  boot  image  file.  Up  to  4  are  allowed.  See
          README.prep_boot (Alpha)

     ----iiiinnnnppppuuuutttt----hhhhffffssss----cccchhhhaaaarrrrsssseeeetttt _c_h_a_r_s_e_t
          Input charset that defines the characters used  in  HFS
          file  names  when  used with the -_m_a_c-_n_a_m_e option.  The
          default charset is cp10000  (Mac  Roman)  _c_p_1_0_0_0_0  (Mac
          Roman)  See CCCCHHHHAAAARRRRAAAACCCCTTTTEEEERRRR SSSSEEEETTTTSSSS and HHHHFFFFSSSS MMMMAAAACCCCIIIINNNNTTTTOOOOSSSSHHHH FFFFIIIILLLLEEEE NNNNAAAAMMMMEEEESSSS
          sections below for more details.

     ----oooouuuuttttppppuuuutttt----hhhhffffssss----cccchhhhaaaarrrrsssseeeetttt _c_h_a_r_s_e_t
          Output charset that defines the characters that will be
          used in the HFS file names. Defaults to the input char-
          set. See CCCCHHHHAAAARRRRAAAACCCCTTTTEEEERRRR SSSSEEEETTTTSSSS section below for more details.

     ----hhhhffffssss----uuuunnnnlllloooocccckkkk
          By default, mmmmkkkkiiiissssooooffffssss will create an HFS volume  that  is
          _l_o_c_k_e_d.  This option leaves the volume unlocked so that
          other applications  (e.g.   hfsutils)  can  modify  the
          volume.  See the HHHHFFFFSSSS PPPPRRRROOOOBBBBLLLLEEEEMMMMSSSS////LLLLIIIIMMMMIIIITTTTAAAATTTTIIIIOOOONNNNSSSS section below
          for warnings about using this option.

     ----hhhhffffssss----bbbblllleeeessssssss _f_o_l_d_e_r__n_a_m_e
          "Bless" the given directory (folder). This  is  usually
          the  SSSSyyyysssstttteeeemmmm FFFFoooollllddddeeeerrrr and is used in creating HFS bootable
          CDs. The name of the directory must be the  whole  path
          name  as mmmmkkkkiiiissssooooffffssss 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).

     --------ccccaaaapppp
          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 _d_o_u_b_l_e _d_a_s_h options are given.

     --------nnnneeeettttaaaattttaaaallllkkkk
          Look for NETATALK Macintosh files

     --------ddddoooouuuubbbblllleeee
          Look for AppleDouble Macintosh files

     --------eeeetttthhhheeeerrrrsssshhhhaaaarrrreeee
          Look for Helios EtherShare Macintosh files



Version 1.14        Last change: 21 Jan 2001                   20






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     --------uuuusssshhhhaaaarrrreeee
          Look for IPT UShare Macintosh files

     --------eeeexxxxcccchhhhaaaannnnggggeeee
          Look for PC Exchange Macintosh files

     --------ssssggggiiii
          Look for SGI Macintosh files

     --------xxxxiiiinnnneeeetttt
          Look for XINET Macintosh files

     --------mmmmaaaaccccbbbbiiiinnnn
          Look for MacBinary Macintosh files

     --------ssssiiiinnnngggglllleeee
          Look for AppleSingle Macintosh files

     --------ddddaaaavvvveeee
          Look for Thursby Software Systems DAVE Macintosh files

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


CCCCHHHHAAAARRRRAAAACCCCTTTTEEEERRRR SSSSEEEETTTTSSSS
     mmmmkkkkiiiissssooooffffssss processes file names in a  POSIX  compliant  way  as
     strings  of  8-bit characters.  To represent all codings for
     all languages, 8-bit characters are not sufficient.  Unicode
     or  IIIISSSSOOOO----11110000666644446666 define character codings that need at least 21
     bits  to  represent  all  known  languages.  They   may   be
     represented  with  UUUUTTTTFFFF----33332222,  UUUUTTTTFFFF----11116666  or UUUUTTTTFFFF----8888 coding.  UUUUTTTTFFFF----33332222
     uses a plain 32-bit coding but seems to be uncommon.  UUUUTTTTFFFF----11116666
     is  used  by Microsoft with Win32 with the disadvantage that
     it only supports a subset of all codes and that 16-bit char-
     acters  are  not  compliant with the POSIX filesystem inter-
     face.

     Modern  UNIX  operating  systems  use   UUUUTTTTFFFF----8888   coding   for
     filenames.  This  coding  allows to use the complete Unicode
     code set.  Each 32-bit character is represented  by  one  or
     more  8-bit  characters.   If  a  character is coded in IIIISSSSOOOO----
     8888888855559999----1111 (used in Central Europe and North  America)  is  maps
     1:1  to a Unicode character.  Character codes that cannot be
     represented as a single byte  in  UTF-8  (typically  if  the
     value  is > 0x7F) use escape sequences that map to more than
     one 8-bit character.

     If all operating systems would  use  UUUUTTTTFFFF----8888  coding,  mmmmkkkkiiiissssooooffffssss
     would  not  need to recode characters in file names.  Unfor-
     tunately, Apple  uses  completely  nonstandard  codings  and



Version 1.14        Last change: 21 Jan 2001                   21






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     Microsoft  uses a Unicode coding that is not compatible with
     the POSIX filename interface.

     For all non UUUUTTTTFFFF----8888 coded operating systems, the actual  char-
     acter that each byte represents depends on the _c_h_a_r_a_c_t_e_r _s_e_t
     or _c_o_d_e_p_a_g_e (which is the name used by  Microsoft)  used  by
     the  local  operating  system  in  use - the characters in a
     character set will reflect the region  or  natural  language
     used by the user.

     Usually character codes 0x00-0x1f  are  control  characters,
     codes  0x20-0x7f are the 7 bit ASCII characters and (on PC's
     and Mac's) 0x80-0xff are used for other characters.   Unfor-
     tunately  even  this  does  not  follow  ISO  standards that
     reserve the range 0x80-0x9f for control characters and  only
     allow 0xa0-0xff for other characters.

     As there is a lot more than 256 characters/symbols  in  use,
     only  a  small  subset  are  represented in a character set.
     Therefore the same character code may represent a  different
     character  in  different character sets. So a file name gen-
     erated, say in central Europe,  may  not  display  the  same
     character when viewed on a machine in, say eastern Europe.

     To make matters more complicated, different  operating  sys-
     tems   use  different  character  sets  for  the  region  or
     language. For example the character code for "small  e  with
     acute  accent" may be character code 0x82 on a PC, code 0x8e
     on a Macintosh and code 0xe9 on a UNIX system.   Note  while
     the  codings  used  on  a PC or Mac are nonstandard, Unicode
     codes this character as 0x00000000e9 which is basically  the
     same value as the value used by most UNIX systems.

     As long as not all operating systems and  applications  will
     use the Unicode character set as the basis for file names in
     a unique way, it may be necessary to specify which character
     set  your file names use in and which character set the file
     names should appear on the CD.

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

     -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 staring point.
          The default input character sets are _c_p_4_3_7 on DOS based
          systems and _i_s_o_8_8_5_9-_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 -_j_c_h_a_r_s_e_t option is  the  same  as



Version 1.14        Last change: 21 Jan 2001                   22






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



          using the -_i_n_p_u_t-_c_h_a_r_s_e_t and -_J options.

     -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 mmmmkkkkiiiissssooooffffssss on a Microsoft
          Win32 machine to create Rock  Ridge  CDs.  If  you  are
          using  mmmmkkkkiiiissssooooffffssss on a Unix machine, it is likely that the
          output character set will be  the  same  as  the  input
          character set.

     -input-hfs-charset
          Defines the HFS character set used for HFS  file  names
          decoded  from  any  of the various Apple/Unix file for-
          mats. Only useful when used with -_m_a_c-_n_a_m_e option.  See
          the  HHHHFFFFSSSS  MMMMAAAACCCCIIIINNNNTTTTOOOOSSSSHHHH  FFFFIIIILLLLEEEE  NNNNAAAAMMMMEEEESSSS  for more information.
          Defaults to _c_p_1_0_0_0_0 (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   - _i_n_p_u_t-_c_h_a_r_s_e_t option. Defaults to the input HFS
          character set.

     There are a number of character sets built  in  to  _m_k_i_s_o_f_s.
     To get a listing, use mmmmkkkkiiiissssooooffffssss ----iiiinnnnppppuuuutttt----cccchhhhaaaarrrrsssseeeetttt hhhheeeellllpppp....

     Additional character sets can be read from file for  any  of
     the  character set options by giving a filename as the argu-
     ment to the options. The given file will only be read if its
     name does not match one of the built in character sets.

     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 # charac-
     ter) are ignored without any  warnings.  Any  missing  input
     code is mapped to Unicode character 0x0000.

     Note that there is no support for 16 bit UNICODE (UTF-16) or
     32  bit  UNICODE  (UTF-32) coding because this coding is not
     POSIX compliant. There should be support for  UTF-8  UNICODE
     coding  which is compatible to POSIX filenames and supported



Version 1.14        Last change: 21 Jan 2001                   23






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     by moder UNIX implementations such as Solaris.

     A 1:1 character set mapping can be defined by using the key-
     word  _d_e_f_a_u_l_t  as  the  argument to any of the character set
     options. This is the behaviour of older (v1.12) versions  of
     mmmmkkkkiiiissssooooffffssss.

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

     Any character that mmmmkkkkiiiissssooooffffssss can not convert will be  replaced
     with a '_' character.

HHHHFFFFSSSS CCCCRRRREEEEAAAATTTTOOOORRRR////TTTTYYYYPPPPEEEE
     A Macintosh file has two properties associated with it which
     define  which  application created the file, the _C_R_E_A_T_O_R and
     what data the file contains, the _T_Y_P_E.  Both are (exactly) 4
     letter  strings.  Usually  this  allows  a Macintosh user to
     double-click on a file and launch  the  correct  application
     etc.  The CREATOR and TYPE of a particular file can be found
     by using something like ResEdit (or similar) on a Macintosh.

     The CREATOR and TYPE information is stored in all the  vari-
     ous  Apple/Unix encoded files.  For other files it is possi-
     ble to base the CREATOR and TYPE on the filename's extension
     using  a  _m_a_p_p_i_n_g  file  (the  ----mmmmaaaapppp option) and/or using the
     _m_a_g_i_c _n_u_m_b_e_r (usually a _s_i_g_n_a_t_u_r_e in the first few bytes) of
     a file (the ----mmmmaaaaggggiiiicccc option). If both these options are given,
     then their order on the command line is important. If the  ----
     mmmmaaaapppp  option  is given first, then a filename extension match
     is attempted before a magic number match. However, if the  ----
     mmmmaaaaggggiiiicccc  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 ....mmmmkkkkiiiissssooooffffssssrrrrcccc file or using the
     ----hhhhffffssss----ccccrrrreeeeaaaattttoooorrrr and/or ----hhhhffffssss----ttttyyyyppppeeee options, otherwise the default
     CREATOR and TYPE are 'unix' and 'TEXT'.

     The format of the _m_a_p_p_i_n_g file is the same _a_f_p_f_i_l_e format as
     used by _a_u_f_s.  This file has five columns for the _e_x_t_e_n_s_i_o_n,
     _f_i_l_e _t_r_a_n_s_l_a_t_i_o_n, _C_R_E_A_T_O_R, _T_Y_P_E and _C_o_m_m_e_n_t.  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"



Version 1.14        Last change: 21 Jan 2001                   24






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     .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 _E_X_T_N defines the Unix filename  exten-
          sion to be mapped. The default mapping for any filename
          extension that doesn't match is defined  with  the  "*"
          character.

          The _X_l_a_t_e column defines the type of  text  translation
          between  the  Unix  and Macintosh file it is ignored by
          mmmmkkkkiiiissssooooffffssss, but is kept to  be  compatible  with  aaaauuuuffffssss(1).
          Although mmmmkkkkiiiissssooooffffssss does not alter the contents of a file,
          if a binary file has it's TYPE set as 'TEXT', it _m_a_y be
          read  incorrectly  on  a  Macintosh. Therefore a better
          choice for the default TYPE may be '????'

          The _C_R_E_A_T_O_R and _T_Y_P_E keywords must be 4 characters long
          and enclosed in single quotes.

          The comment field is enclosed in double quotes - it  is
          ignored  by  mmmmkkkkiiiissssooooffffssss, but is kept to be compatible with
          aaaauuuuffffssss.

     The format of the _m_a_g_i_c file  is  almost  identical  to  the
     mmmmaaaaggggiiiicccc(4)  file  used by the Linux ffffiiiilllleeee(1) command - the rou-
     tines for reading and decoding the _m_a_g_i_c file are  based  on
     the Linux ffffiiiilllleeee(1) command.

     This file has  four  tab  separated  columns  for  the  _b_y_t_e
     _o_f_f_s_e_t, _t_y_p_e, _t_e_s_t and _m_e_s_s_a_g_e.  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     37235     LZIV ZIVU  standard unix compress
     0       string     37213     GNUz ZIVU  gzip compressed data
     0       string    %!         ASPS TEXT  Postscript
     0       string     04%!      ASPS TEXT  PC Postscript with a ^D to start
     4       string    moov       txtt MooV  QuickTime movie file (moov)
     4       string    mdat       txtt MooV  QuickTime movie file (mdat)

     The format of the file is  described  in  the  mmmmaaaaggggiiiicccc(4)  man
     page. The only difference here is that for each entry in the



Version 1.14        Last change: 21 Jan 2001                   25






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     magic file, the _m_e_s_s_a_g_e for the initial  offset  mmmmuuuusssstttt  be  4
     characters  for the CREATOR followed by 4 characters for the
     TYPE - white space is optional between them. Any other char-
     acters on this line are ignored.  Continuation lines (start-
     ing with a '>') are  also  ignored  i.e.  only  the  initial
     offset lines are used.

     Using the ----mmmmaaaaggggiiiicccc option may significantly increase  process-
     ing  time  as  each file has to opened and read to find it's
     magic number.

     In summary, for all files, the default CREATOR is 'unix' and
     the  default  TYPE is 'TEXT'.  These can be changed by using
     entries in the ._m_k_i_s_o_f_s_r_c file or by using the ---- hhhhffffssss----ccccrrrreeeeaaaattttoooorrrr
     and/or ----hhhhffffssss----ttttyyyyppppeeee options.

     If the a file is in one of the known Apple/Unix formats (and
     the format has been selected), then the CREATOR and TYPE are
     taken from the values stored in the Apple/Unix file.

     Other files can have their CREATOR and TYPE set  from  their
     file name extension (the ----mmmmaaaapppp option), or their magic number
     (the ----mmmmaaaaggggiiiicccc option). If the default match  is  used  in  the
     _m_a_p_p_i_n_g 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


HHHHFFFFSSSS MMMMAAAACCCCIIIINNNNTTTTOOOOSSSSHHHH FFFFIIIILLLLEEEE FFFFOOOORRRRMMMMAAAATTTTSSSS
     Macintosh files have two parts called the _D_a_t_a and  _R_e_s_o_u_r_c_e
     fork.  Either  may  be  empty. Unix (and many other OSs) can
     only cope with files having one part (or fork).  To  add  to
     this, Macintosh files have a number of attributes associated
     with them - probably the most important  are  the  TYPE  and
     CREATOR.  Again Unix has no concept of these types of attri-
     butes.

     e.g. a Macintosh file may be a JPEG image where the image is
     stored  in  the  Data fork and a desktop thumbnail stored in
     the Resource fork. It is usually the information in the data
     fork that is useful across platforms.

     Therefore to store a Macintosh file on a Unix filesystem,  a
     way has to be found to cope with the two forks and the extra
     attributes (which are  referred  to  as  the  _f_i_n_d_e_r  _i_n_f_o).
     Unfortunately,  it  seems  that  every software package that
     stores Macintosh files on Unix has chosen a completely  dif-
     ferent storage method.





Version 1.14        Last change: 21 Jan 2001                   26






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



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

     CAP AUFS format
          Data fork stored in a file. Resource fork in  subdirec-
          tory  .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.

     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.

     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: _m_k_i_s_o_f_s 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 ---- cccclllluuuusssstttteeeerrrr----
          ssssiiiizzzzeeee  option.   The  cluster  or allocation size can be
          found by using the DOS utility CCCCHHHHKKKKDDDDSSSSKKKK.

          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  mmmmssssddddoooossss  (not
          vvvvffffaaaatttt) when using Linux.

     SGI/XINET
          Used by SGI machines when they mount  HFS  disks.  Data
          fork  stored  in  a file. Resource fork in subdirectory



Version 1.14        Last change: 21 Jan 2001                   27






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



          .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 subdirec-
          tory resource.frk. Uses the AppleDouble format to store
          resource fork.

     Services for Macintosh
          Format of files stored by NT Servers on  NTFS  filesys-
          tems.  Data fork is stored as "filename". Resource fork
          stored as a NTFS _s_t_r_e_a_m called "filename:AFP_Resource".
          The  finder  info  is  stored  as  a NTFS _s_t_r_e_a_m called
          "filename:Afp_AfpInfo".  These  streams  are   normally
          invisible to the user.

          Warning: mkisofs only partially supports the  SFM  for-
          mat.  If  an HFS file or folder stored on the NT server
          contains an _i_l_l_e_g_a_l NT character in its name,  then  NT
          converts  these characters to _P_r_i_v_a_t_e _U_s_e _U_n_i_c_o_d_e char-
          acters. 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 direc-
          tory.

     _m_k_i_s_o_f_s will attempt to set the CREATOR, TYPE, date and pos-
     sibly  other flags from the finder info. Additionally, if it
     exists, the Macintosh filename is set from the finder  info,
     otherwise the Macintosh name is based on the Unix filename -
     see the HHHHFFFFSSSS MMMMAAAACCCCIIIINNNNTTTTOOOOSSSSHHHH FFFFIIIILLLLEEEE NNNNAAAAMMMMEEEESSSS section below.

     When using the ----aaaapppppppplllleeee  option,  the  TYPE  and  CREATOR  are
     stored  in  the  optional  System  Use  or SUSP field in the
     ISO9660 Directory Record - in much the same way as the  Rock
     Ridge  attributes  are. In fact to make life easy, the Apple
     extensions are added at the beginning of the  existing  Rock
     Ridge  attributes  (i.e. to get the Apple extensions you get
     the Rock Ridge extensions as well).

     The Apple extensions require the resource fork to be  stored
     as  an ISO9660 _a_s_s_o_c_i_a_t_e_d file. This is just like any normal
     file stored in the ISO9660 filesystem except that the  asso-
     ciated  file  flag  is  set in the Directory Record (bit 2).
     This file has the same name as the data fork (the file  seen



Version 1.14        Last change: 21 Jan 2001                   28






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     by   non-Apple  machines).  Associated  files  are  normally
     ignored by other OSs

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

     In most cases, it is better to use the ----hhhhffffssss  option  instead
     of  the   ---- aaaapppppppplllleeee  option, as the latter imposes the limited
     ISO9660 characters allowed in filenames. However, the  Apple
     extensions  do  give the advantage that the files are packed
     on the disk more efficiently and it may be possible  to  fit
     more  files  on  a CD - important when the total size of the
     source files is approaching 650MB.


HHHHFFFFSSSS MMMMAAAACCCCIIIINNNNTTTTOOOOSSSSHHHH FFFFIIIILLLLEEEE NNNNAAAAMMMMEEEESSSS
     Where possible, the HFS filename  that  is  stored  with  an
     Apple/Unix file is used for the HFS part of the CD. However,
     not all the Apple/Unix encodings store the HFS filename with
     the  finderinfo. In these cases, the Unix filename is used -
     with escaped special characters. Special characters  include
     '/' and characters with codes over 127.

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

     If mkisofs can't find an HFS filename, then it uses the Unix
     name,  with any %xx or :xx characters (xx == two hex digits)
     converted to a single character code. If "xx"  are  not  hex
     digits  ([0-9a-fA-F]),  then  they are left alone - although
     any remaining ":" is converted to "%" as colon  is  the  HFS
     directory separator. Care must be taken, as an ordinary Unix
     file with %xx or :xx will also be converted. e.g.

     This:2fFile   converted to This/File

     This:File     converted to This%File

     This:t7File   converted to This%t7File

     Although HFS filenames appear to  support  upper  and  lower
     case  letters,  the filesystem is case insensitive. i.e. the
     filenames "aBc" and "AbC" are the same. If a file  is  found
     in  a  directory  with  the same HFS name, then _m_k_i_s_o_f_s will
     attempt, where possible, to make a unique name by adding '_'
     characters to one of the filenames.

     If an HFS filename exists for a file, then mkisofs  can  use
     this  name as the starting point for the ISO9660, Joliet and



Version 1.14        Last change: 21 Jan 2001                   29






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     Rock Ridge filenames using the ----mmmmaaaacccc----nnnnaaaammmmeeee option. Normal Unix
     files  without  an  HFS name will still use their Unix name.
     e.g.

     If  a  _M_a_c_B_i_n_a_r_y  (or  _P_C  _E_x_c_h_a_n_g_e)  file  is   stored   as
     _s_o_m_e_i_m_a_g_e._g_i_f._b_i_n on the Unix filesystem, but contains a HFS
     file called _s_o_m_e_i_m_a_g_e._g_i_f, then this is the name that  would
     appear  on  the HFS part of the CD. However, as mkisofs uses
     the Unix name as the starting point  for  the  other  names,
     then   the   ISO9660   name   generated   will  probably  be
     _S_O_M_E_I_M_A_G._B_I_N   and   the   Joliet/Rock   Ridge   would    be
     _s_o_m_e_i_m_a_g_e._g_i_f._b_i_n.   Although the actual data (in this case)
     is a GIF image. This option will use the HFS filename as the
     starting  point  and  the  ISO9660  name  will  probably  be
     _S_O_M_E_I_M_A_G._G_I_F   and   the   Joliet/Rock   Ridge   would    be
     _s_o_m_e_i_m_a_g_e._g_i_f.

     Using the ----mmmmaaaacccc----nnnnaaaammmmeeee option will not currently work with the
     ---- TTTT  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 _c_p_1_0_0_0_0 (Mac Roman).
     The character set used can be specified  using  the  -_i_n_p_u_t-
     _h_f_s-_c_h_a_r_s_e_t  option.  Other built in HFS character sets are:
     cp10006 (MacGreek), cp10007 (MacCyrillic),  cp10029  (MacLa-
     tin2), cp10079 (MacIcelandandic) and cp10081 (MacTurkish).

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

     The existing mkisofs code will filter out any illegal  char-
     acters  for the ISO9660 and Joliet filenames, but as mkisofs
     expects to be dealing directly with Unix  names,  it  leaves
     the  Rock  Ridge  names  as  is.   But as '/' is a legal HFS
     filename character, the ----mmmmaaaacccc----nnnnaaaammmmeeee option converts '/'  to  a
     '_' in Rock Ridge filenames.

     If the Apple extensions are  used,  then  only  the  ISO9660
     filenames  will  appear  on  the  Macintosh. However, as the
     Macintosh ISO9660 drivers can use _L_e_v_e_l  _2  filenames,  then
     you can use options like ----aaaalllllllloooowwww----mmmmuuuullllttttiiiiddddooootttt without problems on
     a Macintosh - still take care over the  names,  for  example
     _t_h_i_s._f_i_l_e._n_a_m_e will be converted to _T_H_I_S._F_I_L_E i.e. only have
     one '.', also filename _a_b_c_d_e_f_g_h will be seen as _A_B_C_D_E_F_G_H but
     _a_b_c_d_e_f_g_h_i  will be seen as _A_B_C_D_E_F_G_H_I. i.e. with a '.' at the
     end  -  don't  know  if  this  is  a  Macintosh  problem  or
     mkisofs/mkhybrid problem. All filenames will be in uppercase
     when viewed on a Macintosh. Of course,  DOS/Win3.X  machines



Version 1.14        Last change: 21 Jan 2001                   30






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     will not be able to see Level 2 filenames...


HHHHFFFFSSSS CCCCUUUUSSSSTTTTOOOOMMMM VVVVOOOOLLLLUUUUMMMMEEEE////FFFFOOOOLLLLDDDDEEEERRRR IIIICCCCOOOONNNNSSSS
     To give a HFS CD a custom icon,  make  sure  the  root  (top
     level)  folder  includes  a  standard  Macintosh volume icon
     file. To give a volume a custom icon on a Macintosh, an icon
     has  to  be  pasted over the volume's icon in the "Get Info"
     box of the volume. This creates  an  invisible  file  called
     'Icon\r'  ('\r'  is  the 'carriage return' character) in the
     root folder.

     A custom folder icon is very similar  -  an  invisible  file
     called 'Icon\r' exits in the folder itself.

     Probably the easiest  way  to  create  a  custom  icon  that
     mkisofs  can  use, is to format a blank HFS floppy disk on a
     Mac, paste an icon to its "Get Info"  box.  If  using  Linux
     with  the HFS module installed, mount the floppy using some-
     thing 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 are not using Linux, then you can use the hfsutils to
     copy  the icon file from the floppy. However, care has to be
     taken, as the icon file contains a control character. e.g.

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

     Where '^V^M' is control-V followed by  control-M.  Then  run
     mmmmkkkkiiiissssooooffffssss 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  direc-
     tory in the mkisofs source tree.

     You may want to hide the icon files  from  the  ISO9660  and
     Joliet trees.

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



Version 1.14        Last change: 21 Jan 2001                   31






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



HHHHFFFFSSSS BBBBOOOOOOOOTTTT DDDDRRRRIIIIVVVVEEEERRRR
     It _m_a_y be possible to make  the  hybrid  CD  bootable  on  a
     Macintosh.

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

     A driver can be obtained from any other  Macintosh  bootable
     CD-ROM using the _a_p_p_l_e__d_r_i_v_e_r utility. This file can then be
     used with the ----bbbbooooooootttt----hhhhffffssss----ffffiiiilllleeee option.

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

     For a partition to be bootable, it must have it's _b_o_o_t _b_l_o_c_k
     set.  The  boot block is in the first two blocks of a parti-
     tion. For a non-bootable partition the boot block is full of
     zeros.  Normally,  when a System file is copied to partition
     on a Macintosh disk, the boot block is filled with a  number
     of  required  settings - unfortunately I don't know the full
     spec for the boot block, so I'm guessing that the  following
     will work OK.

     Therefore, the utility _a_p_p_l_e__d_r_i_v_e_r 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
     mmmmkkkkiiiissssooooffffssss.

     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.

EEEELLLL TTTTOOOORRRRIIIITTTTOOOO BBBBOOOOOOOOTTTT IIIINNNNFFFFOOOORRRRMMMMAAAATTTTIIIIOOOONNNN TTTTAAAABBBBLLLLEEEE
     When the ----bbbbooooooootttt----iiiinnnnffffoooo----ttttaaaabbbblllleeee  option  is  given,  mmmmkkkkiiiissssooooffffssss  will
     modify the boot file specified by the ----bbbb 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 reli-
     ably obtained at boot time.

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

       Offset    Name           Size      Meaning
        8        bi_pvd         4 bytes   LBA of primary volume descriptor
       12        bi_file        4 bytes   LBA of boot file
       16        bi_length      4 bytes   Boot file length in bytes
       20        bi_csum        4 bytes   32-bit checksum



Version 1.14        Last change: 21 Jan 2001                   32






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



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

CCCCOOOONNNNFFFFIIIIGGGGUUUURRRRAAAATTTTIIIIOOOONNNN
     mmmmkkkkiiiissssooooffffssss looks for the ....mmmmkkkkiiiissssooooffffssssrrrrcccc file, first in the  current
     working  directory,  then  in the user's home directory, and
     then in the directory in which the mmmmkkkkiiiissssooooffffssss binary is stored.
     This  file  is  assumed  to contain a series of lines of the
     form TTTTAAAAGGGG====_v_a_l_u_e, and in this  way  you  can  specify  certain
     options.   The  case  of  the  tag is not significant.  Some
     fields in the volume header are not settable on the  command
     line,  but  can  be altered through this facility.  Comments
     may be placed in this file, using lines which start  with  a
     hash (#) character.

     AAAAPPPPPPPPIIII The application identifier should describe the applica-
          tion  that  will be on the disc.  There is space on the
          disc for 128 characters of information.  May  be  over-
          ridden using the ----AAAA command line option.

     CCCCOOOOPPPPYYYY The copyright information, often the name of a file  on
          the  disc  containing  the  copyright notice.  There is
          space in the disc for  37  characters  of  information.
          May  be  overridden  using  the ----ccccooooppppyyyyrrrriiiigggghhhhtttt command line
          option.

     AAAABBBBSSSSTTTT The abstract information, often the name of a  file  on
          the disc containing an abstract.  There is space in the
          disc for 37 characters of information.  May be overrid-
          den using the ----aaaabbbbssssttttrrrraaaacccctttt command line option.

     BBBBIIIIBBBBLLLL The bibliographic information, often the name of a file
          on  the disc containing a bibliography.  There is space
          in the disc for 37 characters of information.   May  be
          overridden using the ----bbbbiiiilllliiiioooo command line option.

     PPPPRRRREEEEPPPP 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.
          May be overridden using the ----pppp command line option.

     PPPPUUUUBBBBLLLL This should describe the publisher of the  CDROM,  usu-
          ally with a mailing address and phone number.  There is
          space on the disc for 128  characters  of  information.
          May be overridden using the ----PPPP command line option.

     SSSSYYYYSSSSIIII The System Identifier.  There is space on the disc  for
          32  characters of information.  May be overridden using



Version 1.14        Last change: 21 Jan 2001                   33






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



          the ----ssssyyyyssssiiiidddd command line option.

     VVVVOOOOLLLLIIII The Volume Identifier.  There is space on the disc  for
          32  characters of information.  May be overridden using
          the ----VVVV command line option.

     VVVVOOOOLLLLSSSS The Volume Set Name.  There is space on  the  disc  for
          128 characters of information.  May be overridden using
          the ----vvvvoooollllsssseeeetttt command line option.

     HHHHFFFFSSSS____TTTTYYYYPPPPEEEE
          The default TYPE for Macintosh files. Must be exactly 4
          characters.  May be overridden using the ----hhhhffffssss----ttttyyyyppppeeee com-
          mand line option.

     HHHHFFFFSSSS____CCCCRRRREEEEAAAATTTTOOOORRRR
          The  default  CREATOR  for  Macintosh  files.  Must  be
          exactly  4  characters.   May be overridden using the ----
          hhhhffffssss----ccccrrrreeeeaaaattttoooorrrr command line option.

     mmmmkkkkiiiissssooooffffssss can also be configured at compile time with defaults
     for many of these fields.  See the file defaults.h.


EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS
     To create a vanilla ISO-9660 filesystem image  in  the  file
     _c_d._i_s_o,  where  the  directory  _c_d__d_i_r  will become the root
     directory if the CD, call:

     % mkisofs -o cd.iso cd_dir

     To create a CD with Rock  Ridge  extensions  of  the  source
     directory _c_d__d_i_r:

     % mkisofs -o cd.iso -R cd_dir

     To create a CD with Rock  Ridge  extensions  of  the  source
     directory  _c_d__d_i_r where all files have at least read permis-
     sion and all files are owned by _r_o_o_t, call:

     % mkisofs -o cd.iso -r cd_dir

     To create a HFS hybrid CD with the  Joliet  and  Rock  Ridge
     extensions of the source directory _c_d__d_i_r:

     % mkisofs -o cd.iso -R -J -hfs cd_dir

     To create a HFS hybrid CD from the source  directory  _c_d__d_i_r
     that contains Netatalk Apple/Unix files:

     % mkisofs -o cd.iso --netatalk cd_dir




Version 1.14        Last change: 21 Jan 2001                   34






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



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

     % mkisofs -o cd.iso -map mapping cd_dir

     To create a CD with the 'Apple Extensions to ISO9660',  from
     the source directories _c_d__d_i_r and _a_n_o_t_h_e_r__d_i_r.  Files in all
     the known Apple/Unix format are decoded and any other  files
     are given CREATOR and TYPE based on their magic number given
     in the file "magic":

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

     The following example puts different files on  the  CD  that
     all  have  the name README, but have different contents when
     seen as a ISO9660/RockRidge, Joliet or HFS CD.

     Current directory contains:

     % ls -F
     README.hfs     README.joliet  README.unix    cd_dir/

     The following command puts the  contents  of  the  directory
     _c_d__d_i_r  on  the  CD  along with the three README files - but
     only one will be seen from each of the three filesystems:

     % mkisofs -o cd.iso -hfs -J -r -graft-points \
             -hide README.hfs -hide README.joliet \
             -hide-joliet README.hfs -hide-joliet README.unix \
             -hide-hfs README.joliet -hide-hfs README.unix \
             README=README.hfs README=README.joliet \
             README=README.unix cd_dir

     i.e. the file README.hfs will be seen as README on  the  HFS
     CD  and the other two README files will be hidden. Similarly
     for the Joliet and ISO9660/RockRidge CD.

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


AAAAUUUUTTTTHHHHOOOORRRR
     mmmmkkkkiiiissssooooffffssss is not based on the standard mk*fs tools  for  unix,
     because  we  must  generate  a complete  copy of an existing
     filesystem on a disk in the  iso9660 filesystem.   The  name
     mkisofs  is  probably a bit of a misnomer, since it not only
     creates the filesystem, but it also populates  it  as  well.
     However,  the  appropriate  tool  name  for a UNIX tool that
     creates populated filesystems - mkproto - is not well known.




Version 1.14        Last change: 21 Jan 2001                   35






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     Eric Youngdale <ericy@gnu.ai.mit.edu> or  <eric@andante.org>
     wrote  the  first  versions  (1993  ... 1998) of the mkisofs
     utility.  The copyright for  old  versions  of  the  mkisofs
     utility is held by Yggdrasil Computing, Incorporated.  Joerg
     Schilling wrote the SCSI transport library and it's  adapta-
     tion  layer  to mmmmkkkkiiiissssooooffffssss and newer parts (starting from 1999)
     of the utility, this makes mmmmkkkkiiiissssooooffffssss Copyright (C) 1999, 2000,
     2001 Joerg Schilling.

     HFS hybrid code Copyright  (C)  James  Pearson  1997,  1998,
     1999, 2000, 2001
     libhfs code Copyright (C) 1996, 1997 Robert Leslie
     libfile code Copyright (C) Ian F. Darwin 1986,  1987,  1989,
     1990, 1991, 1992, 1994, 1995.

NNNNOOOOTTTTEEEESSSS
     MMMMkkkkiiiissssooooffffssss may safely be  installed  suid  root.  This  may  be
     needed  to  allow  mmmmkkkkiiiissssooooffffssss to read the previous session when
     creating a multi session image.

     If mmmmkkkkiiiissssooooffffssss 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,  mmmmkkkkiiiissssooooffffssss  will  do
     deep  directory  relocation.   This  results  in a directory
     called RRRRRRRR____MMMMOOOOVVVVEEEEDDDD in the root directory of the CD. You  cannot
     avoid this directory.

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

     +o     Does not check for SUSP record(s) in "." entry of  the
          root  directory  to  verify the existence of Rock Ridge
          enhancements.

          This problem is present when reading old sessions while
          adding data in multi-session mode.

      +o     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.

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




Version 1.14        Last change: 21 Jan 2001                   36






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     +o     Does not  create  whole_name  entry  for  RR_MOVED  in
          multi-session mode.

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


HHHHFFFFSSSS PPPPRRRROOOOBBBBLLLLEEEEMMMMSSSS////LLLLIIIIMMMMIIIITTTTAAAATTTTIIIIOOOONNNNSSSS
     I have had to make several assumptions on how I  expect  the
     modified  libhfs  routines  to  work,  however  there may be
     situations that either I haven't thought of, or come  across
     when  these  assumptions  fail.  Therefore I can't guarantee
     that mkisofs will work as expected (although I haven't had a
     major problem yet). Most of the HFS features work fine, how-
     ever, some are not fully tested. These are marked  as  _A_l_p_h_a
     above.

     Although HFS filenames appear to  support  upper  and  lower
     case  letters,  the filesystem is case insensitive. i.e. the
     filenames "aBc" and "AbC" are the same. If a file  is  found
     in  a  directory  with  the same HFS name, then _m_k_i_s_o_f_s will
     attempt, where possible, to make a unique name by adding '_'
     characters to one of the filenames.

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

     Care must be  taken  when  "grafting"  Apple/Unix  files  or
     directories  (see above for the method and syntax involved).
     It is not possible to use  a  new  name  for  an  Apple/Unix
     encoded  file/directory.  e.g.  If a Apple/Unix encoded file
     called "oldname" is to added to the CD, then you can not use
     the command line:

          mkisofs   -  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, ----
     MMMM  and ----CCCC, only files in the last session will be in the HFS
     volume. i.e. mkisofs can not _a_d_d existing files from  previ-
     ous sessions to the HFS volume.

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

     Hybrid volumes may be larger than pure ISO9660 volumes  con-
     taining the same data.



Version 1.14        Last change: 21 Jan 2001                   37






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     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 lllloooocccckkkkeeeedddd.... The option
      ---- hhhhffffssss----uuuunnnnlllloooocccckkkk will create an output image that is unlocked -
     however no changes should be made to  the  contents  of  the
     volume  (unless  you really know what you are doing) as it's
     not a "real" HFS volume.

     Using the ----mmmmaaaacccc----nnnnaaaammmmeeee option will not currently work with the
     ---- TTTT  option  -  the  Unix name will be used in the TRANS.TBL
     file, not the Macintosh name.

     Although mmmmkkkkiiiissssooooffffssss does not alter the contents of a file, if a
     binary  file  has  it's  TYPE  set as 'TEXT', it _m_a_y be read
     incorrectly on a Macintosh. Therefore a  better  choice  for
     the default TYPE may be '????'

     The ----mmmmaaaacccc----bbbbooooooootttt----ffffiiiilllleeee option may not work at all...

     May not work with PC Exchange v2.2 or higher  files  (avail-
     able  with  MacOS  8.1).   DOS  media containing PC Exchange
     files should be mounted as type mmmmssssddddoooossss (not vvvvffffaaaatttt) when  using
     Linux.

     The SFM format is only partially supported - see HHHHFFFFSSSS  MMMMAAAACCCCIIIINNNN----
     TTTTOOOOSSSSHHHH FFFFIIIILLLLEEEE FFFFOOOORRRRMMMMAAAATTTTSSSS section above.

     It is not possible to use the the ----ssssppppaaaarrrrcccc----bbbbooooooootttt or  ---- ggggeeeennnneeeerrrriiiicccc----
     bbbbooooooootttt options with the ----bbbbooooooootttt----hhhhffffssss----ffffiiiilllleeee or ----pppprrrreeeepppp----bbbbooooooootttt options.


SSSSEEEEEEEE AAAALLLLSSSSOOOO
     ccccddddrrrreeeeccccoooorrrrdddd((((1111)))) mmmmaaaaggggiiiicccc(5), aaaapppppppplllleeee____ddddrrrriiiivvvveeeerrrr(8)


FFFFUUUUTTTTUUUURRRREEEE IIIIMMMMPPPPRRRROOOOVVVVEEEEMMMMEEEENNNNTTTTSSSS
     Some sort of gui interface.

AAAAVVVVAAAAIIIILLLLAAAABBBBIIIILLLLIIIITTTTYYYY
     mmmmkkkkiiiissssooooffffssss is available as part of the  cdrecord  package  from
     ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/    hhhhffffssssuuuuttttiiiillllssss   from
     ftp://ftp.mars.org/pub/hfs

MMMMAAAAIIIILLLLIIIINNNNGGGG LLLLIIIISSSSTTTTSSSS
     If you want to actively take  part  on  the  development  of
     mkisofs, and/or mkhybrid, you may join the cdwriting mailing
     list by sending mail to:

               other-cdwrite-request@lists.debian.org

     and include the  word  _s_u_b_s_c_r_i_b_e  in  the  body.   The  mail
     address of the list is:



Version 1.14        Last change: 21 Jan 2001                   38






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



               cdwrite@lists.debian.org


MMMMAAAAIIIINNNNTTTTAAAAIIIINNNNEEEERRRR
     Joerg Schilling
     Seestr. 110
     D-13353 Berlin
     Germany

HHHHFFFFSSSS MMMMKKKKHHHHYYYYBBBBRRRRIIIIDDDD MMMMAAAAIIIINNNNTTTTAAAAIIIINNNNEEEERRRR
     James Pearson

     j.pearson@ge.ucl.ac.uk


     If you have support questions, send them to:

     ccccddddrrrreeeeccccoooorrrrdddd----ssssuuuuppppppppoooorrrrtttt@@@@bbbbeeeerrrrlllliiiioooossss....ddddeeee
     or ooootttthhhheeeerrrr----ccccddddwwwwrrrriiiitttteeee@@@@lllliiiissssttttssss....ddddeeeebbbbiiiiaaaannnn....oooorrrrgggg

     Of you definitly found a bug, send a mail to:

     ccccddddrrrreeeeccccoooorrrrdddd----ddddeeeevvvveeeellllooooppppeeeerrrrssss@@@@bbbbeeeerrrrlllliiiioooossss....ddddeeee
     or sssscccchhhhiiiilllllllliiiinnnngggg@@@@ffffooookkkkuuuussss....ggggmmmmdddd....ddddeeee

     To subscribe, use:

     hhhhttttttttpppp::::////////lllliiiissssttttssss....bbbbeeeerrrrlllliiiioooossss....ddddeeee////mmmmaaaaiiiillllmmmmaaaannnn////lllliiiissssttttiiiinnnnffffoooo////ccccddddrrrreeeeccccoooorrrrdddd----ddddeeeevvvveeeellllooooppppeeeerrrrssss
     or hhhhttttttttpppp::::////////lllliiiissssttttssss....bbbbeeeerrrrlllliiiioooossss....ddddeeee////mmmmaaaaiiiillllmmmmaaaannnn////lllliiiissssttttiiiinnnnffffoooo////ccccddddrrrreeeeccccoooorrrrdddd----ssssuuuuppppppppoooorrrrtttt


























Version 1.14        Last change: 21 Jan 2001                   39



