/[gentoo]/xml/htdocs/doc/en/altinstall.xml
Gentoo

Contents of /xml/htdocs/doc/en/altinstall.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.74 - (show annotations) (download) (as text)
Wed Jan 9 20:36:44 2008 UTC (6 years, 10 months ago) by jkt
Branch: MAIN
Changes since 1.73: +5 -5 lines
File MIME type: application/xml
#205074, typo in file names

1 <?xml version='1.0' encoding="UTF-8"?>
2 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/altinstall.xml,v 1.73 2007/09/20 18:36:49 nightmorph Exp $ -->
3 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4
5 <guide link="/doc/en/altinstall.xml">
6
7 <title>The Gentoo Linux alternative installation method HOWTO</title>
8
9 <author title="Contributor">
10 <mail link="gerrynjr@gentoo.org">Gerald Normandin Jr.</mail>
11 </author>
12 <author title="Contributor">
13 <mail link="lordviram@rebelpacket.net">Travis Tilley</mail>
14 </author>
15 <author title="Contributor">
16 <mail link="volontir@yahoo.com">Oleg Raisky</mail>
17 </author>
18 <author title="Contributor">
19 <mail link="luminousit@hotmail.com">Alex Garbutt</mail>
20 </author>
21 <author title="Contributor">
22 <mail link="alex@openvs.com">Alexandre Georges</mail>
23 </author>
24 <author title="Contributor">
25 <mail link="vargen@b0d.org">Magnus Backanda</mail>
26 </author>
27 <author title="Contributor">
28 <mail link="davoid@gentoo.org">Faust A. Tanasescu</mail>
29 </author>
30 <author title="Contributor">
31 <mail link="aliz@gentoo.org">Daniel Ahlberg</mail>
32 </author>
33 <author title="Editor">
34 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
35 </author>
36 <author title="Reviewer">
37 Ken Nowack <!-- antifa@gentoo.org seems out -->
38 </author>
39 <author title="Editor">
40 <mail link="blubber@gentoo.org">Tiemo Kieft</mail>
41 </author>
42 <author title="Editor">
43 <mail link="bennyc@gentoo.org">Benny Chuang</mail>
44 </author>
45 <author title="Editor">
46 <mail link="smithj@gentoo.org">Jonathan Smith</mail>
47 </author>
48
49 <abstract>
50 This HOWTO is meant to be a repository of alternative Gentoo installation
51 methods, for those with special installation needs such as lack of a cdrom
52 or a computer that can't boot cds.
53 </abstract>
54
55 <!-- The content of this document is licensed under the CC-BY-SA license -->
56 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
57 <license/>
58
59 <version>0.73</version>
60 <date>2008-01-09</date>
61
62 <chapter>
63 <title>About this document</title>
64 <section>
65 <body>
66
67 <p>
68 If the standard boot-from-CD install method doesn't work for you (or you just
69 don't like it), help is now here. This document serves to provide a repository
70 of alternative Gentoo Linux installation techniques to those who need them.
71 Or, if you prefer, it serves as a place to put your wacky installation methods.
72 If you have an installation method that you yourself find useful, or you have
73 devised an amusing way of installing Gentoo, please don't hesitate to write
74 something up and post it on <uri link="http://bugs.gentoo.org">Bugzilla</uri>.
75 </p>
76
77 </body>
78 </section>
79 </chapter>
80
81 <chapter>
82 <title>Booting the Install CD with Smart BootManager</title>
83 <section>
84 <body>
85
86 <p>
87 Download Smart BootManager available from
88 <uri>http://btmgr.sourceforge.net/download.html</uri>.
89 Linux source or binary format and windows .exe versions are available as well
90 as many language packs. However, at this time, the preferred method would be to
91 use the binary format, as the source will not compile with newer versions of
92 NASM.
93 </p>
94
95 <p>
96 Either compile the package from source or just grab the binary. There are
97 several options that can be utilized while creating your boot floppy, as seen
98 below.
99 </p>
100
101 <pre caption="Smart BootManager Options">
102 sbminst [-t theme] [-d drv] [-b backup_file] [-u backup_file]
103
104 -t theme select the theme to be used, in which the theme could be:
105 us = English theme de = German theme
106 hu = Hungarian theme zh = Chinese theme
107 ru = Russian theme cz = Czech theme
108 es = Spanish theme fr = French theme
109 pt = Portuguese theme
110
111
112 -d drv set the drive that you want to install Smart BootManager on;
113 for Linux:
114 /dev/fd0 is the first floppy driver,
115 /dev/hda is the first IDE harddisk driver.
116 /dev/sda is the first SCSI harddisk driver.
117 for DOS:
118 0 is the first floppy drive
119 128 is the first hard drive;
120
121 -c disable CD-ROM booting feature;
122
123 -b backup_file backup the data that will be overwritten for
124 future uninstallation;
125
126 -u backup_file uninstall Smart BootManager, should be used alone;
127
128 -y do not ask any question or warning.
129 </pre>
130
131 <pre caption="Using sbminst to build the boot floppy">
132 # <i>sbminst -t us -d /dev/fd0</i>
133 </pre>
134
135 <note>
136 Replace <path>fd0</path> with your respective floppy device name if yours is different.
137 </note>
138
139 <p>
140 Now simply place the floppy in the floppy drive of the computer you'd like to
141 boot the Install CD on, as well as placing the Install CD in the CD-ROM and boot
142 the computer.
143 </p>
144
145 <p>
146 You'll be greeted with the Smart BootManager dialog. Select your CD-ROM and
147 press ENTER to boot the Install CD. Once booted proceed with the standard
148 installation instructions.
149 </p>
150
151 <p>
152 Further information on Smart BootManager may be found at
153 <uri>http://btmgr.sourceforge.net/</uri>
154 </p>
155
156 </body>
157 </section>
158 </chapter>
159
160 <chapter>
161 <title>Knoppix Installation</title>
162 <section>
163 <body>
164
165 <note>
166 Knoppix is only available for x86 users.
167 </note>
168
169 <!-- this works with knoppix 3.6+ and gentoo 2004.3, 2005.0-->
170
171 <p>
172 Booting from the <uri link="http://www.knoppix.org/">Knoppix</uri> LiveCD is a
173 way to have a fully functional system while you're compiling Gentoo. Tux Racer
174 will help you pass the time while you wait, and you can use OpenOffice for
175 work.
176 </p>
177
178 <warn>
179 Be aware that if you save anything in Knoppix's home directory while waiting
180 for your Gentoo system to install, it will not be available when you reboot
181 into Gentoo. Be sure to save important files on the hard disk or on some other
182 computer!
183 </warn>
184
185 <p>
186 Boot from the Knoppix CD. If you have Knoppix 3.6-3.8.2, you will need to
187 specify <c>knoppix26</c> as a boot option to load a 2.6 kernel. If you miss
188 this step, when you <c>chroot</c>, you will recieve an error saying that your
189 kernel is too old. If, however, you have Knoppix 3.9+, this step is
190 unnecessary, since the 2.6 kernel is default.
191 </p>
192
193 <p>
194 By default Knoppix boots into a KDE desktop. Open a <c>konsole</c> and <c>su -</c>
195 so you can change your password. This lets you set the root password for
196 Knoppix. You can now configure <c>sshd</c> for remote login, at your
197 preference.
198 </p>
199
200 <pre caption="Creating the /mnt/gentoo mountpoint">
201 # <i>mkdir /mnt/gentoo</i>
202 </pre>
203
204 <p>
205 At this point, you can pick up with the standard install documentation at <uri
206 link="/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=4">part 4</uri>.
207 However, when you are asked to mount the proc system, issue the following
208 command instead:
209 </p>
210
211 <pre caption="Bind-mounting the proc pseudo filesystem">
212 # <i>mount -o bind /proc /mnt/gentoo/proc</i>
213 </pre>
214
215 <p>
216 Also, know that some of Portage's FEATURES will not work in knoppix. Especially
217 watch out for <c>userpriv</c> and <c>usersandbox</c>. If you find yourself
218 getting errors, it might be wise to disable some or all of the optional
219 features.
220 </p>
221
222 <!--
223 Commenting out due to #78716. If it needs to be restated again, note
224 that some will require to bind-mount it, others don't, and that you have
225 a 50-50 chance of winning the gold strike.
226
227
228 <p>
229 You will also need to bind-mount the device tree to resolve permission issues
230 with various device files.
231 </p>
232
233 < ! - -
234 If this doesn't seem to work, #71901 mentions the following command:
235 mount -o remount,rw,nosuid /dev/hd* /mnt/hd*
236 before all. Looks weird to me, but if this doesn't work, we might want to try
237 that.
238 - - >
239
240 <pre caption="Bind-mounting the device tree">
241 # <i>mount -o bind /dev /mnt/gentoo/dev</i>
242 </pre>
243 -->
244
245 </body>
246 </section>
247 </chapter>
248
249 <chapter>
250 <title>Diskless install using PXE boot</title>
251 <section>
252 <title>Requirements</title>
253 <body>
254
255 <p>
256 You will need a network card on the diskless client that uses the PXE protocol
257 to boot, like many 3com cards. You will also need a BIOS that supports booting
258 from PXE.
259 </p>
260
261 </body>
262 </section>
263 <section>
264 <title>Server base setup</title>
265 <body>
266
267 <p>
268 Create directories: The first thing to do is to create the directories where
269 your diskless system will be stored. Create a directory called
270 <path>/diskless</path> which houses a directory for each diskless client. For
271 the rest of this howto we'll be working on the client 'eta'.
272 </p>
273
274 <pre caption="Directory setup">
275 # <i>mkdir /diskless</i>
276 # <i>mkdir /diskless/eta</i>
277 # <i>mkdir /diskless/eta/boot</i>
278 </pre>
279
280 <p>
281 DHCP and TFTP setup: The client will get boot informations using DHCP and
282 download all the required files using TFTP. Just emerge DHCP and configure it
283 for your basic needs. Then, add the following on
284 <path>/etc/dhcp/dhcpd.conf</path>.
285 </p>
286
287 <note>
288 This provide a static IP address for the client and the path of a PXE boot
289 image, here <path>pxegrub</path>. You have to replace the MAC address of the Ethernet card
290 of the client and the directory where you will put the client files with the
291 one you use.
292 </note>
293
294 <p>
295 For DHCPd, run <c>emerge dhcp</c> (or any other DHCP server of your choice).
296 Make sure that the correct interface is selected in
297 <path>/etc/conf.d/dhcpd</path>.
298 </p>
299
300 <pre caption="dhcpd.conf">
301 option option-150 code 150 = text ;
302 ddns-update-style none ;
303 host eta {
304 hardware ethernet 00:00:00:00:00:00;
305 fixed-address <i>ip.add.re.ss</i>;
306 option option-150 "/eta/boot/grub.lst";
307 filename "/eta/boot/pxegrub";
308 }
309 </pre>
310
311 <p>
312 Next you'll need to configure your interface in <path>/etc/conf.d/net</path> so
313 that it doesn't get cleared at bootup. See <path>/etc/conf.d/net.example</path>
314 for more information.
315 </p>
316
317 <pre caption="/etc/conf.d/net">
318 <comment>(Replace eth0 with the correct interface)</comment>
319 config_eth0=( "noop" )
320 </pre>
321
322 <p>
323 For TFTP, emerge <c>app-admin/tftp-hpa</c>. In
324 <path>/etc/conf.d/in.tftpd</path>, put the following :
325 </p>
326
327 <pre caption="in.tftpd">
328 INTFTPD_PATH="/diskless"
329 INTFTPD_USER="nobody"
330 INTFTPD_OPTS="-u ${INTFTPD_USER} -l -vvvvvv -p -c -s ${INTFTPD_PATH}"
331 </pre>
332
333 <p>
334 Setup GRUB: To provide PXE booting I use GRUB with the <c>netboot</c> USE flag
335 enabled. Once GRUB is compiled, copy the PXE image to the diskless client's
336 boot directory. Then edit its <path>grub.lst</path> config file.
337 </p>
338
339 <pre caption="Grub setup">
340 # <i>echo "sys-boot/grub netboot" &gt;&gt; /etc/portage/package.use</i>
341 # <i>emerge -av grub</i>
342 # <i>cp /usr/lib/grub/pxegrub /diskless/eta/boot/pxegrub</i>
343 # <i>nano -w /diskless/eta/boot/grub.lst</i>
344 </pre>
345
346 <pre caption="grub.lst">
347 default 0
348 timeout 30
349
350 title=Diskless Gentoo
351 root (nd)
352 kernel /eta/bzImage ip=dhcp root=/dev/nfs nfsroot=<i>ip.add.re.ss</i>:/diskless/eta
353
354 <comment># For the nfsroot option, the IP address is the one of the server and
355 the directory is the one where your diskless client files are located (on the server).</comment>
356 </pre>
357
358 <p>
359 Setup NFS: NFS is quite easy to configure. The only thing you have to do is to
360 add a line on the <path>/etc/exports</path> config file:
361 </p>
362
363 <pre caption="/etc/exports">
364 # <i>nano -w /etc/exports</i>
365 # /etc/exports: NFS file systems being exported. See exports(5).
366 /diskless/eta eta(rw,sync,no_root_squash)
367 </pre>
368
369 <p>
370 Update your hosts: One important thing to do now is to modify your
371 <path>/etc/hosts</path> file to fit your needs.
372 </p>
373
374 <pre caption="/etc/hosts">
375 127.0.0.1 localhost
376
377 192.168.1.10 eta.example.com eta
378 192.168.1.20 sigma.example.com sigma
379 </pre>
380
381 </body>
382 </section>
383 <section>
384 <title>Creating the system on the server</title>
385 <body>
386
387 <p>
388 You might want to reboot the server with a Gentoo Install CD, although you can
389 very well continue immediately if you know how to proceed with the Gentoo
390 Installation Instructions from an existing installation. Follow the standard
391 install procedure as explained in the <uri link="/doc/en/handbook/">Gentoo Handbook</uri> BUT with the
392 following differences:
393 When you mount the file system, do the following (where <path>hdaX</path> is the partition
394 where you created the <path>/diskless</path> directory). You do not need to mount any other
395 partitions as all of the files will reside in the <path>/diskless/eta</path>
396 directory.
397 </p>
398
399 <pre caption="Mounting the filesystem">
400 #<i> mount /dev/hdaX /mnt/gentoo</i>
401 </pre>
402
403 <p>
404 Stage tarballs and chroot: This example uses a stage3 tarball. Mount
405 <path>/proc</path> to your diskless directory and chroot into it to continue
406 with the install. Then follow the installation manual until kernel
407 configuration.
408 </p>
409
410 <warn>
411 Be very careful where you extract your stage tarball. You don't want to end up
412 extracting over your existing installation.
413 </warn>
414
415 <pre caption="Extracting the stage tarball">
416 # <i>cd /mnt/gentoo/diskless/eta/</i>
417 # <i>tar -xvjpf /mnt/cdrom/gentoo/stage3-*.tar.bz2</i>
418 # <i>mount -t proc /proc /mnt/gentoo/diskless/eta/proc</i>
419 # <i>cp /etc/resolv.conf /mnt/gentoo/diskless/eta/etc/resolv.conf</i>
420 # <i>chroot /mnt/gentoo/diskless/eta/ /bin/bash</i>
421 # <i>env-update</i>
422 # <i>source /etc/profile</i>
423 </pre>
424
425 <p>
426 Kernel configuration: When you do the <c>make menuconfig</c> of your kernel
427 configuration, don't forget to enable the following options with the others
428 recommended into the install howto.
429 </p>
430
431 <pre caption="menuconfig options">
432 - Your network card device support
433 <comment>(In the kernel, *not* as a module!)</comment>
434
435 - Under "Networking options" :
436
437 [*] TCP/IP networking
438 [*] IP: kernel level autoconfiguration
439 [*] IP: DHCP support
440 [*] IP: BOOTP support
441
442
443 - Under "File systems --> Network File Systems" :
444
445 &lt;*&gt; NFS file system support
446 [*] Provide NFSv3 client support
447 [*] Root file system on NFS
448 </pre>
449
450 <p>
451 Save the kernel in your chrooted <path>/</path> (not in <path>/boot</path>)
452 according to the pxegrub setting defined earlier. Next configure your
453 diskless client's <path>/etc/fstab</path>.
454 </p>
455
456 <pre caption="/etc/fstab">
457 # <i>nano -w /etc/fstab</i>
458 /dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0
459 proc /proc proc defaults 0 0
460 tmpfs /dev/shm tmpfs nodev,nosuid,noexec 0 0
461 </pre>
462
463 <p>
464 You also need to prevent the client to run a filesystem check:
465 </p>
466
467 <pre caption="Preventing the client to run a filesystem check">
468 # <i>touch /fastboot</i>
469 # <i>echo "touch /fastboot" &gt;&gt; /etc/conf.d/local.start</i>
470 </pre>
471
472 <p>
473 Install <c>nfs-utils</c> since your client will heavily depend on it:
474 </p>
475
476 <pre caption="Installing nfs-utils">
477 # <i>emerge nfs-utils</i>
478 </pre>
479
480 <p>
481 Bootloader. Don't install another bootloader because we already have one -
482 pxegrub. Simply finish the install and restart the server. Start the services
483 you'll need to boot the new client: DHCP, TFTPD, and NFS.
484 </p>
485
486 <pre caption="Starting services">
487 # <i>/etc/init.d/dhcp start</i>
488 # <i>/etc/init.d/in.tftpd start</i>
489 # <i>/etc/init.d/nfs start</i>
490 </pre>
491
492 </body>
493 </section>
494 <section>
495 <title>Booting the new client</title>
496 <body>
497
498 <p>
499 For the new client to boot properly, you'll need to configure the bios and the
500 network card to use PXE as the first boot method - before CD-ROM or floppy. For
501 help with this consult your hardware manuals or manufacturers website. The
502 network card should get an IP address using DHCP and download the GRUB PXE
503 image using TFTP. Then, you should see a nice black and white GRUB bootmenu
504 where you will select the kernel to boot and press Enter. If everything is ok
505 the kernel should boot, mount the root filesystem using NFS and provide you
506 with a login prompt. Enjoy.
507 </p>
508
509 </body>
510 </section>
511 </chapter>
512
513 <chapter>
514 <title>Installing Gentoo from an existing Linux distribution</title>
515 <section>
516 <title>Requirements</title>
517 <body>
518
519 <p>
520 In order to install Gentoo from your existing Linux distribution you need to
521 have chroot command installed, and have a copy of the Gentoo installation
522 tarball or ISO you want to install. A network connection would be preferable if
523 you want more than what's supplied in your tarball. (by the way, a tarball is
524 just a file ending in .tbz or .tar.gz). The author used RedHat Linux 7.3 as the
525 "host" operating system, but it is not very important. Let's get started!
526 </p>
527
528 </body>
529 </section>
530 <section>
531 <title>Overview</title>
532 <body>
533
534 <p>
535 We will first allocate a partition to Gentoo by resizing our existing Linux
536 partition, mount the partition, untar the tarball to the partition that is mounted, chroot
537 inside the pseudo-system and start building. Once the bootstrap process is
538 done, we will do some final configuration on the system so as to make sure it
539 boots, then we are ready to reboot and use Gentoo.
540 </p>
541
542 </body>
543 </section>
544 <section>
545 <title>How should we make space for Gentoo?</title>
546 <body>
547
548 <p>
549 The root partition is the filesystem mounted under <path>/</path>. A quick run
550 of <c>mount</c> on my system shows what I am talking about. We well also use <c>df</c> (disk
551 free) to see how much space I have left and how I will be resizing. Note that
552 it is not mandatory to resize your root partition! You could be resizing
553 anything else supported by our resizer, but let's talk about that later.
554 </p>
555
556 <pre caption="Filesystem information">
557 # <i>mount</i>
558 /dev/hdb2 on / type ext3 (rw)
559 none on /proc type proc (rw)
560 none on /dev/pts type devpts (rw,gid=5,mode=620)
561 none on /dev/shm type tmpfs (rw,nodev,nosuid,noexec)
562 # <i>df -h </i>
563 Filesystem Size Used Avail Use% Mounted on
564 /dev/hdb2 4.0G 1.9G 2.4G 82% /
565 none 38M 0 38M 0% /dev/shm
566 </pre>
567
568 <p>
569 As we can see, the partition mounted as <path>/</path> named
570 <path>/dev/hdb2</path> has 2.4 gigabytes free. In my case, I think I will
571 resize it as to leave 400Megs free of space, therefore allocating 2 gigabytes
572 for Gentoo. Not bad, I could have quite some stuff installed. However, I think
573 that even one gigabyte is enough for most users. So let's partition this thing!
574 </p>
575
576 </body>
577 </section>
578 <section>
579 <title>Building parted to resize partition</title>
580 <body>
581
582 <p>
583 Parted is an utility supplied by the GNU foundation, an old and respectable
584 huge project whose software you are using in this very moment. There is one
585 tool, however, that is extremely useful for us at the moment. It's called
586 parted, partition editor and we can get it from
587 <uri>http://www.gnu.org/software/parted/</uri>
588 </p>
589
590 <note>
591 There are other tools for doing resize of partitions as well, but the author is
592 unsure/uninterested whether PartitionMagic(tm) or other software of the kind do
593 the job. It's the reader's job to check them out
594 </note>
595
596 <p>
597 Look up on that page the type of filesystem you want to resize and see if
598 parted can do it. If not, you're out of luck, you will have to destroy some
599 partition to make space for Gentoo, and reinstall back. Go ahead by downloading
600 the software, install it. Here we have a problem. We want to resize our Linux
601 root partition, therefore we must boot from a floppy disk a minimal linux
602 system and use previously-compiled parted copied to a diskette in order to
603 resize <path>/</path>. However, if you can unmount the partition while still
604 in Linux you are lucky, you don't need to do what follows. Just compile parted
605 and run it on an unmounted partition you chose to resize. Here's how I did it
606 for my system.
607 </p>
608
609 <impo>
610 Make sure that the operations you want to do on your partition are supported by
611 parted!
612 </impo>
613
614 <p>
615 Get the mininux boot/root disk (a 2.4-powered mini Linux distribution on a
616 floppy - free of charge) from <uri>http://mininux.free.fr/uk/</uri>, create a
617 floppy as suggested in the Documentation that accompanies the software package
618 and insert a new floppy in the drive for the next step.
619 </p>
620
621 <note>
622 Note again that Linux is synonym of "There's one more way to do it". Your
623 objective is to run parted on an unmounted partition so it can do its work. You
624 might use some boot/root diskset other than mininux. You might not even
625 need to do this step at all, ie. you might only have umount the filesystem you want to
626 repartition in your Linux session and run parted on it.
627 </note>
628
629 <pre caption="Utility disk creation">
630 # <i>mkfs.minix /dev/fd0</i>
631 480 inodes
632 1440 blocks
633 Firstdatazone=19 (19)
634 Zonesize=1024
635 Maxsize=268966912
636 </pre>
637
638 <p>
639 We will now proceed with the build of parted. If it's not already downloaded
640 and untarred, do so now and <c>cd</c> into the corresponding directory. Now run the
641 following set of commands to build the utility and copy it to your floppy disk.
642 </p>
643
644 <pre caption="Building the utility floppy">
645 # <i> mkdir /floppy; mount -t minix /dev/fd0 /floppy &amp;&amp;
646 export CFLAGS="-O3 -pipe -fomit-frame-pointer -static" &amp;&amp; ./configure
647 &amp;&amp; make &amp;&amp; cp parted/parted /floppy &amp;&amp; umount /floppy </i>
648 </pre>
649
650 <p>
651 Congratulations, you are ready to reboot and resize your partition. Do this
652 only after taking a quick look at the parted documentation on the GNU website.
653 The resize should take under 30 minutes for the largest hard-drives, be
654 patient. Reboot your system with the mininux boot disk (just pop it inside),
655 and once you are logged in, switch the disk in the drive with your utility disk
656 we have created above and type <c>mount /dev/fd0 /floppy</c> to have parted under
657 <path>/floppy</path>. There you go. Run parted and you will be able to resize your
658 partition. Once this lenghty process done, we are ready to have the real fun,
659 by installing Gentoo. Reboot back into your old Linux system for now. The drive you
660 wish to operate on is the drive containing the partition we want to resize. For
661 example, if we want to resize /dev/hda3, the drive is /dev/hda
662 </p>
663
664 <pre caption="Commands to run once logged into mininux system">
665 # <i>mount /dev/fd0 /floppy </i>
666 # <i>cd /floppy; ./parted [drive you wish to operate on]</i>
667 (parted) <i> print </i>
668 Disk geometry for /dev/hdb: 0.000-9787.148 megabytes
669 Disk label type: msdos
670 Minor Start End Type Filesystem Flags
671 1 0.031 2953.125 primary ntfs
672 3 2953.125 3133.265 primary linux-swap
673 2 3133.266 5633.085 primary ext3
674 4 5633.086 9787.148 extended
675 5 5633.117 6633.210 logical
676 6 6633.242 9787.148 logical ext3
677 (parted) <i> help resize </i>
678 resize MINOR START END resize filesystem on partition MINOR
679
680 MINOR is the partition number used by Linux. On msdos disk labels, the
681 primary partitions number from 1-4, and logical partitions are 5
682 onwards.
683 START and END are in megabytes
684 (parted) <i> resize 2 3133.266 4000.000 </i>
685 </pre>
686
687 <impo>
688 Be patient! The computer is working! Just look at the harddrive LED on your case
689 to see that it is really working. This should take between 2 and 30 minutes.
690 </impo>
691
692 <p>
693 Once you have resized, boot back into your old linux as described. Then go to
694 <uri link="/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=4">The Gentoo
695 Handbook: Preparing the Disks</uri> and follow the instructions. When
696 chrooting, use the following command to flush your environment:
697 </p>
698
699 <pre caption="Flushing the environment during chroot">
700 # <i>env -i HOME=$HOME TERM=$TERM chroot /mnt/gentoo /bin/bash</i>
701 # <i>/usr/sbin/env-update</i>
702 # <i>source /etc/profile</i>
703 </pre>
704
705 <p>
706 Enjoy!
707 </p>
708
709 </body>
710 </section>
711 </chapter>
712 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20