/[gentoo]/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml

Diff of /xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml

Parent Directory | Revision Log | View Patch Patch

Revision 1.23		Revision 1.43
1	<?xml version='1.0' encoding='UTF-8'?>	1	<?xml version='1.0' encoding='UTF-8'?>
2	<!DOCTYPE sections SYSTEM "/dtd/book.dtd">	2	<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3		3
4	<!-- The content of this document is licensed under the CC-BY-SA license -->	4	<!-- The content of this document is licensed under the CC-BY-SA license -->
5	<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->	5	<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6		6
7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml,v 1.23 2004/11/20 22:23:30 neysx Exp $ -->	7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml,v 1.43 2007/06/26 07:07:27 nightmorph Exp $ -->
8		8
9	<sections>	9	<sections>
10		10
11	<version>1.19</version>	11	<version>8.2</version>
12	<date>2004-11-02</date>	12	<date>2007-06-26</date>
13		13
14	<section>	14	<section>
15	<title>Introduction to Block Devices</title>	15	<title>Introduction to Block Devices</title>
16	<subsection>	16	<subsection>
17	<title>Block Devices</title>	17	<title>Block Devices</title>
18	<body>	18	<body>
19		19
20	<p>	20	<p>
21	We'll take a good look at disk-oriented aspects of Gentoo Linux	21	We'll start by taking a good look at disk-oriented aspects of Gentoo Linux
22	and Linux in general, including Linux filesystems, partitions and block devices.	22	and Linux in general, including Linux filesystems, partitions and block devices.
23	Then, once you're familiar with the ins and outs of disks and filesystems,	23	Then, once you're familiar with the ins and outs of disks and filesystems,
24	you'll be guided through the process of setting up partitions and filesystems	24	you'll be guided through the process of setting up partitions and filesystems
25	for your Gentoo Linux installation.	25	for your Gentoo Linux installation.
26	</p>	26	</p>
27		27
28	<p>	28	<p>
29	To begin, we'll introduce <e>block devices</e>. The most famous block device is	29	To begin, we'll introduce <e>block devices</e>. The most common block device is
30	probably the one that represents the first IDE drive in a Linux system, namely	30	the one that represents the first IDE drive in a Linux system, namely
31	<path>/dev/hda</path>. If your system uses SCSI drives, then your first hard	31	<path>/dev/hda</path>. If you are installing onto SCSI, FireWire, USB or SATA
32	drive would be <path>/dev/sda</path>.	32	drives, then your first hard drive would be <path>/dev/sda</path>. Additional
		33	drives are enumerated by the next letter in the alphabet. As an example, the
		34	third IDE disk could be found at <path>/dev/hdc</path>.
33	</p>	35	</p>
34		36
35	<p>	37	<p>
36	The block devices above represent an abstract interface to the disk. User	38	The block devices above represent an abstract interface to the disk. User
37	programs can use these block devices to interact with your disk without worrying	39	programs can use these block devices to interact with the disk without worrying
38	about whether your drives are IDE, SCSI or something else. The program can	40	about whether the drives are IDE, SCSI or something else. The program can
39	simply address the storage on the disk as a bunch of contiguous,	41	simply address the storage on the disk as a bunch of contiguous,
40	randomly-accessible 512-byte blocks.	42	randomly-accessible 512-byte blocks.
41	</p>	43	</p>
42		44
43	</body>	45	</body>
44	</subsection>	46	</subsection>
45	<subsection>	47	<subsection>
46	<title>Partitions and Slices</title>	48	<title>Partitions</title>
47	<body>	49	<body>
48		50
49	<p>	51	<p>
50	Although it is theoretically possible to use a full disk to house your Linux	52	Although it is theoretically possible to use a full disk to house your Linux
51	system, this is almost never done in practice. Instead, full disk block devices	53	system, this is almost never done in practice. Instead, full disk block devices
52	are split up in smaller, more manageable block devices. On most systems,	54	are split up in smaller, more manageable block devices. On most systems,
53	these are called <e>partitions</e>. Other architectures use a similar technique,	55	these are called <e>partitions</e>.
54	called <e>slices</e>.
55	</p>	56	</p>
56		57
57	</body>	58	</body>
58	</subsection>	59	</subsection>
59	</section>	60	</section>
…		…
63	<title>Default Partitioning Scheme</title>	64	<title>Default Partitioning Scheme</title>
64	<body>	65	<body>
65		66
66	<p>	67	<p>
67	If you are not interested in drawing up a partitioning scheme for your system,	68	If you are not interested in drawing up a partitioning scheme for your system,
68	you can use the partitioning scheme we use throughout this book:	69	you can use the partitioning scheme we use throughout this book. Choose the
		70	filesystem layout that best matches the type of PowerPC system you are
		71	installing on.
		72	</p>
		73
		74	</body>
		75	</subsection>
		76	<subsection>
		77	<title>Apple New World</title>
		78	<body>
		79
