/[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.46 - (show annotations) (download) (as text)
Wed Dec 22 22:18:46 2004 UTC (9 years, 7 months ago) by swift
Branch: MAIN
Changes since 1.45: +9 -2 lines
File MIME type: application/xml
#75212 - Updates for PXE stuff

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

  ViewVC Help
Powered by ViewVC 1.1.20