1 .\" Copyright (c) 2013, 2014 Juniper Networks, Inc.
2 .\" All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
8 .\" 1. Redistributions of source code must retain the above copyright
9 .\" notice, this list of conditions and the following disclaimer.
10 .\" 2. Redistributions in binary form must reproduce the above copyright
11 .\" notice, this list of conditions and the following disclaimer in the
12 .\" documentation and/or other materials provided with the distribution.
14 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
15 .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
16 .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
17 .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
18 .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
19 .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
20 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
21 .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
22 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
23 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
27 .Dd September 12, 2014
32 .Nd "utility to make disk images"
46 .Op Fl p Ar partition ...
50 utility creates a disk image from the raw partition contents specified with
53 argument(s) and using the partitioning scheme specified with the
56 The disk image is written to
58 by default or the file specified with the
61 The image file is a raw disk image by default, but the format of the
62 image file can be specified with the
66 The disk image can be made bootable by specifying the scheme-specific boot
67 block contents with the
70 depending on the scheme,
71 with a boot partition.
72 The contents of such a boot partition is provided like any other partition
75 utility does not treat it any differently from other partitions.
77 Some partitioning schemes need a disk geometry and for those the
83 arguments, specifying the number of sectors per track and the number of
84 heads per cylinder (resp.)
86 Both the logical and physical sector size can be specified and for that the
96 argument is used to specify the logical sector size.
97 This is the sector size reported by a disk when queried for its capacity.
98 Modern disks use a larger sector size internally,
99 referred to as block size by the
101 utility and this can be specified by the
106 utility will use the (physical) block size to determine the start of
107 partitions and to round the size of the disk image.
111 option increases the level of output that the
117 option is used for testing purposes only and is not to be used in production.
120 utility will generate predictable values for Universally Unique Identifiers
121 (UUIDs) and time stamps so that consecutive runs of the
123 utility will create images that are identical.
125 For a complete list of supported partitioning schemes or supported output
126 format, or for a detailed description of how to specify partitions, run the
128 utility without any arguments.
130 .Bl -tag -width "TMPDIR" -compact
132 Directory to put temporary files in; default is
136 To create a bootable disk image that is partitioned using the GPT scheme and
137 containing a root file system that was previously created using
139 and also containing a swap partition, run the
142 .Dl % mkimg -s gpt -b /boot/pmbr -p freebsd-boot:=/boot/gptboot \
143 -p freebsd-ufs:=root-file-system.ufs -p freebsd-swap::1G \
146 The command line given above results in a raw image file.
147 This is because no output format was given.
148 To create a VMDK image for example, add the
152 utility and name the output file accordingly.
154 A nested partitioning scheme is created by running the
157 The output of the first will be fed as the contents of a partition to the
159 This can be done using a temporary file, like so:
160 .Dl % mkimg -s bsd -b /boot/boot -p freebsd-ufs:=root-file-system.ufs \
161 -p freebsd-swap::1G -o /tmp/bsd.img
162 .Dl % mkimg -s mbr -b /boot/mbr -p freebsd:=/tmp/bsd.img -o mbr-bsd.img
166 utility can be run in a cascaded fashion, whereby the output of the
167 first is fed directly into the second.
171 .Dl % mkimg -s mbr -b /boot/mbr -p freebsd:-'mkimg -s bsd -b /boot/boot \
172 -p freebsd-ufs:=root-file-system.ufs -p freebsd-swap::1G' -o mbr-bsd.img
174 To accomodate the need to have partitions named or numbered in a certain
177 utility allows for the specification of empty partitions.
178 For example, to create an image that is compatible with partition layouts
181 the 'd' partition often needs to be skipped.
182 This is accomplished by inserting an unused partition after the first 2
183 partition specifications.
184 It is worth noting at this time that the BSD scheme will automatically
185 skip the 'c' partition by virtue of it referring to the entire disk.
186 To create an image that is compatible with the qp120at disk, use the
189 .Dl % mkimg -s bsd -b /boot/boot -p freebsd-ufs:=root-file-system.ufs \
190 -p freebsd-swap::20M -p- -p- -p- -p- -p freebsd-ufs:=usr-file-system.ufs \
193 For partitioning schemes that feature partition labels, the
195 utility supports assigning labels to the partitions specified.
196 In the following example the file system partition is labeled as 'backup':
197 .Dl % mkimg -s gpt -p freebsd-ufs/backup:=file-system.ufs -o gpt.img
206 utility first appeared in
211 utility and manpage were written by Marcel Moolenaar <marcelm@juniper.net>