mk9660 3.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232
  1. .TH MK9660 8
  2. .SH NAME
  3. dump9660, mk9660 \- create an ISO-9660 CD image
  4. .SH SYNOPSIS
  5. .B disk/mk9660
  6. [
  7. .B -:D
  8. ]
  9. [
  10. .B -9cjr
  11. ]
  12. [
  13. .B -b
  14. .I bootfile
  15. ]
  16. [
  17. .B -p
  18. .I proto
  19. ]
  20. [
  21. .B -s
  22. src
  23. ]
  24. [
  25. .B -v
  26. volume
  27. ]
  28. .I image
  29. .PP
  30. .B disk/dump9660
  31. [
  32. .B -:D
  33. ]
  34. [
  35. .B -9cjr
  36. ]
  37. [
  38. .B -p
  39. .I proto
  40. ]
  41. [
  42. .B -s
  43. src
  44. ]
  45. [
  46. .B -v
  47. volume
  48. ]
  49. [
  50. .B -m
  51. .I maxsize
  52. ]
  53. [
  54. .B -n
  55. .I now
  56. ]
  57. .I image
  58. .SH DESCRIPTION
  59. .I Mk9660
  60. writes to the random access file
  61. .I image
  62. an ISO-9660 CD image containing the
  63. files named in
  64. .I proto
  65. (by default,
  66. .BR /sys/lib/sysconfig/proto/allproto )
  67. from the file tree
  68. .I src
  69. (by default,
  70. the current directory).
  71. The
  72. .I proto
  73. file is formatted as described in
  74. .IR mkfs (8).
  75. .PP
  76. The created CD image will be in ISO-9660
  77. format, but by default the file names will
  78. be stored in UTF-8 with no imposed length
  79. or character restrictions.
  80. The
  81. .B -c
  82. flag causes
  83. .I mk9660
  84. to use only file names in ``8.3'' form
  85. that use digits, letters, and underscore.
  86. File names that do not conform are changed
  87. to
  88. .BI D nnnnnn
  89. (for directories)
  90. or
  91. .BI F nnnnnn
  92. (for files);
  93. a key file
  94. .B _CONFORM.MAP
  95. is created in the root
  96. directory to ease the reverse process.
  97. .PP
  98. If the
  99. .B -9
  100. flag is given, the system use fields at the end of
  101. each directory entry will be populated with
  102. Plan directory information (owner, group, mode,
  103. full name); this is interpreted by
  104. .IR 9660srv .
  105. .PP
  106. If the
  107. .B -j
  108. flag is given, the usual directory tree is written,
  109. but an additional tree in Microsoft Joliet format is
  110. also added.
  111. This second tree can contain long Unicode file names,
  112. and can be read by
  113. .I 9660srv
  114. as well as most versions of Windows
  115. and many Unix clones.
  116. The characters
  117. .BR * ,
  118. .BR : ,
  119. .BR ; ,
  120. .BR ? ,
  121. and
  122. .B \e
  123. are allowed in Plan 9 file names but not in Joliet file names;
  124. non-conforming file names are translated
  125. and a
  126. .B _CONFORM.MAP
  127. file written
  128. as in the case of the
  129. .B -c
  130. option.
  131. .PP
  132. If the
  133. .B -r
  134. flag is given, Rock Ridge extensions are written in the
  135. format of the system use sharing protocol;
  136. this format provides Posix-style file metadata and is
  137. common on Unix platforms.
  138. .PP
  139. The options
  140. .BR -c ,
  141. .BR -9 ,
  142. .BR -j ,
  143. and
  144. .B -r
  145. may be mixed freely with the exception that
  146. .B -9
  147. and
  148. .B -r
  149. are mutually exclusive.
  150. .PP
  151. The
  152. .B -v
  153. flag sets the volume title;
  154. if unspecified, the base name of
  155. .I proto
  156. is used.
  157. .PP
  158. The
  159. .B -:
  160. flag causes
  161. .B mk9660
  162. to replace colons in scanned file names with spaces;
  163. this is the inverse of the map applied by
  164. .IR dossrv (4)
  165. and is useful for writing Joliet CDs containing data
  166. from FAT file systems.
  167. .PP
  168. The
  169. .B -b
  170. option creates a bootable CD.
  171. Bootable CDs contain pointers to floppy images which are
  172. loaded and booted by the BIOS.
  173. .I Bootfile
  174. should be the name of the floppy image to use;
  175. it is a path relative to the root of the created CD.
  176. That is, the boot floppy image must be listed in the
  177. .I proto
  178. file already:
  179. the
  180. .B -b
  181. flag just creates a pointer to it.
  182. .PP
  183. The
  184. .B -D
  185. flag creates immense amounts of debugging output
  186. on standard error.
  187. .PP
  188. .I Dump9660
  189. is similar in specification to
  190. .I mk9660
  191. but creates and updates backup CD images in the style of
  192. the
  193. .I dump
  194. file system
  195. (see
  196. .IR fs (4)).
  197. The dump is file-based rather than block-based:
  198. if a file's contents have not changed since the last
  199. backup, only its directory entry will be rewritten.
  200. .PP
  201. The
  202. .B -n
  203. option specifies a time (in seconds since January 1, 1970)
  204. to be used for naming the dump directory.
  205. .PP
  206. The
  207. .B -m
  208. option specifies a maximum size for the image;
  209. if a backup would cause the image to grow larger than
  210. .IR maxsize ,
  211. it will not be written, and
  212. .I dump9660
  213. will exit with a non-empty status.
  214. .SH EXAMPLE
  215. .PP
  216. Create an image of the Plan 9 source tree,
  217. including a conformant ISO-9660 directory tree,
  218. Plan 9 extensions in the system use fields, and
  219. a Joliet directory tree.
  220. .IP
  221. .EX
  222. disk/mk9660 -9cj -s /n/bootes \e
  223. -p /sys/lib/sysconfig/srcproto cdimage
  224. .EE
  225. .SH SOURCE
  226. .B /sys/src/cmd/disk/9660
  227. .SH "SEE ALSO"
  228. .I 9660srv
  229. (in
  230. .IR dossrv (4)),
  231. .IR cdfs (4),
  232. .IR mkfs (8)