69	</p>	80	<p>
		81	Apple New World machines are fairly straightforward to configure. The first
		82	partition is always an <e>Apple Partition Map</e>. This partition keeps track
		83	of the layout of the disk. You cannot remove this partition. The next
		84	partition should always be a bootstrap partition. This partition contains a
		85	small (800k) HFS filesystem that holds a copy of the bootloader Yaboot and its
		86	configuration file. This partition is <e>not</e> the same as a
		87	<path>/boot</path> partition as found on other architectures. After the boot
		88	partition, the usual Linux filesystems are placed, according to the scheme
		89	below. The swap partition is a temporary storage place for when your system
		90	runs out of physical memory. The root partition will contain the filesystem
		91	that Gentoo is installed on. If you wish to dual boot, the OSX partition
		92	can go anywhere after the bootstrap partition to insure that yaboot starts
		93	first.
		94	</p>
		95
		96	<note>
		97	There may be "Disk Driver" partitions on your disk such as
		98	<path>Apple_Driver63</path>, <path>Apple_Driver_ATA</path>,
		99	<path>Apple_FWDriver</path>, <path>Apple_Driver_IOKit</path>, and
		100	<path>Apple_Patches</path>. These are used to boot MacOS, so if you have no
		101	need for this, you can remove them by initializing the disk with mac-fdisk's
		102	<c>i</c> option. This will completely erase the disk! If you are in doubt,
		103	just let them be.
		104	</note>
		105
		106	<note>
		107	If you partitioned this disk with Apple's Disk Utility, there may be
		108	128Mb spaces between partitions which Apple reserves for "future use". You
		109	can safely remove these.
		110	</note>
70		111
71	<table>	112	<table>
72	<tr>	113	<tr>
73	<th>Partition NewWorld</th>
74	<th>Partition OldWorld</th>
75	<th>Partition Pegasos</th>	114	<th>Partition</th>
		115	<th>Size</th>
76	<th>Filesystem</th>	116	<th>Filesystem</th>
		117	<th>Description</th>
		118	</tr>
		119	<tr>
		120	<ti><path>/dev/hda1</path></ti>
		121	<ti>32k</ti>
		122	<ti>None</ti>
		123	<ti>Apple Partition Map</ti>
		124	</tr>
		125	<tr>
		126	<ti><path>/dev/hda2</path></ti>
		127	<ti>800k</ti>
		128	<ti>HFS</ti>
		129	<ti>Apple Bootstrap</ti>
		130	</tr>
		131	<tr>
		132	<ti><path>/dev/hda3</path></ti>
		133	<ti>512Mb</ti>
		134	<ti>Swap</ti>
		135	<ti>Linux Swap</ti>
		136	</tr>
		137	<tr>
		138	<ti><path>/dev/hda4</path></ti>
		139	<ti>Rest of Disk</ti>
		140	<ti>ext3, reiserfs, xfs</ti>
		141	<ti>Linux Root</ti>
		142	</tr>
		143	</table>
		144
		145	</body>
		146	</subsection>
		147	<subsection>
		148	<title>Apple Old World</title>
		149	<body>
		150
		151	<p>
		152	Apple Old World machines are a bit more complicated to configure. The first
		153	partition is always an <e>Apple Partition Map</e>. This partition keeps track
		154	of the layout of the disk. You cannot remove this partition. If you are using
		155	BootX, the configuration below assumes that MacOS is installed on a seperate
		156	disk. If this is not the case, there will be additional partitions for "Apple
		157	Disk Drivers" such as <path>Apple_Driver63, Apple_Driver_ATA, Apple_FWDriver,
		158	Apple_Driver_IOKit, Apple_Patches</path> and the MacOS install. If you are
		159	using Quik, you will need to create a boot partition to hold the kernel, unlike
		160	other Apple boot methods. After the boot partition, the usual Linux filesystems
		161	are placed, according to the scheme below. The swap partition is a temporary
		162	storage place for when your system runs out of physical memory. The root
		163	partition will contain the filesystem that Gentoo is installed on.
		164	</p>
		165
		166	<note>
		167	If you are using an OldWorld machine, you will need to keep MacOS available.
		168	The layout here assumes MacOS is installed on a separate drive.
		169	</note>
		170
		171	<table>
		172	<tr>
		173	<th>Partition</th>
77	<th>Size</th>	174	<th>Size</th>
		175	<th>Filesystem</th>
78	<th>Description</th>	176	<th>Description</th>
79	</tr>	177	</tr>
80	<tr>	178	<tr>
81	<ti><path>/dev/hda1</path></ti>	179	<ti><path>/dev/hda1</path></ti>
82	<ti>/dev/hda1</ti>
83	<ti>(Not applicable)</ti>
84	<ti>(Partition Map)</ti>
85	<ti>32k</ti>	180	<ti>32k</ti>
		181	<ti>None</ti>
