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