source: trunk/minix/man/man8/part.8@ 9

Last change on this file since 9 was 9, checked in by Mattia Monga, 13 years ago

Minix 3.1.2a

File size: 4.7 KB
Line 
1.TH PART 8
2.SH NAME
3part \- partition table editor
4.SH SYNOPSIS
5.B part
6.RI [ device "] ..."
7.SH DESCRIPTION
8.B Part
9is a screen oriented partition table editor.
10.PP
11While editing you will see six lines of numbers, the first line shows the
12device name and its geometry (number of cylinders, heads and sectors), the
13second shows the start and end of the drive or partition you are working on,
14the last four lines show the different partitions or subpartitions. All
15numbers except those on the second line can be edited. Question marks are
16showed instead of numbers if the partition table is not loaded yet. You
17have to select a device and type 'r'.
18.PP
19Editing is a simple matter of moving around with the arrow keys and changing
20the values with + and \- (or PgUp and PgDn), or by typing the desired value.
21The '?' key will give a small list of commands, the '!' key gives advice on
22how to make a new entry.
23.PP
24The spacebar toggles between showing the size of the partition and the last
25sector on the partition. Useful to check if a partition is adjacent to the
26next.
27.PP
28The 'm' key is "magical", it lets you cycle through a set of interesting
29values for the base or size of a partition. These values are: Aligned to a
30cylinder, taped to other partitions (inside or outside), or filling out holes.
31.BR "Use this key" !
32.PP
33MINIX 3 subpartition tables or extended partitions may be edited after hitting
34the '>' key. The number of this partition will be shown after the device
35name on the second row, e.g.
36.BR /dev/hd0:2 .
37MINIX 3 subpartition tables are shown as is, but extended partition bases are
38translated to absolute offsets on the screen to hide the gory details of their
39implementation from the innocent user. (Hit 'p' if you dare.) The '<' key
40will bring you back to the enclosing partition table.
41.PP
42With arguments,
43.B part
44will use the given devices or files. Without arguments,
45.B part
46will use all interesting block devices in
47.B /dev
48sorted by device number and starting with
49.BR /dev/hd0 .
50.PP
51Values that are out of range, overlapping, or otherwise strange are shown in
52reverse video. Values that may possibly be a problem for operating systems
53other then MINIX 3 are shown in bold characters.
54.PP
55The name of the device is highlighted when it has not been read yet.
56.PP
57Head or sector numbers are highlighted if the partition does not start or
58end at a cylinder boundary.
59.PP
60The base and/or size field is highlighted if they fall outside the device,
61if they are inside some other partition, if the base equals the device's base
62(no room for the boot sector), or if the size is zero.
63.PP
64.B Part
65complies with the good old \s-2UNIX\s+2 tradition of trusting the user.
66It will write any table, no matter how bad. You have been warned.
67.PP
68By the way, as far as MINIX 3 is concerned there is absolutely no reason to
69make partitions start precisely on a cylinder or track nor does it have to
70be an exact number of cylinders long. MINIX 3 only looks at the base and size
71of a partition, the geometry of the drive doesn't have to be correct. Other
72Operating systems can be very picky about partitions that are not aligned.
73Some partition editors may refuse to edit a table, others may even make a
74mess of the table. The only exception is the first partition, it
75traditionally starts on the first track, not the first cylinder. All
76editors must understand this. (Subpartition tables are MINIX 3 specific, so
77there is no reason at all for any alignment.)
78.SS "Extended Partitions"
79Extended partitions are a mess that is only made slightly better by
80.B part
81by translating the base offsets to absolute numbers. It is better to use DOS
82.B fdisk
83to create them, but if you insist on using
84.B part
85then this is what they should look like:
86.RS
87.sp
88The extended partition entry in the primary partition table must cover the
89whole logical partition space within it.
90.sp
91The area thus created is split in segments, each segment contains a partition
92table in sector 0 and one (just one) logical partition.
93.sp
94The first entry of a segment's partition table describes this logical
95partition: it's partition ID, base and size.
96.sp
97The second entry is an extended partition that describes base and size of
98the next segment (partition table and logical partition). The last segment's
99partition table is empty, or contains one logical partition.
100.SH "SEE ALSO"
101.BR mkfs (1),
102.BR fd (4),
103.BR hd (4).
104.SH BUGS
105You can have a table read, messed up, and written in no time, be careful.
106.PP
107You can't type head or sector numbers directly.
108.PP
109Sectors are counted from 0 for consistency, but the partition table counts
110from 1 like DOS addresses them. Most confusing.
111.PP
112You can't write a backup copy to a file, that's what
113.BR dd (1)
114with count=1 is for.
115.SH AUTHOR
116Kees J. Bot (kjb@cs.vu.nl)
Note: See TracBrowser for help on using the repository browser.