86	<ti>Apple_partition_map</ti>	182	<ti>Apple Partition Map</ti>
87	</tr>	183	</tr>
88	<tr>	184	<tr>
89	<ti><path>/dev/hda2</path></ti>	185	<ti><path>/dev/hda2</path></ti>
90	<ti>(Not needed)</ti>	186	<ti>32Mb</ti>
91	<ti>(Not applicable)</ti>	187	<ti>ext2</ti>
92	<ti>(bootstrap)</ti>	188	<ti>Quik Boot Partition (quik only)</ti>
		189	</tr>
		190	<tr>
		191	<ti><path>/dev/hda3</path></ti>
		192	<ti>512Mb</ti>
		193	<ti>Swap</ti>
		194	<ti>Linux Swap</ti>
		195	</tr>
		196	<tr>
		197	<ti><path>/dev/hda4</path></ti>
		198	<ti>Rest of Disk</ti>
		199	<ti>ext3, reiserfs, xfs</ti>
		200	<ti>Linux Root</ti>
		201	</tr>
		202	</table>
		203
		204	</body>
		205	</subsection>
		206	<subsection>
		207	<title>Pegasos</title>
		208	<body>
		209
		210	<p>
		211	The Pegasos partition layout is quite simple compared to the Apple layouts.
		212	The first partition is a Boot Partition, which contains kernels to be booted,
		213	along with an OpenFirmware script that presents a menu on boot. After the boot
		214	partition, the usual Linux filesystems are placed, according to the scheme
		215	below. The swap partition is a temporary storage place for when your system
		216	runs out of physical memory. The root partition will contain the filesystem
		217	that Gentoo is installed on.
		218	</p>
		219
		220	<table>
		221	<tr>
		222	<th>Partition</th>
		223	<th>Size</th>
		224	<th>Filesystem</th>
		225	<th>Description</th>
		226	</tr>
		227	<tr>
		228	<ti><path>/dev/hda1</path></ti>
		229	<ti>32Mb</ti>
		230	<ti>affs1 or ext2</ti>
		231	<ti>Boot Partition</ti>
		232	</tr>
		233	<tr>
		234	<ti><path>/dev/hda2</path></ti>
		235	<ti>512Mb</ti>
		236	<ti>Swap</ti>
		237	<ti>Linux Swap</ti>
		238	</tr>
		239	<tr>
		240	<ti><path>/dev/hda3</path></ti>
		241	<ti>Rest of Disk</ti>
		242	<ti>ext3, reiserfs, xfs</ti>
		243	<ti>Linux Root</ti>
		244	</tr>
		245	</table>
		246
		247	</body>
		248	</subsection>
		249	<subsection>
		250	<title>IBM PReP (RS/6000)</title>
		251	<body>
		252
		253	<p>
		254	The IBM PowerPC Reference Platform (PReP) requires a small PReP boot partition
		255	on the disk's first partition, followed by the swap and root partitions.
		256	</p>
		257
		258	<table>
		259	<tr>
		260	<th>Partition</th>
		261	<th>Size</th>
		262	<th>Filesystem</th>
		263	<th>Description</th>
		264	</tr>
		265	<tr>
		266	<ti><path>/dev/hda1</path></ti>
93	<ti>800k</ti>	267	<ti>800k</ti>
94	<ti>Apple_Bootstrap</ti>	268	<ti>None</ti>
		269	<ti>PReP Boot Partition (Type 0x41)</ti>
		270	</tr>
		271	<tr>
		272	<ti><path>/dev/hda2</path></ti>
		273	<ti>512Mb</ti>
		274	<ti>Swap</ti>
		275	<ti>Linux Swap (Type 0x82)</ti>
95	</tr>	276	</tr>
96	<tr>	277	<tr>
97	<ti><path>/dev/hda3</path></ti>	278	<ti><path>/dev/hda3</path></ti>
98	<ti><path>/dev/hda2</path></ti>
99	<ti><path>/dev/hda1</path></ti>
100	<ti>(swap)</ti>
101	<ti>512M</ti>
102	<ti>Swap partition</ti>
103	</tr>
104	<tr>
105	<ti><path>/dev/hda4</path></ti>
106	<ti><path>/dev/hda3</path></ti>
107	<ti><path>/dev/hda2</path></ti>
108	<ti>ext3</ti>
109	<ti>Rest of the disk</ti>	279	<ti>Rest of Disk</ti>
110	<ti>Root partition</ti>	280	<ti>ext3, reiserfs, xfs</ti>
		281	<ti>Linux Root (Type 0x83)</ti>
