Commit | Line | Data |
---|---|---|
fb9cffef MD |
1 | .\" Copyright (c) 2002 Marcel Moolenaar |
2 | .\" All rights reserved. | |
3 | .\" | |
4 | .\" Redistribution and use in source and binary forms, with or without | |
5 | .\" modification, are permitted provided that the following conditions | |
6 | .\" are met: | |
7 | .\" | |
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. | |
13 | .\" | |
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. | |
24 | .\" | |
25 | .\" $FreeBSD: src/sbin/gpt/gpt.8,v 1.17 2006/06/22 22:22:32 marcel Exp $ | |
fb9cffef | 26 | .\" |
476d60c5 | 27 | .Dd March 2, 2019 |
fb9cffef | 28 | .Dt GPT 8 |
fb5b3747 | 29 | .Os |
fb9cffef MD |
30 | .Sh NAME |
31 | .Nm gpt | |
32 | .Nd "GUID partition table maintenance utility" | |
33 | .Sh SYNOPSIS | |
34 | .Nm | |
35 | .Op Ar general_options | |
36 | .Ar command | |
37 | .Op Ar command_options | |
38 | .Ar device ... | |
39 | .Sh DESCRIPTION | |
40 | The | |
41 | .Nm | |
42 | utility provides the necessary functionality to manipulate GUID partition | |
43 | tables (GPTs), but see | |
44 | .Sx BUGS | |
45 | below for how and where functionality is missing. | |
68418bfc TN |
46 | GPT partitions are accessed as |
47 | .Dx | |
b9016d53 | 48 | disk slices, with same number as GPT partition, |
94f07f65 | 49 | 127 slices per disk device are supported. |
fb9cffef MD |
50 | The basic usage model of the |
51 | .Nm | |
52 | tool follows that of the | |
53 | .Xr cvs 1 | |
54 | tool. | |
55 | The general options are described in the following paragraph. | |
56 | The remaining paragraphs describe the individual commands with their options. | |
57 | Here we conclude by mentioning that a | |
58 | .Ar device | |
59 | is either a special file | |
60 | corresponding to a disk-like device or a regular file. | |
61 | The command is applied to each | |
62 | .Ar device | |
63 | listed on the command line. | |
64 | .Ss General Options | |
65 | The general options allow the user to change default settings or otherwise | |
66 | change the behaviour that is applicable to all commands. | |
67 | Not all commands use all default settings, so some general options may not | |
68 | have an effect on all commands. | |
69 | .Pp | |
70 | The | |
71 | .Fl p Ar count | |
72 | option allows the user to change the number of partitions the GPT can | |
163ffa07 | 73 | accommodate. |
fb9cffef MD |
74 | This is used whenever a new GPT is created. |
75 | By default, the | |
76 | .Nm | |
77 | utility will create space for 128 partitions (or 32 sectors of 512 bytes). | |
78 | .Pp | |
79 | The | |
80 | .Fl r | |
81 | option causes the | |
82 | .Nm | |
83 | utility to open the device for reading only. | |
84 | Currently this option is primarily useful for the | |
85 | .Ic show | |
86 | command, but the intent | |
87 | is to use it to implement dry-run behaviour. | |
88 | .Pp | |
89 | The | |
90 | .Fl v | |
91 | option controls the verbosity level. | |
92 | The level increases with every occurrence of this option. | |
93 | There is no formalized definition of the different levels yet. | |
94 | .Ss Commands | |
95 | .Bl -tag -width indent | |
96 | .\" ==== add ==== | |
97 | .It Xo | |
98 | .Nm | |
99 | .Ic add | |
100 | .Op Fl b Ar number | |
101 | .Op Fl i Ar index | |
102 | .Op Fl s Ar count | |
103 | .Op Fl t Ar type | |
104 | .Ar device ... | |
105 | .Xc | |
106 | The | |
107 | .Ic add | |
68418bfc TN |
108 | command allows the user to add a new partition to an existing table, |
109 | the name of the disk slice for the added partition is printed. | |
110 | By default, it will create a | |
111 | .Cm dfly | |
112 | partition covering the first available block | |
fb9cffef MD |
113 | of an unused disk space. |
114 | The command-specific options can be used to control this behaviour. | |
115 | .Pp | |
116 | The | |
117 | .Fl b Ar number | |
118 | option allows the user to specify the starting (beginning) sector number of | |
119 | the partition. | |
120 | The minimum sector number is 1, but has to fall inside an unused region of | |
121 | disk space that is covered by the GPT. | |
122 | .Pp | |
123 | The | |
124 | .Fl i Ar index | |
125 | option allows the user to specify which (free) entry in the GPT table is to | |
126 | be used for the new partition. | |
127 | By default, the first free entry is selected. | |
71cfd094 | 128 | Entries start at index 0 representing partition 0 of the GPT. |
fb9cffef MD |
129 | .Pp |
130 | The | |
131 | .Fl s Ar count | |
132 | option allows the user to specify the size of the partition in sectors. | |
133 | The minimum size is 1. | |
134 | .Pp | |
135 | The | |
136 | .Fl t Ar type | |
137 | option allows the user to specify the partition type. | |
138 | The type is given as an UUID, but | |
139 | .Nm | |
140 | accepts | |
41d6e048 | 141 | .Cm efi , swap , ufs , hfs , linux , dfly , hammer, hammer2 |
fb9cffef MD |
142 | and |
143 | .Cm windows | |
144 | as aliases for the most commonly used partition types. | |
68418bfc TN |
145 | .Cm ufs |
146 | is a | |
147 | .Fx | |
148 | UFS UUID. | |
149 | .Cm dfly | |
150 | has the alias | |
151 | .Cm dragonfly | |
152 | and is a | |
153 | .Dx | |
154 | .Xr disklabel64 5 | |
155 | UUID. | |
156 | You may also specify any symbolic name in the system | |
157 | .Xr uuids 5 | |
158 | files. | |
a844b566 FT |
159 | .Pp |
160 | .Em NOTE! | |
161 | If you don't specify a beginning sector with | |
162 | .Fl b Ar number | |
163 | , the new partition will be aligned to 1MiB in size and position | |
164 | (in case of 512 byte sector sizes). | |
6148a411 MD |
165 | .\" ==== boot ==== |
166 | .It Nm Ic boot Ar device ... | |
167 | The | |
168 | .Ic boot | |
169 | command allows the user to create a small boot partition in a freshly | |
170 | created GPT. | |
171 | .Pp | |
059599af | 172 | This command creates a small, 1GB boot partition as partition #0 |
b9016d53 TN |
173 | and hacks in a special |
174 | .Sq slice 1 | |
175 | in the PMBR which aliases it. | |
6148a411 | 176 | The PMBR is further modified to add the necessary boot code. |
a668cf6a TN |
177 | You can then disklabel GPT partition #0 and mount it, placing the contents of |
178 | .Pa /boot | |
179 | directory within. | |
180 | You must add a line to | |
181 | .Pa loader.conf , | |
182 | like | |
183 | .Bd -literal -offset indent | |
6d78c8db | 184 | vfs.root.mountfrom="ufs:da1s1a" |
a668cf6a TN |
185 | .Ed |
186 | .Pp | |
187 | which point to the actual root mount. | |
6148a411 MD |
188 | .Pp |
189 | Your root partition may be another GPT partition and you may use a 64 bit | |
b9016d53 | 190 | disklabel within that partition if you desire. |
6148a411 | 191 | .Pp |
b9016d53 TN |
192 | The |
193 | .Sq boot0 | |
194 | boot manager is used, it can be manipulated with the | |
195 | .Xr boot0cfg 8 | |
196 | command, | |
197 | .Sq packet | |
198 | option usually needs to be set. | |
199 | .Pp | |
200 | .Em NOTE! | |
201 | A disk setup with the | |
202 | .Ar boot | |
6d78c8db TN |
203 | command may not be shared with another OS, |
204 | as it doesn't use a fully standard GPT. | |
b9016d53 TN |
205 | .Pp |
206 | .Em WARNING! | |
207 | Some BIOSes may not be able to deal with this hack, your mileage may vary. | |
fb9cffef MD |
208 | .\" ==== create ==== |
209 | .It Nm Ic create Oo Fl fp Oc Ar device ... | |
210 | The | |
211 | .Ic create | |
212 | command allows the user to create a new (empty) GPT. | |
213 | By default, one cannot create a GPT when the device contains a MBR, | |
214 | however this can be overridden with the | |
215 | .Fl f | |
216 | option. | |
217 | If the | |
218 | .Fl f | |
219 | option is specified, an existing MBR is destroyed and any partitions | |
220 | described by the MBR are lost. | |
221 | .Pp | |
222 | The | |
223 | .Fl p | |
224 | option tells | |
225 | .Nm | |
226 | to create only the primary table and not the backup table. | |
227 | This option is only useful for debugging and should not be used otherwise. | |
228 | .\" ==== destroy ==== | |
229 | .It Nm Ic destroy Oo Fl r Oc Ar device ... | |
230 | The | |
231 | .Ic destroy | |
232 | command allows the user to destroy an existing, possibly not empty GPT. | |
233 | .Pp | |
234 | The | |
235 | .Fl r | |
236 | option instructs | |
237 | .Nm | |
238 | to destroy the table in a way that it can be recovered. | |
35a9ab8a MD |
239 | .\" ==== expand ==== |
240 | .It Nm Ic expand Ar device | |
241 | The | |
242 | .Ic expand | |
243 | command will expand an existing gpt label to cover a device which | |
244 | has grown in size, and will also expand the size of the last GPT | |
245 | partition to fit. | |
246 | This is typically the first step when expanding a hammer2 filesystem, | |
247 | after which disklabel -x and hammer2 growfs are run. | |
bd2b9b6f | 248 | .\" ==== init ==== |
d9306807 | 249 | .It Nm Ic init Fl f Oo Fl B Oc Oo Fl E Oc Ar device ... |
bd2b9b6f MD |
250 | The |
251 | .Ic init | |
252 | command allows the user to create a new GPT similar | |
253 | to the create command, but will also populate it with | |
254 | a boot slice (s0) and a | |
255 | .Dx | |
256 | slice (s1). | |
257 | The boot slice will be dos-formatted. | |
258 | The disklabel will be left empty and ready to edit. | |
259 | .Pp | |
260 | Due to the destructive nature of this directive, the | |
261 | .Fl f | |
262 | option must also be specified. | |
263 | .Pp | |
264 | If the | |
265 | .Fl B | |
266 | option is specified, /boot/bootx64.efi will be copied into | |
267 | the msdos slice (s0), and the disklabel will be initialized | |
268 | with -B in addition to the normal -r -w. | |
d9306807 MD |
269 | .Pp |
270 | If the | |
271 | .Fl E | |
272 | option is specified, the drive is TRIMed prior to the installation | |
273 | of the new label, if supported. The operation will continue if not | |
274 | supported. Note that this will complete destroy the contents of the | |
275 | drive. | |
fb9cffef MD |
276 | .\" ==== label ==== |
277 | .It Xo | |
278 | .Nm | |
279 | .Ic label | |
280 | .Op Fl a | |
281 | .Aq Fl f Ar file | Fl l Ar label | |
282 | .Ar device ... | |
283 | .Xc | |
284 | .It Xo | |
285 | .Nm | |
286 | .Ic label | |
287 | .Op Fl b Ar number | |
288 | .Op Fl i Ar index | |
289 | .Op Fl s Ar count | |
290 | .Op Fl t Ar type | |
291 | .Aq Fl f Ar file | Fl l Ar label | |
292 | .Ar device ... | |
293 | .Xc | |
294 | The | |
295 | .Ic label | |
296 | command allows the user to label any partitions that match the selection. | |
297 | At least one of the following selection options must be specified. | |
298 | .Pp | |
299 | The | |
300 | .Fl a | |
301 | option specifies that all partitions should be labeled. | |
302 | It is mutually exclusive with all other selection options. | |
303 | .Pp | |
304 | The | |
305 | .Fl b Ar number | |
306 | option selects the partition that starts at the given block number. | |
307 | .Pp | |
308 | The | |
309 | .Fl i Ar index | |
310 | option selects the partition with the given partition number. | |
71cfd094 | 311 | Partition numbers start at 0. |
fb9cffef MD |
312 | .Pp |
313 | The | |
314 | .Fl s Ar count | |
315 | option selects all partitions that have the given size. | |
316 | This can cause multiple partitions to be removed. | |
317 | .Pp | |
318 | The | |
319 | .Fl t Ar type | |
320 | option selects all partitions that have the given type. | |
321 | The type is given as an UUID or by the aliases that the | |
322 | .Ic add | |
323 | command accepts. | |
324 | This can cause multiple partitions to be removed. | |
325 | .Pp | |
326 | The | |
327 | .Fl f Ar file | |
328 | or | |
329 | .Fl l Ar label | |
330 | options specify the new label to be assigned to the selected partitions. | |
331 | The | |
332 | .Fl f Ar file | |
333 | option is used to read the label from the specified file. | |
334 | Only the first line is read from the file and the trailing newline | |
335 | character is stripped. | |
336 | If the file name is the dash or minus sign | |
337 | .Pq Fl , | |
338 | the label is read from | |
339 | the standard input. | |
340 | The | |
341 | .Fl l Ar label | |
342 | option is used to specify the label in the command line. | |
343 | The label is assumed to be encoded in UTF-8. | |
344 | .\" ==== migrate ==== | |
345 | .It Nm Ic migrate Oo Fl fs Oc Ar device ... | |
346 | The | |
347 | .Ic migrate | |
348 | command allows the user to migrate an MBR-based disk partitioning into a | |
349 | GPT-based partitioning. | |
350 | By default, the MBR is not migrated when it contains partitions of an unknown | |
351 | type. | |
352 | This can be overridden with the | |
353 | .Fl f | |
354 | option. | |
355 | Specifying the | |
356 | .Fl f | |
357 | option will cause unknown partitions to be ignored and any data in it | |
358 | to be lost. | |
359 | .Pp | |
360 | The | |
361 | .Fl s | |
362 | option prevents migrating | |
363 | .Bx | |
364 | disk labels into GPT partitions by creating | |
365 | the GPT equivalent of a slice. | |
366 | .\" ==== remove ==== | |
367 | .It Nm Ic remove Oo Fl a Oc Ar device ... | |
368 | .It Xo | |
369 | .Nm | |
370 | .Ic remove | |
371 | .Op Fl b Ar number | |
372 | .Op Fl i Ar index | |
373 | .Op Fl s Ar count | |
374 | .Op Fl t Ar type | |
375 | .Ar device ... | |
376 | .Xc | |
377 | The | |
378 | .Ic remove | |
379 | command allows the user to remove any and all partitions that match the | |
380 | selection. | |
381 | It uses the same selection options as the | |
382 | .Ic label | |
383 | command. | |
384 | See above for a description of these options. | |
385 | Partitions are removed by clearing the partition type. | |
386 | No other information is changed. | |
387 | .\" ==== show ==== | |
476d60c5 | 388 | .It Nm Ic show Oo Fl glu Oc Ar device ... |
fb9cffef MD |
389 | The |
390 | .Ic show | |
391 | command displays the current partitioning on the listed devices and gives | |
392 | an overall view of the disk contents. | |
476d60c5 AL |
393 | By default, the GPT partition type is displayed in a user-friendly form. |
394 | If the | |
395 | .Fl u | |
396 | option is specified, the GPT partition type is displayed as a UUID. | |
fb9cffef MD |
397 | With the |
398 | .Fl l | |
476d60c5 | 399 | option, the GPT partition label will be displayed instead of the GPT partition |
fb9cffef | 400 | type. |
fb9cffef | 401 | With the |
476d60c5 AL |
402 | .Fl g |
403 | option, the GPT partition GUID will be displayed instead of the GPT partition | |
404 | type. | |
405 | None of the options has any effect on non-GPT partitions. | |
406 | The order of precedence of the options are: | |
407 | .Fl l , | |
408 | .Fl g , | |
409 | .Fl u . | |
fb9cffef | 410 | .El |
68418bfc TN |
411 | .Sh FILES |
412 | .Bl -tag -width ".Pa /etc/defaults/uuids" | |
b9016d53 TN |
413 | .It Pa /boot/boot0 |
414 | The default | |
415 | .Sq boot0 | |
416 | image. | |
68418bfc TN |
417 | .It Pa /etc/defaults/uuids |
418 | A list of UUIDs | |
419 | and their symbolic names provided by the OS vendor. | |
420 | .It Pa /etc/uuids | |
421 | A list of UUIDs | |
422 | and their symbolic names provided by the system administrator. | |
423 | .El | |
424 | .Sh EXAMPLES | |
425 | To install an empty GPT on | |
426 | .Pa ad6 : | |
427 | .Pp | |
428 | .Dl "gpt create ad6" | |
429 | .Pp | |
430 | GPT partitions are defined in number of sectors, the sector size is usually 512B, | |
431 | which is assumed in the examples below, it can be found using: | |
432 | .Pp | |
433 | .Dl "gpt -v show ad6" | |
434 | .Pp | |
435 | To add a dummy GPT partition 0: | |
436 | .Pp | |
a668cf6a | 437 | .Dl "gpt add -i0 -s16 ad6" |
68418bfc TN |
438 | .Pp |
439 | You might want to do this to not use slice 0 for data; | |
440 | when GPT is not used on a disk, slice 0 is the compatibility slice, | |
441 | which is used for | |
442 | .Dq dangerously dedicated | |
443 | disks. | |
444 | For GPT slice 0 has no special meaning, it is just the first slice on the disk. | |
445 | .Pp | |
446 | To add a GPT partition of size approx. 100GB: | |
447 | .Pp | |
448 | .Dl "gpt add -s200000000 ad6" | |
449 | .Pp | |
450 | This will be GPT partition 1 as it is the first one free, | |
451 | it will be accessible as | |
452 | .Pa ad6s1 , | |
453 | which is also printed by the command. | |
454 | The type will be | |
455 | .Dq DragonFly Label64 , | |
456 | it will have to be set up by | |
457 | .Xr disklabel64 8 . | |
458 | .Pp | |
459 | To add GPT partition 5 with type | |
460 | .Dq DragonFly HAMMER | |
461 | using the remaining free space: | |
462 | .Bd -literal -offset indent | |
463 | gpt add -i5 -t "DragonFly HAMMER" ad6 | |
464 | .Ed | |
465 | .Pp | |
466 | To print the contents of the GPT: | |
467 | .Pp | |
468 | .Dl "gpt show ad6" | |
b9016d53 | 469 | .Ss Boot Setup |
6896d265 TN |
470 | To setup a disk using GPT for booting, the steps below can be used. |
471 | System is copied from an already installed disk, | |
472 | e.g.\& a hard disk or an install CD. | |
473 | This example will setup disk | |
6d78c8db | 474 | .Pa da1 |
6896d265 TN |
475 | with GPT for booting, using the |
476 | .Ic boot | |
477 | command. | |
478 | .Pp | |
479 | .Em WARNING! | |
480 | Any previous data on disk installed to will be deleted. | |
b9016d53 | 481 | .Bd -literal -offset indent |
6d78c8db TN |
482 | gpt create -f da1 |
483 | gpt boot da1 | |
484 | boot0cfg -s 2 da1 | |
485 | disklabel -B -r -w da1s0 auto | |
486 | disklabel -e da1s0 # add `a: * * 4.2BSD', to add `a' partition | |
487 | # with fstype `4.2BSD' covering whole slice | |
b9016d53 | 488 | |
6d78c8db TN |
489 | gpt add da1 |
490 | disklabel64 -r -w da1s1 auto | |
491 | disklabel64 -e da1s1 # add `b: 4G * swap', to add `b' partition | |
492 | # with fstype `swap' and size 4GB, | |
493 | # add `a: * * HAMMER', to add `a' partition | |
494 | # with fstype `HAMMER' covering rest of slice | |
495 | newfs_hammer -L ROOT /dev/da1s1a | |
496 | mount_hammer /dev/da1s1a /mnt | |
ec05e219 | 497 | |
6d78c8db | 498 | newfs /dev/da1s0a |
ec05e219 | 499 | mkdir /mnt/boot |
6d78c8db | 500 | mount /dev/da1s0a /mnt/boot |
ec05e219 | 501 | |
b9016d53 | 502 | cpdup / /mnt # copy each file system you need, e.g. |
ec05e219 | 503 | cpdup /boot /mnt/boot |
b9016d53 | 504 | cpdup /var /mnt/var |
ec05e219 | 505 | cpdup /var/tmp /mnt/var/tmp |
b9016d53 TN |
506 | cpdup /usr /mnt/usr |
507 | ||
6896d265 | 508 | cd /mnt |
6d78c8db TN |
509 | vi etc/fstab # add `/dev/da1s1a / hammer rw', |
510 | # add `/dev/da1s1b none swap sw', | |
511 | # add `/dev/da1s0a /boot ufs rw 1 1', | |
6896d265 | 512 | # delete lines for file systems cpdup'ed above |
6d78c8db | 513 | vi boot/loader.conf # add `vfs.root.mountfrom="hammer:da1s1a"' |
b9016d53 | 514 | cd |
ec05e219 | 515 | umount /mnt/boot |
b9016d53 TN |
516 | umount /mnt |
517 | .Ed | |
68418bfc TN |
518 | .Sh COMPATIBILITY |
519 | The GPT that | |
520 | .Nm | |
521 | manipulates is part of the EFI standard and is supported by many OSs. | |
522 | GPT uses 64 bits to store number of sectors, this supports very large disks. | |
523 | With the prevalent sector size of 512B this is 8 billion TB. | |
fb9cffef | 524 | .Sh SEE ALSO |
68418bfc TN |
525 | .Xr uuid 3 , |
526 | .Xr disklabel64 5 , | |
527 | .Xr uuids 5 , | |
b9016d53 | 528 | .Xr boot0cfg 8 , |
68418bfc TN |
529 | .Xr disklabel 8 , |
530 | .Xr disklabel64 8 , | |
fb9cffef MD |
531 | .Xr fdisk 8 , |
532 | .Xr mount 8 , | |
533 | .Xr newfs 8 , | |
68418bfc | 534 | .Xr newfs_hammer 8 , |
fb9cffef MD |
535 | .Xr swapon 8 |
536 | .Sh HISTORY | |
537 | The | |
538 | .Nm | |
539 | utility appeared in | |
540 | .Fx 5.0 | |
541 | for ia64. | |
68418bfc TN |
542 | It was imported to |
543 | .Dx 1.9 . | |
fb9cffef MD |
544 | .Sh BUGS |
545 | The development of the | |
546 | .Nm | |
547 | utility is still work in progress. | |
548 | Many necessary features are missing or partially implemented. | |
549 | In practice this means that the manual page, supposed to describe these | |
550 | features, is farther removed from being complete or useful. | |
551 | As such, missing functionality is not even documented as missing. | |
552 | However, it is believed that the currently present functionality is reliable | |
553 | and stable enough that this tool can be used without bullet-proof footware if | |
554 | one thinks one does not make mistakes. | |
555 | .Pp | |
556 | It is expected that the basic usage model does not change, but it is | |
557 | possible that future versions will not be compatible in the strictest sense | |
558 | of the word. | |
559 | For example, the | |
560 | .Fl p Ar count | |
561 | option may be changed to a command option rather than a generic option. | |
562 | There are only two commands that use it so there is a chance that the natural | |
563 | tendency for people is to use it as a command option. | |
564 | Also, options primarily intended for diagnostic or debug purposes may be | |
565 | removed in future versions. | |
566 | .Pp | |
567 | Another possibility is that the current usage model is accompanied by | |
568 | other interfaces to make the tool usable as a back-end. | |
569 | This all depends on demand and thus feedback. | |
68418bfc TN |
570 | .Pp |
571 | The | |
572 | .Ic migrate | |
573 | command doesn't support | |
574 | .Dx | |
575 | partition types. |