Subversion Repositories planix.SVN

Rev

Rev 2 | Details | Compare with Previous | Last modification | View Log | RSS feed

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