1 .\" $NetBSD: makefs.8,v 1.32 2009/01/20 20:47:25 bjh21 Exp $
3 .\" Copyright (c) 2001-2003 Wasabi Systems, Inc.
4 .\" All rights reserved.
6 .\" Written by Luke Mewburn for Wasabi Systems, Inc.
8 .\" Redistribution and use in source and binary forms, with or without
9 .\" modification, are permitted provided that the following conditions
11 .\" 1. Redistributions of source code must retain the above copyright
12 .\" notice, this list of conditions and the following disclaimer.
13 .\" 2. Redistributions in binary form must reproduce the above copyright
14 .\" notice, this list of conditions and the following disclaimer in the
15 .\" documentation and/or other materials provided with the distribution.
16 .\" 3. All advertising materials mentioning features or use of this software
17 .\" must display the following acknowledgement:
18 .\" This product includes software developed for the NetBSD Project by
19 .\" Wasabi Systems, Inc.
20 .\" 4. The name of Wasabi Systems, Inc. may not be used to endorse
21 .\" or promote products derived from this software without specific prior
22 .\" written permission.
24 .\" THIS SOFTWARE IS PROVIDED BY WASABI SYSTEMS, INC. ``AS IS'' AND
25 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
26 .\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
27 .\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL WASABI SYSTEMS, INC
28 .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
29 .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
30 .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
31 .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
32 .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
33 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
34 .\" POSSIBILITY OF SUCH DAMAGE.
43 .Nd create a file system image from a directory tree or a mtree manifest
47 .Op Fl B Ar byte-order
48 .Op Fl b Ar free-blocks
49 .Op Fl d Ar debug-mask
51 .Op Fl f Ar free-files
52 .Op Fl M Ar minimum-size
53 .Op Fl m Ar maximum-size
54 .Op Fl N Ar userdb-dir
55 .Op Fl o Ar fs-options
56 .Op Fl S Ar sector-size
57 .Op Fl s Ar image-size
60 .Ar directory | manifest
64 creates a file system image into
66 from the directory tree
68 or from the mtree manifest
70 No special devices or privileges are required to perform this task.
72 The options are as follows:
74 .It Fl B Ar byte-order
75 Set the byte order of the image to
88 Some file systems may have a fixed byte order; in those cases this
89 argument will be ignored.
90 .It Fl b Ar free-blocks
91 Ensure that a minimum of
93 free blocks exist in the image.
96 suffix may be provided to indicate that
98 indicates a percentage of the calculated image size.
99 .It Fl d Ar debug-mask
100 Enable various levels of debugging, depending upon which bits are
111 This option has no effect when the image is created from a mtree manifest
112 rather than a directory.
114 If a specfile entry exists in the underlying file system, its
115 permissions and modification time will be used unless specifically
116 overridden by the specfile.
117 An error will be raised if the type of entry in the specfile
118 conflicts with that of an existing entry.
120 In the opposite case (where a specfile entry does not have an entry
121 in the underlying file system) the following occurs:
122 If the specfile entry is marked
124 the specfile entry is ignored.
125 Otherwise, the entry will be created in the image, and it is
126 necessary to specify at least the following parameters in the
139 (in the case of symbolic links).
142 isn't provided, the current time will be used.
145 isn't provided, the current file flags will be used.
146 Missing regular file entries will be created as zero-length files.
147 .It Fl f Ar free-files
148 Ensure that a minimum of
150 free files (inodes) exist in the image.
153 suffix may be provided to indicate that
155 indicates a percentage of the calculated image size.
156 .It Fl M Ar minimum-size
157 Set the minimum size of the file system image to
159 .It Fl m Ar maximum-size
160 Set the maximum size of the file system image to
162 An error will be raised if the target file system needs to be larger
163 than this to accommodate the provided directory tree.
165 Use the user database text file
167 and group database text file
171 rather than using the results from the system's
175 (and related) library calls.
176 .It Fl o Ar fs-options
177 Set file system specific options.
179 is a comma separated list of options.
180 Valid file system specific options are detailed below.
181 .It Fl S Ar sector-size
182 Set the file system sector size to
184 .\" XXX: next line also true for cd9660?
186 .It Fl s Ar image-size
187 Set the size of the file system image to
193 The following file system types are supported:
194 .Bl -tag -width cd9660 -offset indent
196 BSD fast file system (default).
198 ISO 9660 file system.
201 Exclude file system nodes not explicitly listed in the specfile.
204 Where sizes are specified, a decimal number of bytes is expected.
205 Two or more numbers may be separated by an
207 to indicate a product.
208 Each number may have one of the following optional suffixes:
209 .Bl -tag -width 3n -offset indent -compact
211 Block; multiply by 512
213 Kibi; multiply by 1024 (1 KiB)
215 Mebi; multiply by 1048576 (1 MiB)
217 Gibi; multiply by 1073741824 (1 GiB)
219 Tebi; multiply by 1099511627776 (1 TiB)
221 Word; multiply by the number of bytes in an integer
225 .Ss FFS-specific options
227 images have ffs-specific optional parameters that may be provided.
228 Each of the options consists of a keyword, an equal sign
231 The following keywords are supported:
233 .Bl -tag -width optimization -offset indent -compact
235 Expected average file size.
237 Expected number of files per directory.
245 Label name of the image.
247 Maximum blocks per file in a cylinder group.
251 Optimization preference; one of
258 Maximum total number of blocks in a cylinder group.
261 1 for FFS (default), 2 for UFS2.
263 .Ss CD9660-specific options
265 images have ISO9660-specific optional parameters that may be
267 The arguments consist of a keyword and, optionally, an equal sign
270 The following keywords are supported:
272 .Bl -tag -width omit-trailing-period -offset indent -compact
273 .It Sy allow-deep-trees
274 Allow the directory structure to exceed the maximum specified in
276 .\" .It Sy allow-illegal-chars
278 .\" .It Sy allow-lowercase
280 .It Sy allow-max-name
281 Allow 37 instead of 33 characters for filenames by omitting the
283 .It Sy allow-multidot
284 Allow multiple dots in a filename.
286 Application ID of the image.
294 Write an MBR partition table to the image to allow older CHRP hardware to
296 .It Sy boot-load-segment
297 Set load segment for the boot image.
299 Filename of a boot image in the format
309 .It Sy generic-bootimage
310 Load a generic boot image into the first 32K of the cd9660 image.
311 .It Sy hard-disk-boot
312 Boot image is a hard disk image.
313 .It Sy keep-bad-images
314 Don't throw away images whose write was aborted due to an error.
315 For debugging purposes.
317 Label name of the image.
319 Boot image is not bootable.
324 .It Sy no-trailing-padding
325 Do not pad the image (apparently Linux needs the padding).
326 .\" .It Sy omit-trailing-period
329 Preparer ID of the image.
331 Publisher ID of the image.
333 Use RockRidge extensions (for longer filenames, etc.).
335 Volume set identifier of the image.
353 .An Alan Perez-Rathke ,