111	</tr>	282	</tr>
112	</table>	283	</table>
113		284
114	<note>	285	<warn>
115	There are some partitions named like this: <path>Apple_Driver43,	286	<c>parted</c> is able to resize partitions including HFS+. Unfortunately there
116	Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit,	287	may be issues with resizing HFS+ journaled filesystems, so, for the best
117	Apple_Patches</path>. If you are not planning to use MacOS 9 you can	288	results, switch off journaling in Mac OS X before resizing. Remember that any
118	delete them, because MacOS X and Linux don't need them.	289	resizing operation is dangerous, so attempt at your own risk! Be sure to always
119	You might have to use parted in order to delete them, as mac-fdisk can't delete them yet.	290	have a backup of your data before resizing!
120	</note>	291	</warn>
121		292
122	<p>	293	<p>
123	If you are interested in knowing how big a partition should be, or even how many	294	If you are interested in knowing how big a partition should be, or even how many
124	partitions you need, read on. Otherwise continue now with <uri	295	partitions you need, read on. Otherwise continue now with
125	link="#fdisk">Default: Using mac-fdisk (Apple/IBM) to Partition your Disk</uri>	296	<uri link="#mac-fdisk"> Default: Using mac-fdisk (Apple) to Partition your Disk
126	or <uri link="#parted">Alternative: Using parted (especially Pegasos) to	297	</uri> or <uri link="#parted">Alternative: Using parted (IBM/Pegasos) to
127	Partition your Disk</uri>.	298	Partition your Disk</uri>.
128	</p>	299	</p>
129		300
130	</body>	301	</body>
131	</subsection>	302	</subsection>
…		…
136	<p>	307	<p>
137	The number of partitions is highly dependent on your environment. For instance,	308	The number of partitions is highly dependent on your environment. For instance,
138	if you have lots of users, you will most likely want to have your	309	if you have lots of users, you will most likely want to have your
139	<path>/home</path> separate as it increases security and makes backups easier.	310	<path>/home</path> separate as it increases security and makes backups easier.
140	If you are installing Gentoo to perform as a mailserver, your <path>/var</path>	311	If you are installing Gentoo to perform as a mailserver, your <path>/var</path>
141	should be separate as all mails are stored inside <path>/var</path>. A good	312	should be separate as all received mail is stored in <path>/var</path>. A good
142	choice of filesystem will then maximise your performance. Gameservers will have	313	choice of filesystem will then maximise your performance. Game servers should
143	a separate <path>/opt</path> as most gaming servers are installed there. The	314	have a separate <path>/opt</path> as most game servers are installed there. The
144	reason is similar for <path>/home</path>: security and backups.	315	reason is similar for <path>/home</path>: security and backups. Whatever layout
		316	you chose, you will definitely want to keep <path>/usr</path> large: not only
		317	will it contain the majority of applications, the Portage tree alone takes
		318	more than 500Mb excluding the various sources that are stored in it.
145	</p>	319	</p>
146		320
147	<p>	321	<p>
148	As you can see, it very much depends on what you want to achieve. Separate	322	As you can see, it very much depends on what you want to achieve. Separate
149	partitions or volumes have the following advantages:	323	partitions or volumes have the following advantages:
…		…
161	If necessary, file system checks are reduced in time, as multiple checks can	335	If necessary, file system checks are reduced in time, as multiple checks can
162	be done in parallel (although this advantage is more with multiple disks than	336	be done in parallel (although this advantage is more with multiple disks than
163	it is with multiple partitions)	337	it is with multiple partitions)
164	</li>	338	</li>
165	<li>	339	<li>
166	Security can be enhanced by mounting some partitions or volumes read-only,	340	Security can be enhanced by mounting some partitions or volumes read-only,
167	nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc.	341	nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc.
168	</li>	342	</li>
169	</ul>	343	</ul>
170		344
171	<p>	345	<p>
172	However, multiple partitions have one big disadvantage: if not configured	346	However, multiple partitions have one big disadvantage: if not configured
173	properly, you might result in having a system with lots	347	properly, you might result in having a system with lots of free space on one
174	of free space on one partition and none on another. There is also a 15-partition	348	partition and none on another. There is also a 15-partition limit for SCSI and
175	limit for SCSI and SATA.	349	SATA.
176	</p>	350	</p>
177		351
178	</body>	352	</body>
179	</subsection>	353	</subsection>
180	</section>	354	</section>
181	<section id="fdisk">	355	<section id="mac-fdisk">
182	<title>Default: Using mac-fdisk (Apple/IBM) Partition your Disk</title>	356	<title>Default: Using mac-fdisk (Apple) Partition your Disk</title>
183	<body>	357	<body>
184		358
185	<p>	359	<p>
186	At this point, create your partitions using <c>mac-fdisk</c>:	360	At this point, create your partitions using <c>mac-fdisk</c>:
187	</p>	361	</p>
…		…
189	<pre caption="Starting mac-fdisk">	363	<pre caption="Starting mac-fdisk">
190	# <i>mac-fdisk /dev/hda</i>	364	# <i>mac-fdisk /dev/hda</i>
191	</pre>	365	</pre>
192		366
193	<p>	367	<p>
194	First delete the partitions you have cleared previously to make room for your	368	If you used Apple's Disk Utility to leave space for Linux, first delete the
195	Linux partitions. Use <c>d</c> in <c>mac-fdisk</c> to delete those partition(s).	369	partitions you have created previously to make room for your new install. Use
		370	<c>d</c> in <c>mac-fdisk</c> to delete those partition(s). It will ask for the
