1
<!-- retain these comments for translator revision tracking -->
2
<!-- original version: 28997 untranslated -->
6
<title>Partitioning in Tru64 UNIX</title>
9
Tru64 UNIX, formerly known as Digital UNIX, which is in turn formerly
10
known as OSF/1, uses the partitioning scheme similar to the BSD <quote>disk
11
label</quote>, which allows for up to eight partitions per disk drive. The
12
partitions are numbered <quote>1</quote> through to <quote>8</quote> in
13
Linux and <quote>lettered</quote> <quote>a</quote> through to
14
<quote>h</quote> in UNIX. Linux kernels 2.2 and higher always correspond
15
<quote>1</quote> to <quote>a</quote>, <quote>2</quote> to <quote>b</quote>
16
and so on. For example, <filename>rz0e</filename> in Tru64 UNIX would most
17
likely be called <filename>sda5</filename> in Linux.
21
Partitions in a Tru64 disk label may overlap. Moreover, if this disk
22
will be used from Tru64, the <quote>c</quote> partition is required to span
23
the entire disk (thus overlapping all other non-empty partitions). Under
24
Linux this makes <filename>sda3</filename> identical to
25
<filename>sda</filename> (<filename>sdb3</filename> to
26
<filename>sdb</filename>, if present, and so on). However, the partman
27
partitioning tool used by &d-i; cannot handle overlapping partitions at
28
present. As a result, it is currently not recommended to share disks
29
between Tru64 and Debian. Partitions on Tru64 disks can be mounted
30
under Debian after installation has been completed.
34
Another conventional requirement is for the <quote>a</quote> partition to
35
start from the beginning of the disk, so that it always includes the boot
36
block with the disk label. If you intend to boot Debian from that disk, you
37
need to size it at least 2MB to fit aboot and perhaps a kernel.
38
Note that this partition is only required for compatibility; you must
39
not put a file system onto it, or you'll destroy data.
43
It is possible, and indeed quite reasonable, to share a swap partition
44
between UNIX and Linux. In this case it will be needed to do a
45
<command>mkswap</command> on that partition every time the system is rebooted
46
from UNIX into Linux, as UNIX will damage the swap signature. You may
47
want to run <command>mkswap</command> from the Linux start-up scripts before
48
adding swap space with <command>swapon -a</command>.
52
If you want to mount UNIX partitions under Linux, note that Digital UNIX
53
can use two different file system types, UFS and AdvFS, of which Linux
54
only understands the former.
60
<title>Partitioning in Windows NT</title>
64
Windows NT uses the PC-style partition table. If you are manipulating
65
existing FAT or NTFS partitions, it is recommended that you use the
66
native Windows NT tools (or, more conveniently, you can also
67
repartition your disk from the AlphaBIOS setup menu). Otherwise, it
68
is not really necessary to partition from Windows; the Linux
69
partitioning tools will generally do a better job. Note that when you
70
run NT, the Disk Administrator may offer you to write a <quote>harmless
71
signature</quote> on non-Windows disks if you have any.
72
<emphasis>Never</emphasis> let it do that, as this signature will destroy
73
the partition information.
77
If you plan to boot Linux from an ARC/AlphaBIOS/ARCSBIOS console, you
78
will need a (small) FAT partition for MILO. 5 MB is quite
79
sufficient. If Windows NT is installed, its 6 MB bootstrap partition
80
can be employed for this purpose. Debian &releasename; does not support
81
installing MILO. If you already have MILO installed on your system, or
82
install MILO from other media, Debian can still be booted from ARC.