prep revision 1.1 
1Note you will be modifying your HD's if you mess something up here you
2could lose everything on all the drives that you mess with.  It is
3therefore advised that you:
4
5	Write down your current configurations.  Do this
6	by writing down all partition info (especially their sizes).
7
8	Back up the partitions you are keeping.
9
10What you need to do is partition your drives; creating
11space for at least root, swap and /usr partitions and possibly at
12least one more for /local if you have the space.
13
14The partitioning can be done in two ways, the first method heavily
15relies on the AHDI way of partitioning, the second method nearly
16ignores the AHDI partitioning and gives you far more flexibility.
17Currently, the second method can only be achieved from a working
18NetBSD/atari system.  How this should be done is described in
19"upgrading to NetBSD-labeling".
20
21Using AHDI partitioning:
22	The paritioning can be done with the AHDI-disk that is
23	provided with your TT or Falcon. Note that the AHDI partioning
24	function erases all partions on your harddisk even if they are
25	not changed!
26	I know this is rather stupid, but don't say I didn't warn you.
27
28	You will need the 'chg_part' program from the bootdisk to
29	prepare your harddisk a bit more. This program will change the
30	partition-id so NetBSD knows which partitions it can use. The
31	synopsis is:
32		chg_part <driveno> <partno> <new_id>
33
34	The drive number corresponds with the drive's SCSI-id. The new
35	id can be selected from one of the following acronyms:
36		NBU - NetBSD User partition
37		NBR - NetBSD Root partition
38		NBS - NetBSD Swap partition
39	Because NetBSD cannot be bootloaded (yet) and thus must be
40	loaded through GEM, it is unwise to use drive 'C'
41	(drive 0/partition 1) as a NetBSD partition. When a partition-id
42	is changed, GEMDOS won't be able to recognize your drive, so be
43	warned that the drive labels are shifted afterwards. The chg_part
44	program still recognizes them, take this into account when
45	re-labeling partitions. Also note that the chg_part process is
46	reversible. So don't panic if you made a mistake. Just run
47	chg_part again with the same drive/partition arguments but
48	supplied the original partition id.
49
50Upgrading to NetBSD-labeling:
51	First of all the new disk label functions are fully backwards
52	compatible with the current (old) behaviour, therefore you don't
53	have to rename partition identifiers if you don't want to. The only
54	limitation is that you won't be able to write a disklabel to your
55	harddisk ("Device not configured.").
56
57	If you'ld like to have the flexibility of the NetBSD disk label,
58	the procedure is very simple: change the identifier of the AHDI
59	partition that contains your NetBSD root filesystem from NBR to NBD.
60	Boot NetBSD; run `disklabel -e sd?'; disklabel will start vi;
61	quit vi without changing anything; now the disklabel should be
62	written to the NBD partition. If at this point disklabel tells
63	you that one or more of your partitions extend past the end of
64	the unit, then you have an old version of disklabel. Get the
65
66	If you like, you can now change the NBD partition id to RAW
67	(this would for example be necessary if the partition must be
68	shared with MiNT), but keep in mind that the partition id must
69	be either NBD or RAW, otherwise NetBSD won't be able to find the
70	disklabel. The NBS id (used for a swap partition) is no longer
71	needed, you can change it to whatever you like (or leave it as
72	is, if that's what you like :-) ). The same is true for the
73	NBU id's.
74
75	WARNINGS:
76		- the NBD partition does not necessarily have to be the
77		  partition that contains the NetBSD root filesystem, but
78		  it *must* be a partition that contains a fast filesystem.
79		  Do *not* try this with a partition that contains a gemdos,
80		  minix or ext2 filesystem; if you do, you'll *loose* a
81		  filesystem.
82		- Now that you have a real disklabel, you can modify it in
83		  (almost) any way you want. However, if you make a mess of
84		  the disk label, NetBSD may (or may not) make a mess of
85		  your disk! No freedom without responsibility.
86		  NetBSD will try to warn you for a possibly dangerous
87		  partition table, but it's up to you to either take that
88		  warning serious or ignore it (there may be good reasons
89		  to ignore the warning, if you know what you're doing).
90
91	So what do you do if you have a new disk, that will be exclusively
92	used by NetBSD? Very simple: don't let it get `infected' by the
93	AHDI `virus'. ,-) Just connect the disk to your TT/Falcon; boot
94	NetBSD; run `disklabel -e'; you'll see only one large partiton `d'
95	(there won't be any filesytem on it yet); you can create partitions
96	in any way you want, as you're no longer limited by an AHDI partition
97	table.
98