196	It will ask for the partition number to delete. Usually the first partition on	371	partition number to delete. Usually the first partition on NewWorld machines
197	NewWorld machines (Apple_partition_map) could not be deleted.	372	(Apple_partition_map) could not be deleted. If you would like to start with a
		373	clean disk, you can simply initialize the disk by pressing <c>i</c>. This
		374	will completely erase the disk, so use this with caution.
198	</p>	375	</p>
199		376
200	<p>	377	<p>
201	Second, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>. It will	378	Second, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>. It will
202	ask for what block you want to start. Enter the number of your first free	379	ask for what block you want to start. Enter the number of your first free
203	partition, followed by a <c>p</c>. For instance this is <c>2p</c>.	380	partition, followed by a <c>p</c>. For instance this is <c>2p</c>.
204	</p>	381	</p>
205		382
206	<note>	383	<note>
207	This partition is <e>not</e> a "boot" partition. It is not used by Linux at all;	384	This partition is <e>not</e> a <path>/boot</path> partition. It is not used by
208	you don't have to place any filesystem on it and you should never mount it. PPC	385	Linux at all; you don't have to place any filesystem on it and you should never
209	users don't need an extra partition for <path>/boot</path>.	386	mount it. Apple users don't need an extra partition for <path>/boot</path>.
210	</note>	387	</note>
211		388
212	<p>	389	<p>
213	Now create a swap partition by pressing <c>c</c>. Again <c>mac-fdisk</c> will	390	Now create a swap partition by pressing <c>c</c>. Again <c>mac-fdisk</c> will
214	ask for what block you want to start this partition from. As we used <c>2</c>	391	ask for what block you want to start this partition from. As we used <c>2</c>
215	before to create the Apple_Bootstrap partition, you now have to enter	392	before to create the Apple_Bootstrap partition, you now have to enter
216	<c>3p</c>. When you're asked for the size, enter <c>512M</c> (or whatever size	393	<c>3p</c>. When you're asked for the size, enter <c>512M</c> (or whatever size
217	you want -- 512MB is recommended though). When asked for a name, enter <c>swap</c>	394	you want -- a minimum of 512MB is recommended, but 2 times your physical memory
218	(mandatory).	395	is the generally accepted size). When asked for a name, enter <c>swap</c>.
219	</p>	396	</p>
220		397
221	<p>	398	<p>
222	To create the root partition, enter <c>c</c>, followed by <c>4p</c> to select	399	To create the root partition, enter <c>c</c>, followed by <c>4p</c> to select
223	from what block the root partition should start. When asked for the size, enter	400	from what block the root partition should start. When asked for the size, enter
224	<c>4p</c> again. <c>mac-fdisk</c> will interpret this as "Use all available	401	<c>4p</c> again. <c>mac-fdisk</c> will interpret this as "Use all available
225	space". When asked for the name, enter <c>root</c> (mandatory).	402	space". When asked for the name, enter <c>root</c>.
226	</p>	403	</p>
227		404
228	<p>	405	<p>
229	To finish up, write the partition to the disk using <c>w</c> and <c>q</c> to	406	To finish up, write the partition to the disk using <c>w</c> and <c>q</c> to
230	quit <c>mac-fdisk</c>.	407	quit <c>mac-fdisk</c>.
231	</p>	408	</p>
232		409
233	<note>	410	<note>
234	To make sure everything is ok, you should run mac-fdisk once more and check	411	To make sure everything is ok, you should run <c>mac-fdisk -l</c> and check
235	whether all the partitions are there. If you don't see any of the partitions	412	whether all the partitions are there. If you don't see any of the partitions
236	you created, or the changes you made, you should reinitialize your partitions	413	you created, or the changes you made, you should reinitialize your partitions
237	by pressing "i" in mac-fdisk. Note that this will recreate the partition map	414	by pressing "i" in mac-fdisk. Note that this will recreate the partition map
238	and thus remove all your partitions.	415	and thus remove all your partitions.
239	</note>	416	</note>
240		417
241	<p>	418	<p>
242	Now that your partitions are created, you can continue with <uri	419	Now that your partitions are created, you can continue with
243	link="#filesystems">Creating Filesystems</uri>.	420	<uri link="#filesystems">Creating Filesystems</uri>.
244	</p>	421	</p>
245		422
246	</body>	423	</body>
247	</section>	424	</section>
248	<section id="parted">	425	<section id="parted">
249	<title>Using parted (especially Pegasos) to Partition your Disk</title>	426	<title>Using parted to Partition your Disk (Pegasos and RS/6000)</title>
250	<body>	427	<body>
251		428
252	<p>	429	<p>
253	<c>parted</c>, the Partition Editor, can now handle HFS+ partitions used by	430	<c>parted</c>, the Partition Editor, can now handle HFS+ partitions used by
254	Mac OS and Mac OS X. With this tool you can shrink your Mac-partitions and	431	Mac OS and Mac OS X. With this tool you can resize your Mac-partitions and
255	create space for your Linux partitions. Nevertheless, the example below	432	create space for your Linux partitions. Nevertheless, the example below
256	describes partitioning for Pegasos machines only.	433	describes partitioning for Pegasos machines only.
257	</p>	434	</p>
258		435
259	<p>	436	<p>
…		…
263	<pre caption="Starting parted">	440	<pre caption="Starting parted">
264	# <i>parted /dev/hda</i>	441	# <i>parted /dev/hda</i>
265	</pre>	442	</pre>
266		443
267	<p>	444	<p>
268	If the drive is unpartitioned, run <c>mklabel amiga</c> to create a new	445	If the drive is unpartitioned, run <c>mklabel amiga</c> to create a new
269	disklabel for the drive.	446	disklabel for the drive.
270	</p>	447	</p>
271		448
272	<p>	449	<p>
273	You can type <c>print</c> at any time in parted to display the current partition	450	You can type <c>print</c> at any time in parted to display the current partition
274	table. Your changes aren't saved until you quit the application; if at any time	451	table. If at any time you change your mind or made a mistake you can press
275	you change your mind or made a mistake you can press <c>Ctrl-c</c> to abort	452	<c>Ctrl-c</c> to abort parted.
276	parted.
277	</p>	453	</p>
278		454
279	<p>	455	<p>
280	If you intend to also install MorphOS on your Pegasos create an affs1 filesystem	456	If you intend to also install MorphOS on your Pegasos create an affs1 filesystem
281	named "BI0" (BI zero) at the start of the drive. 50MB should be more than enough	457	at the start of the drive. 32MB should be more than enough to store the MorphOS
282	to store the MorphOS kernel. If you have a Pegasos I or intend to use reiserfs or	458	kernel. If you have a Pegasos I or intend to use any filesystem besides ext2 or
283	xfs, you will also have to store your Linux kernel on this partition (the	459	ext3, you will also have to store your Linux kernel on this partition (the
284	Pegasos II can boot from ext2/ext3 drives). To create the partition run	460	Pegasos II can only boot from ext2/ext3 or affs1 partitions). To create the
285	<c>mkpart primary affs1 START END</c> where <c>START</c> and <c>END</c> should	461	partition run <c>mkpart primary affs1 START END</c> where <c>START</c> and
286	be replaced with the megabyte range (e.g. <c>5 55</c> creates a 50 MB partition	462	<c>END</c> should be replaced with the megabyte range (e.g. <c>0 32</c>) which
287	starting at 5MB and ending at 55MB.	463	creates a 32 MB partition starting at 0MB and ending at 32MB. If you chose to
288	</p>	464	create an ext2 or ext3 partition instead, substitute ext2 or ext3 for affs1 in
289		465	the mkpart command.
290	<p>	466	</p>
291	You need to create two partitions for Linux, one root filesystem for all your	467
292	program files etc, and one swap partition. To create the root filesystem you
293	must first decide which filesystem to use. Possible options are ext2, ext3,
294	reiserfs and xfs. Unless you know what you are doing, use ext3. Run
295	<c>mkpart primary ext3 START END</c> to create an ext3 partition. Again, replace
296	<c>START</c> and <c>END</c> with the megabyte start and stop marks for the
297	partition.
298	</p>	468	<p>
299		469	You will need to create two partitions for Linux, one root filesystem and one
		470	swap partition. Run <c>mkpart primary START END</c> to create each partition,
		471	replacing <c>START</c> and <c>END</c> with the desired megabyte boundries.
300	<p>	472	</p>
		473
		474	<p>
301	It is generally recommended that you create a swap partition the same size as	475	It is generally recommended that you create a swap partition that is two times
302	the amount of RAM in your computer times two. You will probably get away with a	476	bigger than the amount of RAM in your computer, but at least 512Mb is
303	smaller swap partition unless you intend to run a lot of applications at the	477	recommended. To create the swap partition, run
304	same time (although at least 512MB is recommended). To create the swap	478	<c>mkpart primary linux-swap START END</c> with START and END again denoting
305	partition, run <c>mkpart primary linux-swap START END</c>.	479	the partition boundries.
306	</p>
307
308	<p>	480	</p>
309	Write down the partition minor numbers as they are required during the	481
310	installation process. To display the minor numbers run <c>print</c>. Your drives
311	are accessed as <path>/dev/hdaX</path> where X is replaced with the minor number
312	of the partition.
313	</p>	482	<p>
314
315	<p>
316	When you are done in parted simply run <c>quit</c>.	483	When you are done in parted simply type <c>quit</c>.
317	</p>	484	</p>
318		485
319	</body>	486	</body>
320	</section>	487	</section>
321	<section id="filesystems">	488	<section id="filesystems">
…		…
323	<subsection>	490	<subsection>
324	<title>Introduction</title>	491	<title>Introduction</title>
325	<body>	492	<body>
326		493
327	<p>	494	<p>
328	Now that your partitions are created, it is time to place a filesystem on them.	495	Now that your partitions are created, it is time to place a filesystem on them.
329	If you don't care about what filesystem to choose and are happy with what we use	496	If you're not sure which filesystems to choose and are happy with our defaults,
330	as default in this handbook, continue with <uri	497	continue with
331	link="#filesystems-apply">Applying a Filesystem to a Partition</uri>.	498	<uri link="#filesystems-apply">Applying a Filesystem to a Partition</uri>.
332	Otherwise read on to learn about the available filesystems...	499	Otherwise, read on to learn about the available filesystems.
333	</p>	500	</p>
334		501
335	</body>	502	</body>
336	</subsection>	503	</subsection>
337	<subsection>	504	<subsection>
338	<title>Filesystems?</title>	505	<title>Filesystems?</title>
339	<body>	506	<body>
340		507
341	<p>	508	<p>
342	Several filesystems are available. ext2, ext3, ReiserFS and XFS are found stable	509	Several filesystems are available for use on the PowerPC architecture including
343	on the PPC architecture. jfs is unsupported.	510	ext2, ext3, ReiserFS and XFS, each with their strengths and faults.
344	</p>	511	</p>
345		512
346	<p>	513	<p>
347	<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata	514	<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
348	journaling, which means that routine ext2 filesystem checks at startup time can	515	journaling, which means that routine ext2 filesystem checks at startup time can
349	be quite time-consuming. There is now quite a selection of newer-generation	516	be quite time-consuming. There is now quite a selection of journaled
350	journaled filesystems that can be checked for consistency very quickly and are	517	filesystems that can be checked for consistency very quickly and are thus
351	thus generally preferred over their non-journaled counterparts. Journaled	518	generally preferred over their non-journaled counterparts.
352	filesystems prevent long delays when you boot your system and your filesystem
353	happens to be in an inconsistent state.
354	</p>	519	</p>
355		520
356	<p>	521	<p>
357	<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata	522	<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
358	journaling for fast recovery in addition to other enhanced journaling modes like	523	journaling for fast recovery in addition to other enhanced journaling modes like
359	full data and ordered data journaling. ext3 is a very good and reliable	524	full data and ordered data journaling. It uses an HTree index that enables high
360	filesystem. It has an additional hashed b-tree indexing option that enables
361	high performance in almost all situations. In short, ext3 is an excellent	525	performance in almost all situations. In short, ext3 is a very good and reliable
362	filesystem.	526	filesystem.
363	</p>	527	</p>
364		528
365	<p>	529	<p>
366	<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall	530	<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall
367	performance and greatly outperforms both ext2 and ext3 when dealing with small	531	performance and greatly outperforms both ext2 and ext3 when dealing with small
368	files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales	532	files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales
369	extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is	533	extremely well and has metadata journaling. ReiserFS is solid and usable as
370	solid and usable as both general-purpose filesystem and for extreme cases such	534	both general-purpose filesystem and for extreme cases such as the creation of
371	as the creation of large filesystems, the use of many small files, very large	535	large filesystems, very large files and directories containing tens of
372	files and directories containing tens of thousands of files.	536	thousands of small files.
373	</p>	537	</p>
374		538
375	<p>	539	<p>
376	<b>XFS</b> is a filesystem with metadata journaling which comes with a robust	540	<b>XFS</b> is a filesystem with metadata journaling which comes with a robust
377	feature-set and is optimized for scalability. We only recommend using this	541	feature-set and is optimized for scalability. We only recommend using this
…		…
382	deal of data if the system goes down unexpectedly.	546	deal of data if the system goes down unexpectedly.
383	</p>	547	</p>
384		548
385	</body>	549	</body>
386	</subsection>	550	</subsection>
		551	<subsection>
		552	<title>Activating the Swap Partition</title>
		553	<body>
		554
		555	<p>
		556	<c>mkswap</c> is the command that is used to initialize swap partitions:
		557	</p>
		558
		559	<pre caption="Creating a swap signature">
		560	# <i>mkswap /dev/hda3</i>
		561	</pre>
		562
		563	<p>
		564	To activate the swap partition, use <c>swapon</c>:
		565	</p>
		566
		567	<pre caption="Activating the swap partition">
		568	# <i>swapon /dev/hda3</i>
		569	</pre>
		570
		571	<p>
		572	Create and activate the swap now before creating other filesystems.
		573	</p>
		574
		575	</body>
		576	</subsection>
387	<subsection id="filesystems-apply">	577	<subsection id="filesystems-apply">
388	<title>Applying a Filesystem to a Partition</title>	578	<title>Applying a Filesystem to a Partition</title>
389	<body>	579	<body>
390		580
391	<p>	581	<p>
…		…
415	<ti><c>mkfs.xfs</c></ti>	605	<ti><c>mkfs.xfs</c></ti>
416	</tr>	606	</tr>
417	</table>	607	</table>
418		608
419	<p>	609	<p>
420	For instance, to have the root partition (<path>/dev/hda4</path> in our example)	610	For instance, to make an ext3 filesystem on the root partition
421	in ext3 (as in our example), you would use:	611	(<path>/dev/hda4</path> in our example), you would use:
422	</p>	612	</p>
423		613
424	<pre caption="Applying a filesystem on a partition">	614	<pre caption="Applying a filesystem on a partition">
425	# <i>mke2fs -j /dev/hda4</i>	615	# <i>mke2fs -j /dev/hda4</i>
426	</pre>	616	</pre>
…		…
429	Now create the filesystems on your newly created partitions (or logical	619	Now create the filesystems on your newly created partitions (or logical
430	volumes).	620	volumes).
431	</p>	621	</p>
432		622
433	<note>	623	<note>
434	On OldWorld machines and the PegasosII your partition which holds the kernel must	624	On the PegasosII your partition which holds the kernel must be ext2, ext3 or
435	be ext2 or ext3. NewWorld machines can boot from any of ext2, ext3, XFS,	625	affs1. NewWorld machines can boot from any of ext2, ext3, XFS, ReiserFS or
436	ReiserFS or even HFS/HFS+ filesystems.	626	even HFS/HFS+ filesystems. On OldWorld machines booting with BootX, the kernel
		627	must be placed on an HFS partition, but this will be completed when you
		628	configure your bootloader.
437	</note>	629	</note>
438
439	</body>
440	</subsection>
441	<subsection>
442	<title>Activating the Swap Partition</title>
443	<body>
444
445	<p>
446	<c>mkswap</c> is the command that is used to initialize swap partitions:
447	</p>
448
449	<pre caption="Creating a Swap signature">
450	# <i>mkswap /dev/hda3</i>
451	</pre>
452
453	<p>
454	To activate the swap partition, use <c>swapon</c>:
455	</p>
456
457	<pre caption="Activating the swap partition">
458	# <i>swapon /dev/hda3</i>
459	</pre>
460
461	<p>
462	Create and activate the swap now.
463	</p>
464		630
465	</body>	631	</body>
466	</subsection>	632	</subsection>
467	</section>	633	</section>
468	<section>	634	<section>
469	<title>Mounting</title>	635	<title>Mounting</title>
470	<body>	636	<body>
471		637
472	<p>	638	<p>
473	Now that your partitions are initialized and are housing a filesystem, it is	639	Now that your partitions are initialized and are housing a filesystem, it is
474	time to mount those partitions. Use the <c>mount</c> command. Don't forget to	640	time to mount those partitions. Use the <c>mount</c> command. As an example we
475	create the necessary mount directories for every partition you created. As an	641	mount the root partition:
476	example we create a mount-point and mount the root partition:
477	</p>	642	</p>
478		643
479	<pre caption="Mounting partitions">	644	<pre caption="Mounting partitions">
480	# <i>mkdir /mnt/gentoo</i>
481	# <i>mount /dev/hda4 /mnt/gentoo</i>	645	# <i>mount /dev/hda4 /mnt/gentoo</i>
482	</pre>	646	</pre>
483		647
484	<note>	648	<note>
485	If you want your <path>/tmp</path> to reside on a separate partition, be sure to	649	If you want your <path>/tmp</path> to reside on a separate partition, be sure to
486	change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This	650	change its permissions after mounting and unpacking with
487	also holds for <path>/var/tmp</path>.	651	<c>chmod 1777 /mnt/gentoo/tmp</c>. This is also true for <path>/var/tmp</path>.
488	</note>	652	</note>
489
490	<p>
491	Finally we have to create the <path>/dev</path> files in our new home, which is
492	needed during the bootloader installation. This could be done by "bind"-mapping
493	the <path>/dev</path>-filesystem from the LiveCD:
494	</p>
495
496	<pre caption="Bind-mounting the /dev-filesystem">
497	# <i>mkdir /mnt/gentoo/dev</i>
498	# <i>mount -o bind /dev /mnt/gentoo/dev</i>
499	</pre>
500
501	<p>
502	We will also have to mount the proc filesystem (a virtual interface with the
503	kernel) on <path>/proc</path>. But first we will need to place our files on the
504	partitions.
505	</p>
506		653
507	<p>	654	<p>
508	Continue with <uri link="?part=1&chap=5">Installing the Gentoo	655	Continue with <uri link="?part=1&chap=5">Installing the Gentoo
509	Installation Files</uri>.	656	Installation Files</uri>.
510	</p>	657	</p>

 Legend:



Removed from v.1.23
 


changed lines


 
Added in v.1.43
 Legend:



Removed from v.1.23
 


changed lines


 
Added in v.1.43
-Removed from v.1.23
+Added in v.1.43

	ViewVC Help
Powered by ViewVC 1.1.13