swift 08/05/23 20:29:44 Modified: altinstall.xml Log: Coding style
Revision Changes Path 1.75 xml/htdocs/doc/en/altinstall.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/altinstall.xml?rev=1.75&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/altinstall.xml?rev=1.75&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/altinstall.xml?r1=1.74&r2=1.75 Index: altinstall.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/altinstall.xml,v retrieving revision 1.74 retrieving revision 1.75 diff -u -r1.74 -r1.75 --- altinstall.xml 9 Jan 2008 20:36:44 -0000 1.74 +++ altinstall.xml 23 May 2008 20:29:44 -0000 1.75 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/altinstall.xml,v 1.74 2008/01/09 20:36:44 jkt Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/altinstall.xml,v 1.75 2008/05/23 20:29:44 swift Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link="/doc/en/altinstall.xml"> @@ -84,7 +84,7 @@ <body> <p> -Download Smart BootManager available from +Download Smart BootManager available from <uri>http://btmgr.sourceforge.net/download.html</uri>. Linux source or binary format and windows .exe versions are available as well as many language packs. However, at this time, the preferred method would be to @@ -102,16 +102,16 @@ sbminst [-t theme] [-d drv] [-b backup_file] [-u backup_file] -t theme select the theme to be used, in which the theme could be: - us = English theme de = German theme - hu = Hungarian theme zh = Chinese theme + us = English theme de = German theme + hu = Hungarian theme zh = Chinese theme ru = Russian theme cz = Czech theme - es = Spanish theme fr = French theme - pt = Portuguese theme + es = Spanish theme fr = French theme + pt = Portuguese theme + - -d drv set the drive that you want to install Smart BootManager on; for Linux: - /dev/fd0 is the first floppy driver, + /dev/fd0 is the first floppy driver, /dev/hda is the first IDE harddisk driver. /dev/sda is the first SCSI harddisk driver. for DOS: @@ -133,7 +133,8 @@ </pre> <note> -Replace <path>fd0</path> with your respective floppy device name if yours is different. +Replace <path>fd0</path> with your respective floppy device name if yours is +different. </note> <p> @@ -163,7 +164,7 @@ <body> <note> -Knoppix is only available for x86 users. +Knoppix is only available for x86 users. </note> <!-- this works with knoppix 3.6+ and gentoo 2004.3, 2005.0--> @@ -191,8 +192,8 @@ </p> <p> -By default Knoppix boots into a KDE desktop. Open a <c>konsole</c> and <c>su -</c> -so you can change your password. This lets you set the root password for +By default Knoppix boots into a KDE desktop. Open a <c>konsole</c> and <c>su +-</c> so you can change your password. This lets you set the root password for Knoppix. You can now configure <c>sshd</c> for remote login, at your preference. </p> @@ -219,11 +220,11 @@ features. </p> -<!-- +<!-- Commenting out due to #78716. If it needs to be restated again, note that some will require to bind-mount it, others don't, and that you have a 50-50 chance of winning the gold strike. - + <p> You will also need to bind-mount the device tree to resolve permission issues @@ -286,9 +287,9 @@ <note> This provide a static IP address for the client and the path of a PXE boot -image, here <path>pxegrub</path>. You have to replace the MAC address of the Ethernet card -of the client and the directory where you will put the client files with the -one you use. +image, here <path>pxegrub</path>. You have to replace the MAC address of the +Ethernet card of the client and the directory where you will put the client +files with the one you use. </note> <p> @@ -385,15 +386,15 @@ <body> <p> -You might want to reboot the server with a Gentoo Install CD, although you can -very well continue immediately if you know how to proceed with the Gentoo -Installation Instructions from an existing installation. Follow the standard -install procedure as explained in the <uri link="/doc/en/handbook/">Gentoo Handbook</uri> BUT with the -following differences: -When you mount the file system, do the following (where <path>hdaX</path> is the partition -where you created the <path>/diskless</path> directory). You do not need to mount any other -partitions as all of the files will reside in the <path>/diskless/eta</path> -directory. +You might want to reboot the server with a Gentoo Install CD, although you can +very well continue immediately if you know how to proceed with the Gentoo +Installation Instructions from an existing installation. Follow the standard +install procedure as explained in the <uri link="/doc/en/handbook/">Gentoo +Handbook</uri> BUT with the following differences: +When you mount the file system, do the following (where <path>hdaX</path> is +the partition where you created the <path>/diskless</path> directory). You do +not need to mount any other partitions as all of the files will reside in the +<path>/diskless/eta</path> directory. </p> <pre caption="Mounting the filesystem"> @@ -449,7 +450,7 @@ <p> Save the kernel in your chrooted <path>/</path> (not in <path>/boot</path>) -according to the pxegrub setting defined earlier. Next configure your +according to the pxegrub setting defined earlier. Next configure your diskless client's <path>/etc/fstab</path>. </p> @@ -511,7 +512,7 @@ </chapter> <chapter> -<title>Installing Gentoo from an existing Linux distribution</title> +<title>Installing Gentoo from an existing Linux distribution</title> <section> <title>Requirements</title> <body> @@ -533,10 +534,10 @@ <p> We will first allocate a partition to Gentoo by resizing our existing Linux -partition, mount the partition, untar the tarball to the partition that is mounted, chroot -inside the pseudo-system and start building. Once the bootstrap process is -done, we will do some final configuration on the system so as to make sure it -boots, then we are ready to reboot and use Gentoo. +partition, mount the partition, untar the tarball to the partition that is +mounted, chroot inside the pseudo-system and start building. Once the bootstrap +process is done, we will do some final configuration on the system so as to +make sure it boots, then we are ready to reboot and use Gentoo. </p> </body> @@ -547,10 +548,11 @@ <p> The root partition is the filesystem mounted under <path>/</path>. A quick run -of <c>mount</c> on my system shows what I am talking about. We well also use <c>df</c> (disk -free) to see how much space I have left and how I will be resizing. Note that -it is not mandatory to resize your root partition! You could be resizing -anything else supported by our resizer, but let's talk about that later. +of <c>mount</c> on my system shows what I am talking about. We well also use +<c>df</c> (disk free) to see how much space I have left and how I will be +resizing. Note that it is not mandatory to resize your root partition! You +could be resizing anything else supported by our resizer, but let's talk about +that later. </p> <pre caption="Filesystem information"> @@ -560,9 +562,9 @@ none on /dev/pts type devpts (rw,gid=5,mode=620) none on /dev/shm type tmpfs (rw,nodev,nosuid,noexec) # <i>df -h </i> -Filesystem Size Used Avail Use% Mounted on +Filesystem Size Used Avail Use% Mounted on /dev/hdb2 4.0G 1.9G 2.4G 82% / -none 38M 0 38M 0% /dev/shm +none 38M 0 38M 0% /dev/shm </pre> <p> @@ -576,7 +578,7 @@ </body> </section> <section> -<title>Building parted to resize partition</title> +<title>Building parted to resize partition</title> <body> <p> @@ -590,10 +592,10 @@ <note> There are other tools for doing resize of partitions as well, but the author is unsure/uninterested whether PartitionMagic(tm) or other software of the kind do -the job. It's the reader's job to check them out +the job. It's the reader's job to check them out </note> -<p> +<p> Look up on that page the type of filesystem you want to resize and see if parted can do it. If not, you're out of luck, you will have to destroy some partition to make space for Gentoo, and reinstall back. Go ahead by downloading @@ -622,8 +624,8 @@ Note again that Linux is synonym of "There's one more way to do it". Your objective is to run parted on an unmounted partition so it can do its work. You might use some boot/root diskset other than mininux. You might not even -need to do this step at all, ie. you might only have umount the filesystem you want to -repartition in your Linux session and run parted on it. +need to do this step at all, ie. you might only have umount the filesystem you +want to repartition in your Linux session and run parted on it. </note> <pre caption="Utility disk creation"> @@ -637,13 +639,14 @@ <p> We will now proceed with the build of parted. If it's not already downloaded -and untarred, do so now and <c>cd</c> into the corresponding directory. Now run the -following set of commands to build the utility and copy it to your floppy disk. +and untarred, do so now and <c>cd</c> into the corresponding directory. Now run +the following set of commands to build the utility and copy it to your floppy +disk. </p> <pre caption="Building the utility floppy"> -# <i> mkdir /floppy; mount -t minix /dev/fd0 /floppy && -export CFLAGS="-O3 -pipe -fomit-frame-pointer -static" && ./configure +# <i> mkdir /floppy; mount -t minix /dev/fd0 /floppy && +export CFLAGS="-O3 -pipe -fomit-frame-pointer -static" && ./configure && make && cp parted/parted /floppy && umount /floppy </i> </pre> @@ -653,12 +656,12 @@ The resize should take under 30 minutes for the largest hard-drives, be patient. Reboot your system with the mininux boot disk (just pop it inside), and once you are logged in, switch the disk in the drive with your utility disk -we have created above and type <c>mount /dev/fd0 /floppy</c> to have parted under -<path>/floppy</path>. There you go. Run parted and you will be able to resize your -partition. Once this lenghty process done, we are ready to have the real fun, -by installing Gentoo. Reboot back into your old Linux system for now. The drive you -wish to operate on is the drive containing the partition we want to resize. For -example, if we want to resize /dev/hda3, the drive is /dev/hda +we have created above and type <c>mount /dev/fd0 /floppy</c> to have parted +under <path>/floppy</path>. There you go. Run parted and you will be able to +resize your partition. Once this lenghty process done, we are ready to have the +real fun, by installing Gentoo. Reboot back into your old Linux system for now. +The drive you wish to operate on is the drive containing the partition we want +to resize. For example, if we want to resize /dev/hda3, the drive is /dev/hda. </p> <pre caption="Commands to run once logged into mininux system"> @@ -668,12 +671,12 @@ Disk geometry for /dev/hdb: 0.000-9787.148 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags -1 0.031 2953.125 primary ntfs -3 2953.125 3133.265 primary linux-swap -2 3133.266 5633.085 primary ext3 -4 5633.086 9787.148 extended -5 5633.117 6633.210 logical -6 6633.242 9787.148 logical ext3 +1 0.031 2953.125 primary ntfs +3 2953.125 3133.265 primary linux-swap +2 3133.266 5633.085 primary ext3 +4 5633.086 9787.148 extended +5 5633.117 6633.210 logical +6 6633.242 9787.148 logical ext3 (parted) <i> help resize </i> resize MINOR START END resize filesystem on partition MINOR -- [email protected] mailing list
