mkisofs.man

刻录光盘的程序

MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



NNNNAAAAMMMMEEEE
     mkisofs - create a iso9660  filesystem  with  optional  Rock
     Ridge attributes.

SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
     mmmmkkkkiiiissssooooffffssss [ ----aaaa ] [ ----aaaabbbbssssttttrrrraaaacccctttt _F_I_L_E ] [ ----bbbbiiiibbbblllliiiioooo _F_I_L_E  ]  [   ---- bbbb
     _e_l_t_o_r_i_t_o__b_o_o_t__i_m_a_g_e  ]  [   ---- 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  ]  [   ----
     ccccooooppppyyyyrrrriiiigggghhhhtttt  _F_I_L_E ] [ ----AAAA _a_p_p_l_i_c_a_t_i_o_n__i_d ] [ ----ffff ] [ ----dddd ] [ ----DDDD ]
     [ ----hhhhiiiiddddeeee _g_l_o_b ] [ ----hhhhiiiiddddeeee----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 ] [ ----JJJJ ] [ ----llll ] [ ----LLLL ] [ ----lllloooogggg----ffffiiiilllleeee _l_o_g__f_i_l_e ] [ ---- MMMM
     _p_a_t_h  | _d_e_v_i_c_e ] [ ----nnnnoooobbbbaaaakkkk ] [ ----nnnnoooo----bbbbaaaakkkk ] [ ----nnnnoooo----sssspppplllliiiitttt----ssssyyyymmmmlllliiiinnnnkkkk----
     ccccoooommmmppppoooonnnneeeennnnttttssss ] [ ----nnnnoooo----sssspppplllliiiitttt----ssssyyyymmmmlllliiiinnnnkkkk----ffffiiiieeeellllddddssss ] [ ----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 ] [ ----ssssyyyyssssiiiidddd _I_D ] [ ----TTTT ] [ ----UUUU ] [ ----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 ]  ---- 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
     the  iso9660  filesystem  -  it  takes a snapshot of a given
     directory tree, and generates  a  binary  image  which  will
     correspond  to an iso9660 filesystem when written to a block
     device.

     mmmmkkkkiiiissssooooffffssss is also capable of generating the System Use Sharing
     Protocol  records  specified  by  the Rock Ridge Interchange
     Protocol.  This is used to further describe the files in the
     iso9660  filesystem to a unix host, and provides information
     such as longer filenames, uid/gid,  posix  permissions,  and
     block and character devices.

     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~



Version 1.12b5      Last change: 7. Jan 2000                    1






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     would be written as FOO.000;1 and the file foo.bar would  be
     written as FOO.BAR;1

     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
     specialized  tool  to  actually  burn the disk.  The ccccddddwwwwrrrriiiitttteeee
     utility is one such tool that runs under Linux and  performs
     this task.  The latest version of ccccddddwwwwrrrriiiitttteeee is capable of com-
     municating with the Phillips/IMS/Kodak, HP and Yamaha drives
     that  have been manufactured before 1997.  Most writers come
     with some version of DOS software that allows a direct image
     copy of an iso9660 image to the writer.  The current version
     of ccccddddwwwwrrrriiiitttteeee is available from  sunsite.unc.edu:  /utils/disk-
     management/cdwrite-2.0.tar.gz Note that cdwrite has not been
     actively maintained since 1995.

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

     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.

     It is possible to graft the paths at points other  than  the
     root  directory, and it is possible to graft files or direc-
     tories 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



Version 1.12b5      Last change: 7. Jan 2000                    2






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



     directories as well.  mmmmkkkkiiiissssooooffffssss wwwwiiiillllllll  ccccrrrreeeeaaaatttteeee  aaaannnnyyyy  ddddiiiirrrreeeeccccttttoooorrrriiiieeeessss
     rrrreeeeqqqquuuuiiiirrrreeeedddd ssssuuuucccchhhh tttthhhhaaaatttt tttthhhheeee ggggrrrraaaafffftttt points exist on the cdrom image
     - the directories do not need to appear in one of the paths.
     Any  directories  that are created on the fly like this will
     have permissions 0555 and appear to be owned by  the  person
     running mkisofs.  If you wish other permissions or owners of
     the intermediate directories, the  easiest  solution  is  to
     create  real  directories  in  the  path  such  that mkisofs
     doesn't have to invent them.


OOOOPPPPTTTTIIIIOOOONNNNSSSS
     ----aaaa    Include all files on the iso9660 filesystem.  Normally
          files  that  contain the characters '~' or '#' will not
          be included (these are typically backup files for  edi-
          tors  under  unix).  This  option  is now obsolete (see
          -no-bak option).

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

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

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



Version 1.12b5      Last change: 7. Jan 2000                    3






MKISOFS(8)           Maintenance Procedures            MKISOFS(8)



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

     ----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 wil be placed on  the  first  16
          sectors of the CD. The first 16 sectors are the sectors