| View previous topic :: View next topic |
| Author |
Message |
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
 Posted: Thu Nov 10, 2005 1:18 am Post subject: Stage 1/3 Installation Guide for Gentoo 2005.1 & GCC 3.4 |
 |
|
... Imitated but Never Duplicated...
Stage 1/3 Installation for Gentoo 2005.1 and GCC 3.4.4 / GCC 3.4.5
This Installation Guide is no longer being maintained on this site. To view the most current revision of this Guide, >>Click Here<<.
This thread is a Maintenance Update to the now-famous series of Stage 1/3 Installation Guides for Gentoo Linux. This edition of the Guide supercedes the what is now the penultimate version of the Guide, the Stage 1/3 Installation for Gentoo 2005.0 and GCC 3.4.4. Please be sure to look at the older versions of the Guide and look at the credits!
The Official Support Thread for the Stage 1/3 Guide for GCC 3.4.4 is located >> here. <<
Effective 2005-12-31 the text of this Guide remains correct for GCC 3.4.4 testing branch ebuilds, while the PDF version of this Guide has been updated for GCC 3.4.5.
Faster than a Speeding Bullet...
More Powerful than a Locomotive!
and STABLE as ROCK!
How To Build a Fast and Bulletproof Gentoo System -- Stage 1 NPTL Installation on a Stage 3 Tarball Using GCC 3.4.4
Copyright (c) 2005 Bob P and The Jackass! Project. Released under the Creative Commons Attribution-ShareAlike license version 2.0. If you base a derivative work on this Guide, you MUST give credit to the Author in your document, and your document must contain a hyperlink that points to This URL. If you paraphrase sections of this Guide, no further attribution is required. OTOH, if you quote sections of this Guide, you must either: a) identify the quoted sections as quotes, with full citations of authorship and a hyperlink to this web page, or b) provide me with co-authorship status as a secondary author on your work.
Background
The Stage 1/3 Installation Method was developed for Gentoo 2004.3 because at that time any Gentoo installation that was performed with anything other than a Stage 3 tarball suffered from two problems: Circular dependencies within the base system, and the potential to leave behind unwanted files from the stage tarball because /var/db/pkg is incomplete.
As rac noted, "There are some 80+ packages in a stage1ball that are not listed in /var/db/pkg. Why? When you do your "emerge system", you would want your new toolchain to be used to compile all software. If portage sees that a particular version from the stageball is still current, it will omit it. The solution that somebody apparently chose was to make portage forget that most of this software is installed at all, which has the unfortunate side effect of making portage be unable to clean it when your "emerge system" finishes."
It seemed that there were some good reasons to never install from a Stage 1 tarball, and some good reasons to always install from a Stage 3 tarball. The good news is that you can perform a Stage 1 installation using a Stage 3 tarball and have the best of both worlds.
With the advent of Gentoo 2005.0 the situation has improved markedly for users who wish to perform Stage 1 installs. The /var/db/pkg problem has been resolved, but unfortunately some of the circular dependency problems remain.
Another reason to continue to perform Stage 1/3 installs relates to the system toolkit. Unfortunately the GCC 3.4.4 toolkit components remain testing branch ebuilds. As such, Gentoo 2005.0 continues to ship with a stable branch GCC 3.3.5 compiler. Until such time that the GCC 3.4.4 compiler is reclassified into the stable software branch, the Stage 1/3 installation method will continue to be helpful to those users who wish to upgrade to a GCC 3.4.4-based toolkit.
Objective
This Installation Guide will describe how to perform a "Stage 1 on 3" installation of Gentoo on a 686-class x86 platform using 2005.1 installation media, a single CD-ROM drive and a single EIDE hard disk. It will take advantage of the latest 2.6 kernels, NPTL threading, udev, and the latest GCC 3.4.4 compiler. It will also completely sidestep the permissions problems that are inherent in some of the Gentoo 2005.1 installation media.
Note: Support for the 586-CHOST has been terminated in this version of the Guide. If you'd like to install for a 586-box, check out one of the preceeding verisons of the Guide.
Request for Support
If you use the Stage 1/3 Installation Guide and find it helpful in building your Gentoo system, please support my documentation development efforts. You can do so by visiting the Stage 1/3 Installation Home Page and clicking on the Ads by Google on the site: http://bobp.webhop.org. While you are there you can download a PDF version of this Guide. 
To perform a 2005.1 Stage 1/3 Installation with GCC 3.4.4, follow these steps:
1. Download and Burn the Minimal Installation CD. The .ISO image required for the hardware used in this example is | Code: | | http://gentoo.osuosl.org/releases/x86/2005.1/installcd/install-x86-minimal-2005.1.iso |
2. Boot using the Minimal Installation CD. At the "boot:" prompt, press <Enter> to select the default gentoo kernel.
3. Configure LAN Card. We're assuming that your LAN card has been recognized and that you can obtain a LAN connection via DHCP.
4. Configure Your Hard Disk
4.1 View the Hard Drive's Operational Parameters. In this example we will assume that only one hard disk will be installed on the system. It will be recognized by Gentoo as /dev/hda. We will start off by viewing the default disk parameters at boot:
| Code: | # hdparm /dev/hda
/dev/hda:
multcount = 16 (on)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 16383/255/63, sectors = 120034123776, start = 0
# hdparm -i /dev/hda
/dev/hda:
Model=WDC WD1200JB-00GVA0, FwRev=08.02D08, SerialNo=WD-WMAL92634373
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq}
RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=74
BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=234441648
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no, WriteCache=enabled
Drive conforms to: device does not report version:
* signifies the current active mode |
4.2 Tweak the Hard Disk Parameters with Hdparm. In this example we're using a WD1200JB. Its possible to get a little better performance out of this drive by issuing a few parameters with hdparm. The following parameters work well with this drive:
| Code: | # hdparm -a256A1c1d1m16u1 /dev/hda
/dev/hda:
setting fs readahead to 256
setting 32-bit IO_support flag to 1
setting multcount to 16
setting unmaskirq to 1 (on)
setting using_dma to 1 (on)
setting drive read-lookahead to 1 (on)
multcount = 16 (on)
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
readahead = 256 (on) |
4.3 Test the Hard Drive's Performance.
Typical results for a Pentium 3 with UDMA66:
| Code: | # hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 520 MB in 2.01 seconds = 258.75 MB/sec
Timing buffered disk reads: 114 MB in 3.01 seconds = 37.90 MB/sec |
4.4 Partition the Hard Drive
4.4.1 Display the Partition Information
Technically, the syntax of this command is used to change the partition information, but on an unpartitioned drive it will display the partition information that is available:
| Code: | # fdisk /dev/hda
The number of cylinders for this disk is set to 14593.
There is nothing wrong with that, but this is larger than 1024,
and in certain setups could cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/hda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
Command (m for help): |
4.4.2 Plan Our Partition Scheme:
To keep it simple, we're going to use the following partition scheme. I'll leave out the details, assuming that you know how to partition your hard disk.
| Code: | Partition File System ID Size Description
/dev/hda1 ReiserFS 3.6 83 100 MB Boot partition
/dev/hda2 (swap) 82 512 MB Swap partition
/dev/hda3 ReiserFS 3.6 83 Remainder Root Partition |
4.4.3 Partition the Hard Disk (Boring details omitted in the interest of brevity)
4.4.4 Verify the partition configuration.
| Code: | Disk /dev/hda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 76 506047+ 82 Linux swap
/dev/hda3 77 14593 116607802+ 83 Linux |
4.4.5 Exit Fdisk and Save the Partition Layout Press "w" to write the partition table to disk and exit fdisk.
| Code: | Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks
|
4.5 Installing File Systems. This example covers the installation of Reiser FS 3.6 on the /boot and /root partitions, and swap on the /swap partition.
4.5.1 Install Reiser FS on /dev/hda1 and /dev/hda3:
| Code: | | # mkreiserfs /dev/hda1 && mkreiserfs /dev/hda3 |
You will need to answer "Y" when asked if you want to continue installing Reiser FS on the hard disk.
4.5.2 Install the swap partition on /dev/hda2:
| Code: | | # mkswap /dev/hda2 && swapon /dev/hda2 |
4.6 Mounting the File Systems. Mount the partitions using the "mount" command.
| Code: | # mount /dev/hda3 /mnt/gentoo
# mkdir /mnt/gentoo/boot
# mount /dev/hda1 /mnt/gentoo/boot |
5. Installing the Gentoo Installation Files.
5.1 Download the i686 Stage 3 Tarball from the Internet.
Go to the gentoo mount point on your hard disk:
We will need to download 2 files from the mirrors: The Stage 3 tarball and its checksum file. We will download the following four files using the "wget" command at the bash prompt. The entire command must be typed on one line:
| Code: | # wget http://gentoo.osuosl.org/releases/x86/2005.1/stages/i686/stage3-i686-2005.1.tar.bz2
# wget http://gentoo.osuosl.org/releases/x86/2005.1/stages/i686/stage3-i686-2005.1.tar.bz2.md5 |
If you need to check the list of Gentoo Mirrors, Click Here.
5.2 Verify the md5sum of the Tarballs.
| Code: | # md5sum -c stage3-i686-2005.1.tar.bz2.md5
stage3-i686-2005.1.tar.bz2: OK |
5.3 Unpack the Stage 3 Tarball. Unpack the Stage 3 tarball using the following command.
| Code: | | tar -xjpvf stage3-i686-2005.1.tar.bz2 |
Now is a good time to take a break to re-dose with some caffeine, as this will take a little while...
5.4 Installing Portage
5.4.1 Download a Fresh Portage Snapshot from the Internet.
| Code: | | # wget http://gentoo.osuosl.org/snapshots/portage-latest.tar.bz2 |
5.4.2 Extract the Portage Snapshot
| Code: | | tar -xjvf /mnt/gentoo/portage-latest.tar.bz2 -C /mnt/gentoo/usr |
Some of these steps will take a while to complete.
6. Installing the Gentoo Base System
6.1 Copy DNS Information Copy the DNS information in /etc/resolv.conf to ensure that networking works in our new Gentoo environment.
| Code: | | # cp -L /etc/resolv.conf /mnt/gentoo/etc/resolv.conf |
6.2 Mount the proc filesystem We will mount the /proc file system to allow our Gentoo installation to use kernel-provided information within the chrooted environment.
| Code: | # mount -t proc none /mnt/gentoo/proc
# mount -o bind /dev /mnt/gentoo/dev
# cp /proc/mounts /mnt/gentoo/etc/mtab |
6.3 Chroot into the New Environment
| Code: | # chroot /mnt/gentoo /bin/bash
# env-update
# source /etc/profile |
6.4 Set the Date and Time
6.4.1 Set the Correct Date and Time.
The date command uses the syntax MMDDHHMMYYYY, where MM is the month, DD is the day, HHMM is the time, and YYYY is the year. As I type this, it is Sunday March 27, 2005 at 19:30:
| Code: | # date 032719302005
Sun Mar 27 19:30:00 Local time zone must be set--see zic manual page 2005 |
6.4.2 Set the Time Zone Symlink.
This example displays the available time zone selections for the Western Hemisphere:
| Code: | | # ls /usr/share/zoneinfo/America |
I'll set the local time zone to Central Time because I live in Chicago. To do this, I first remove the symlink to the default time zone, and then replace it with a symlink to my local time zone:
| Code: | # rm /etc/localtime
# ln -s /usr/share/zoneinfo/America/Chicago /etc/localtime
Sun Mar 27 19:32:50 CST 2005 |
6.4.3 Get it Right for Daylight Savings Time.
The previous example showed how to select a city when setting the timezone symlink. It is my opinion that you should always choose a city that is in your time zone, and use the city to set the time zone symlink. You should NEVER choose a time zone as your symlink for the setting the time zone. Here's why:
I live in Chicagoland. By setting the timezone symlink to the nearest major city, Chicago, I don't have to worry about implementing Daylight Savings Time. Linux is smart enough to spring forward and fall back so that no changes to the system time are necessary on my part. This past weekend, when Chicago changed from Central Standard Time to Central Daylight Time, I watched with glee as the clocks on all of my linux PCs ticked from 01:59:59 CST to 03:00:00 CDT. (Just in case you were wondering, THAT is confirmation that I am a basement-dwelling linux g33k!) If I had made the mistake of setting the timezone symlink to CST, then linux would have kept my PC's clock on CST, even though the city that I live in had switched to CDT. In this case, I would either have to manually change my clock over from CST to CDT, or learn to live with a PC who's clock is off by an hour.
6.5 Configuring the USE Flags, Portage Options, and Compile Options: /etc/make.conf
In this example, we're compiling for a 686-class box on the x86 architecture. Our CHOST setting will be i686-pc-linux-gnu. Since all of the 686-class boxes use the same CHOST, it really doesn't matter which tarball we start off with. More accurately, you can start off with the i686 tarball and properly complete the install for any of the 686-class boxes. The advantage for doing this is that the i686 tarball is not effected by the permissions problems that plague some of the other 686-class tarballs. All that you need to worry about is changing the architecture specification for your processor.
This Guide uses a minimalist setting of the USE variable. You are free to add additional USE flags as needed for your specific system requirements, but it is recommended that you do not add them to /etc/make.conf until after you have completed the entire installation.
Please note: The specification of the "nptl" and the exclusion of the "nptlonly" USE flag is intentional, in order to provide both NPTL threading support in glibc as well as fallback support for linuxthreads. Use of the "nptlonly" USE flag is NOT recommended! The use of hardened GCC 3.4.4 is not recommended on any x86 systems except AMD64.
| Code: | # cat /etc/make.conf
CHOST="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -pipe"
CXXFLAGS=${CFLAGS}
ACCEPT_KEYWORDS="x86"
PORTAGE_TMPDIR=/var/tmp
PORTDIR=/usr/portage
DISTDIR=${PORTDIR}/distfiles
PKGDIR=${PORTDIR}/packages
PORT_LOGDIR=/var/log/portage
PORTDIR_OVERLAY=/usr/local/portage
GENTOO_MIRRORS="<your mirror goes here> http://gentoo.osuosl.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
RSYNC_RETRIES="3"
RSYNC_TIMEOUT=180
MAKEOPTS="-j2"
PORTAGE_NICENESS=3
AUTOCLEAN="yes"
FEATURES="distlocks sandbox userpriv usersandbox"
USE="nptl"
#CCACHE_SIZE="512M" |
6.6 Additional Portage Configuration
6.6.1 Create Portage Directories
The sample /etc/make.conf listed above specifies directories for Portage log files and overlays that are not included as part of a standard Gentoo installation. If you are going to use the logging and overlay functions listed in the sample make.conf file, then you will need to create two additional directories on your system.
| Code: | # mkdir /var/log/portage
# mkdir /usr/local/portage |
6.6.2 Package Keywords - Enabling GCC 3.4.4 in the Stable Branch
Skip this step and proceed to the next section if you have configured your system to use the "~x86" testing branch.
At the time that I write this guide, GCC 3.4.4 is part of the unstable or "testing" branch in Portage. If you will be using the "x86" stable branch of the software, then we need to configure Portage to enable the use of GCC 3.4.4 and some other toolkit components, even though they are currently classified in the testing branch.
To configure a stable branch system to utilize a testing branch ebuild, we need to let Portage know that we have approved this subset of the testing branch for use on our system. This is accomplished by specifying the name of the package and the applicable keyword in the /etc/portage/package.keywords file. We will enable support for four testing branch ebuilds in our system.
| Code: | # cat /etc/portage/package.keywords
~sys-devel/gcc-3.4.4 ~x86
sys-devel/gcc-config ~x86
sys-libs/libstdc++-v3 ~x86
sys-libs/glibc ~x86
sys-devel/binutils ~x86
sys-libs/timezone-data ~x86 |
6.6.3 Update the Portage Tree
We will now update our portage snapshot to include the current portage tree.
6.7 Activate User Locales
When compiling glibc (we'll do this in an upcoming step), Gentoo's default behavior is to compile a full set of all of the available user locales. We will activate the userlocales local USE flag to limit the compilation of userlocales to those that we specify. Limiting the scope of userlocales will save us a tremendous amount of time while compiling glibc. (While we're editing this file, we'll also add "ithreads" as a package-specific USE flag for perl and libperl to allow interpreter level threading. This flag is optional but recommended.)
6.7.1 Activate the userlocales USE flag for glibc
| Code: | # cat /etc/portage/package.use
sys-libs/glibc userlocales
sys-devel/libperl ithreads
dev-lang/perl ithreads |
6.7.2 Specify the user locales to build.
Create the /etc/locales.build file with your favorite editor. I'm located in the USA, so I'll use the following values.
| Code: | # cat /etc/locales.build
en_US/ISO-8859-1
en_US.UTF-8/UTF-8 |
7. Building the Toolkit
7.1 Building the Toolkit: GCC 3.3.5
To enable NPTL support we are required to use a 2.6 kernel and linux26-headers. Linux26-headers is now contained in the 2005.0 Stage 3 tarball, so it is no longer necessary to manipulate the linux headers as it was when installing with 2004.3 media.
| Code: | # env-update && source /etc/profile
# emerge gcc-config glibc binutils libstdc++-v3 gcc |
This is a good opportunity to take an extended break, as these instructions will take quite some time to complete.
7.2 Re-Building the Toolkit: GCC 3.4.4
After emerging a new version of GCC, we need to pause for a moment and think about what we've done. We've just used GCC 3.3.5 and a toolchain built with GCC 3.3.5 to compile GCC 3.4.4. Before we spend any more time building our Gentoo system we should rebuild the entire toolchain, re-compiling it so that we have GCC 3.4.4 that was built with GCC 3.4.4.
Before we do this we need to examine /etc/make.conf and make changes to the CFLAGS statements in order to take advantage of the new performance-enhancing features of GCC 3.4.4. After making necessary updates to /etc/make.conf we need to rebuild the toolkit using the new GCC 3.4.4 compiler. The result will be a 3.4.4 tooklit, compiled by a 3.4.4 toolkit that was built with a 3.3.5 toolkit. Clear as mud? 
7.2.1 Updating make.conf
Here are some settings for /etc/make.conf that may be worth considering. They are the actual CFLAGS that I used to build my systems and have proven reliable on multiple installations. They include extreme levels of code optimization (notice the -O3 flag), and some very safe and stable performance-enhancing CFLAGS. Depending upon your individual hardware, you may have to simplify some of the CFLAGS settings.
| Code: | CFLAGS="-O3 -march=pentium3 -fforce-addr -fomit-frame-pointer -ftracer -pipe"
CXXFLAGS="${CFLAGS} -fvisibility-inlines-hidden" |
l still be getting most of the benefits of GCC 3.4.4, so this isn't a bad compromise. This may be a better approach for those who don't want to be on the bleeding edge or don't want to spend time troubleshooting.
7.2.2 Configuring the Default C Compiler
Although we have emerged GCC 3.4.4, it has not been automatically installed as our default compiler. If you have any doubts about this, take a quick peek at the output of "emerge info" or "gcc-config -l". Although GCC 3.4.4 has already been emerged, GCC 3.3.5 is still installed as out default compiler:
| Code: | # gcc-config -l
1] i686-pc-linux-gnu-3.3.5.20050130-r1
[2] i686-pc-linux-gnu-3.3.5.20050130-r1-hardened
[3] i686-pc-linux-gnu-3.3.5.20050130-r1-hardenednopie
[4] i686-pc-linux-gnu-3.3.5.20050130-r1-hardenednopiessp
[5] i686-pc-linux-gnu-3.3.5.20050130-r1-hardenednossp
[6] i686-pc-linux-gnu-3.4.4 *
[7] i686-pc-linux-gnu-3.4.4-hardened
[8] i686-pc-linux-gnu-3.4.4-hardenednopie
[9] i686-pc-linux-gnu-3.4.4-hardenednopiessp
[10] i686-pc-linux-gnu-3.4.4-hardenednossp
|
Change the default compiler to gcc 3.4.4 by issuing the following command. Note that the numbers may have changed.
7.2.3 Updating the System Environment
An additional command updates our system environment:
| Code: | | # env-update && source /etc/profile |
7.2.4 Rebuilding the System Toolkit
Now its time to rebuild the toolkit. We'll start off by recompiling glibc, binutils, gcc, and by updating portage. This will rebuild our GCC 3.4.4 compiling toolkit (which had previuosly been compiled with GCC 3.3.5) with the GCC 3.4.4 compiler, taking advantage of our new USE flags and CFLAGS compiler settings.
| Code: | | # emerge glibc binutils libstdc++-v3 gcc portage |
Upon completion of the rebuild of the compiling toolkit, we will recompile the entire system to assure that our entire toolkit has been compiled using GCC 3.4.4 and our hardware-specific settings.
The result will be a 3.4.4 tooklit and an entire system that is built with a 3.4.4 toolkit, that was built with a 3.4.4 toolkit. 
| Code: | | # emerge -e system && emerge -e system |
7.2.5 Prune the GCC Compiler
Now that GCC 3.4.4 has been installed as the default compiler and our system has been rebuilt, we can prune GCC 3.3.5 from our system by issuing the following commands. First, verify that GCC 3.4.4 has indeed been installed as the default compiler using the "l" parameter with gcc-config. (Just to avoid any confusion, the parameter used is a lower case "L", not the number "one".) Then, after confirming that GCC 3.4.4 has been installed as the default compiler, prune GCC 3.3.5 from your system.
| Code: | # gcc-config -l
# emerge -P gcc |
7.2.6 Summary
Although these command have been broken down into separate steps for the purpose of clarity, they can be concatenated into three steps. The one-liners in Steps 1 and 3 will take quite some time to complete, and represent good opportunities for you to take an extended break while Gentoo does its thing.
Step 1: | Code: | | # env-update && source /etc/profile && emerge gcc-config glibc binutils libstdc++-v3 gcc |
Step 2: update your USE flags and CFLAGS in /etc/make.conf
Step 3: | Code: | | # gcc-config 6 && env-update && source /etc/profile && emerge glibc binutils libstdc++-v3 gcc portage && emerge -e system && emerge -e system && emerge -P gcc |
8.0 Building the World
8.1 Emerge Ccache (Optional)
Now that our toolkit has been built, we'll emerge the ccache program. Ccache is a compiler cache that will help to reduce compile times when previously compiled programs are being recompiled. It will not effect the time required to compile programs on the first pass, so this is an optional step. (Note: the ccache_size was set to 512 MB in the sample make.conf. If you have sufficient disk space, and you're planning on emerging a bloated window manager like Gnome or KDE (or if you are performing an emerge -e system or an emerge -e world), then you may want to increase the to something like ccache_size="2G".)
8.2 Emerging Programs
Now its time to add a few useful packages to our world profile:
| Code: | # emerge syslog-ng xinetd grub vixie-cron reiserfsprogs sysfsutils dhcpcd hotplug coldplug gentoolkit
# emerge --nodeps acpid ntp |
8.3 Updating the Environment
Now we'll add these services to the default runlevel. Here two ways to accomplish this task that are functionally equivalent. Choose the one you like best.
| Code: | # rc-update add syslog-ng default
# rc-update add net.eth0 default
# rc-update add vixie-cron default
# rc-update add xinetd default
# rc-update add sshd default
# rc-update add hotplug default
# rc-update add coldplug default
# rc-update add acpid default
# rc-update add ntp-client default |
or if you're an ub3r-g33k, try this cool bash loop that saves alot of typing:
| Code: | | for x in syslog-ng net.eth0 vixie-cron xinetd sshd hotplug coldplug acpid ntp-client ; do rc-update add $x default ; done |
8.4 Configuring the NTP Client
In the previous steps we emerged a Network Time Protocol client to allow us to use NTP time servers to synchronize our system clock. In this step we'll configure the ntp-client to eliminate clock skew:
| Code: | | # ntpdate -b -u pool.ntp.org |
9. Kernel
9.1 Downloading the Kernel
The decision to enable NPTL support requires that we use a 2.6 kernel. You are free to choose any flavor of 2.6 kernel that you like. In this example, we'll be using the Gentoo (Development) Sources kernel. Note that a 2.4 kernel will not work properly with this Installation Guide.
| Code: | | # emerge gentoo-sources |
9.2 Building the Kernel Symlink
| Code: | # rm /usr/src/linux
# cd /usr/src
# ln -s linux-2.6.12-gentoo-r6 linux |
9.3 Configuration
9.3.1 Enable udev Support
Edit your /etc/conf.d/rc file so that it contains the following statements:
| Code: | RC_NET_STRICT_CHECKING="no"
RC_DEVICES="udev"
RC_DEVICE_TARBALL="no" |
9.3.2 Configure Kernel Options
If you're following this Installation Guide, we're going to assume that you want the best performance from your system, and that you'll be using a custom-compiled kernel instead of genkernel. When configuring your kernel, be sure to include support for hotplug firmware loading. Also be sure to remove devfs filesystem support, as we are designing udev support into our system.
Configure the kernel:
| Code: | # cd /usr/src/linux
# make menuconfig |
9.3.3 Compiling the Kernel
To compile your kernel and install the kernel and selected modules, issue the following command. I find that this one works a bit better than some of the other one-liner kernel compilation commands. If you should run into a problem where kernel compilation fails, its easy to determine where the problem was. In addition, this command will also install the kernel for you:
| Code: | | # make && make modules && make modules_install && make install |
10. Configuring the System
10.1 Configure Network Adapters
Configure your network adapters as recommended in the Gentoo Installation Handbook. In our case, we'll use DHCP:
| Code: | # cat /etc/conf.d/net
iface_eth0="dhcp"
dhcpcd_eth0="-t 10"
|
If this isn't suitable for you, consider these options as listed in the GIH:
| Code: | # (For DHCP)
iface_eth0="dhcp"
# Some network admins require that you use the
# hostname and domainname provided by the DHCP server.
# In that case, add the following to let dhcpcd use them.
# That will override your own hostname and domainname definitions.
dhcpcd_eth0="-HD"
# If you intend on using NTP to keep your machine clock synchronized, use
# the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file
dhcpcd_eth0="-N"
#(For static IP)
iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
gateway="eth0/192.168.0.1"
#(For rp-pppoe)
iface_eth0="up"
|
10.2 Set Hostnames and Domainnames
The following hostname and domainname locations referenced in the Gentoo Installation Handbook and some of the other HowTo appear to have been deprecated. The first example in each of the following two sections uses the old configuration method, which has been deprecated but this is not yet reflected in many of the installation guides. The second option in each of the following two examples is more current:
10.2.1 Set Your Hostname
The following examples provide instruction for setting the hostname on your Gentoo box. We'll use the "boatanchor" as the hostname in this example.
| Code: | # cat /etc/conf.d/hostname
HOSTNAME="boatanchor"
|
10.2.2 Set Your Domainname
| Code: | # cat /etc/conf.d/domainname
OVERRIDE=1
DNSDOMAIN="mydomain.com"
NISDOMAIN="nis.mydomain.com"
|
10.2.3 Update /etc/hosts
If nameservers on your network handle all name resolution, then you can skip this step.
If your PC is a standalone system, or if your PC has a static IP address and you don't have DNS entries for your machine in a nameserver somwehere on your network, then you should specify the following information in the /etc/hosts file.
| Code: | 127.0.0.1 localhost.localdomain localhost
static.ip.addr.ess boatanchor.mydomain.com boatanchor |
The value of "static.ip.addr.ess" needs to be substituted with the IP address of your Gentoo box. For example, if your Gentoo box's IP address is 192.168.0.5, your /etc/hosts file should contain the following lines.
| Code: | 127.0.0.1 localhost.localdomain localhost
192.168.0.5 boatanchor.mydomain.com boatanchor |
10.2.4 Add domainname to the Default Runlevel
| Code: | # rc-update add domainname default
|
10.3 Gensplash
For all of you eye-candy addicts who can't live without it, here's the section where we add gensplash to give us those ultra-cool framebuffer images in our consoles. Because some of us have really big monitors, we'll configure splash screens at your choice of 1024x768, 1280x1024 and 1600x1200 resolutions:
| Code: | # emerge splashutils splash-themes-gentoo
# splash_geninitramfs -v -g /boot/fbsplash-emergence-1024x768 -r 1024x768 emergence && splash_geninitramfs -v -g /boot/fbsplash-emergence-1280x1024 -r 1280x1024 emergence && splash_geninitramfs -v -g /boot/fbsplash-emergence-1600x1200 -r 1600x1200 emergence && rc-update add splash default |
Note: Gensplash and the framebuffer is UNSUPPORTED in the Stage 1/3 Guide.
10.4 Grub Bootloader
10.4.1 Grub.conf
To boot our installation of Gentoo Linux we'll need to configure a boot menu for the Grub Bootloader. Use your favorite text editor to create the /boot/grub/grub.conf file. In this case we'll use nano:
| Code: | # cd /boot/grub
# nano -w grub.conf |
You can either cut and paste the following text into the file, or type it in manually. Note that the lines beginning with the word "kernel" and ending with the words "splash=verbose,theme:emergence" need to be typed on one line. In this example, we're using the vesafb-tng video driver, and the video= statements are formatted accordingly.
| Code: | # Grub boot menu configuration file
#
# Boot automatically after 30 secs.
timeout 30
# By default, boot the second entry.
default 1
# Fallback to the first entry.
fallback 0
# Use default Grub Splash image
# splashimage=(hd0,0)/grub/splash.xpm.gz
#
# Use custom (downloaded) Gentoo Splash Image
splashimage=(hd0,0)/grub/gentoo.xpm.gz
# Boot Gentoo Linux (no framebuffer)
title Gentoo-2.6.12-r6
root (hd0,0)
kernel (hd0,0)/vmlinuz ro root=/dev/hda3 video=vesafb:ywrap,pmipal,1024x768-16@85
# Boot Gentoo Linux at 1024x768 framebuffer resolution
title Gentoo-2.6.12-r6, 1024x768
root (hd0,0)
kernel (hd0,0)/vmlinuz ro root=/dev/hda3 video=vesafb:ywrap,pmipal,1024x768-24@85 splash=verbose,fadein,theme:emergence CONSOLE=/dev/tty1
initrd (hd0,0)/fbsplash-emergence-1024x768
# Boot Gentoo Linux at 1280x1024 framebuffer resolution
title Gentoo-2.6.12-r6, 1280x1024
root (hd0,0)
kernel (hd0,0)/vmlinuz ro root=/dev/hda3 video=vesafb:ywrap,pmipal,1280x1024-24@85 splash=verbose,fadein,theme:emergence CONSOLE=/dev/tty1
initrd (hd0,0)/fbsplash-emergence-1280x1024
# For installing GRUB into the hard disk
title Install GRUB into the hard disk
root (hd0,0)
setup (hd0)
|
10.4.2 Installing Grub onto the Hard Disk
Start Grub from the command prompt and use the following commands to embed grub into the hard disk. Remember, when counting hard disks we like to start at 1, but Grub likes to start at 0, so /dev/hda1 corresponds to hard disk 0, partition 0 in Grub.
| Code: | # grub
grub> root (hd0,0)
grub> setup (hd0)
grub> quit
|
10.4.3 Download a Cool Grub Splash Screen
We'll also download a cool Gentoo-specific splash screen for Grub.
| Code: | | wget http://www.schultz-net.dk/downloads/grub/gentoo.xpm.gz |
10.5 Filesystem - Configuring fstab
This is a sample /etc/fstab file that reflects the disk partition scheme used earlier in this Installation Guide. Make changes as appropriate if your partition scheme is different.
| Code: | # <fs> <mountpoint> <type> <opts> <dump/pass>
/dev/hda1 /boot reiserfs noauto,notail 1 2
/dev/hda3 / reiserfs notail 0 1
/dev/hda2 none swap sw 0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 user,noauto,ro,exec 0 0
/dev/fd0 /mnt/floppy auto noauto,users 0 0
# NOTE: The next line is critical for boot!
none /proc proc defaults 0 0
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
# Adding the following line to /etc/fstab should take care of this:
none /dev/shm tmpfs nodev,nosuid 0 0
|
10.6 Setting HD Paramaters
Back in Section 4 we developed optimized operating parameters for our hard disk. Now that we're in the chrooted environment of our newly designed Gentoo system, we need to make these configuration changes permanent. To do this, we'll write the HD parameters to the /etc/conf.d/hdparm file:
| Code: | # cat /etc/conf.d/hdparm
disc0_args="-a256A1c1d1m16u1"
cdrom0_args="-d1c1u1"
|
After editing the contents of /etc/conf.d/hdparm type the following command to add hdparm to the boot runlevel.
| Code: | | # rc-update add hdparm boot |
10.7 Set-Up User Accounts
We must change the password of the root user in our newly installed system. Then we will add non-root users to the system. Substitute the username examples "bob" and "mary" with your own usernames.
First, change the root password:
| Code: | # passwd
New password: (Enter your new password)
Re-enter password: (Re-enter your password) |
Now add users who will be allowed to "su" their way to temporary root status. These users must be added to the "wheel" user group:
| Code: | # useradd -m -G users,wheel bob
# passwd bob
New password: (Enter bob's password)
Re-enter password: (Re-enter bob's password) |
Now add non-root users to the system:
| Code: | # useradd -m -G users mary
# passwd mary
New password: (Enter mary's password)
Re-enter password: (Re-enter mary's password) |
10.8 Toggle NUMLOCK ON at Boot
If you'd like the NUMLOCK key to be toggled ON at system boot, execute the following command.
| Code: | | # rc-update add numlock default |
10.9 Define Console Screen Blanking Interval
If youre not happy with the standard screen blanking interval for the console (to me the screen always seems to blank too quickly), you can specify the desired interval (from 1 to 60 minutes) using the following command. Substitute n with the value of the desired blanking interval in minutes. A value of zero will disable screen blanking.
This setting is only temporary; after rebooting the screen will resume blanking at the default interval. To make your changes permanent, issue the following command:
| Code: | | # echo setterm blank n >> /etc/conf.d/local.start |
10.10 Exiting Chroot and Unmounting Partitions
We will now exit the chrooted environment and unmount all of the mounted partitions. Use tab completion to save yourself some typing.
| Code: | exit
cd ~/
umount /mnt/gentoo/dev
umount /mnt/gentoo/proc
umount /mnt/gentoo/boot
umount /mnt/gentoo
swapoff /dev/hda2
|
11. REBOOT!
And now, the moment you've been waiting for!
When the system reboots, you should be welcomed with the following greeting.
| Code: | This is boatanchor.mydomain.com (Linux i686 2.6.15-gentoo-r5) HH:MM:SS
boatanchor login: |
12. TROUBLESHOOTING
If you encounter problems after rebooting, consider the following:
 kernel configuration errors are the most common cause of failure on first boot.
grub configuration errors are another common cause of failure on first boot.
if you have device problems, read the Gentoo udev Guide.
Have fun with your new Gentoo system!
13. If You Need Help
Remember: The Documentation, Tips & Tricks forum is not a support forum:
| Quote: | Documentation, Tips & Tricks
Unofficial documentation for various parts of Gentoo Linux. Note: This is not a support forum.
Moderator: Global Moderators |
Please bear in mind that this thread is located in the Documentation, Tips & Tricks Forum, which is not a support forum. For this reason I would like to ask that we limit the context of this thread to posts that discuss problems with the Installation Guide that need to be corrected, or to ideas about how to improve the Stage 1 on 3 installation procedure itself. If you have a problem and you need help, please post your support request in the Official 2005.0 Stage 1 on 3 for GCC 3.4.4 Support Thread in the Installing Gentoo forum.
NOTE: Documentation, Tips & Tricks is NOT a support forum. Please do not post installation support requests into this thread. Please post in the support thread that is dedicated to this installation method.
14. Corrections, Errors, Omissions
Please let me know if there are any errors or omissions in this document by sending me a personal message through the Gentoo Forums by clicking the link below.
15. Updated Credits
Thanks to @nightmorph for prodding me into addressing the update for glibc-2.3.5-r3 and timezone-data.
16. Revision History:
20051112: Fixed a cut and paste error.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Last edited by Bob P on Sat Feb 18, 2006 3:23 pm; edited 8 times in total |
|
| Back to top |
|
 |
DOSBoy
Tux's lil' helper
Joined: 26 Jun 2005
Posts: 84
|
| Posted: Sun Nov 13, 2005 8:24 pm Post subject: |
|
|
| Should you, perhaps, have a reference to using binutils-config to set the new binutils version as the default in a manner similar to that is used with gcc-config, around the point where you enable GCC 3.4.4, but before you env-update && source /etc/profile? |
|
| Back to top |
|
|
warrens
Apprentice
Joined: 04 Jan 2005
Posts: 239
Location: Don't Tread On Me!
|
| Posted: Mon Nov 14, 2005 12:13 am Post subject: |
|
|
| Quote: | | Should you, perhaps, have a reference to using binutils-config to set the new binutils version as the default in a manner similar to that is used with gcc-config, around the point where you enable GCC 3.4.4, but before you env-update && source /etc/profile? |
I just checked on my freshly installed Stage 1/3 binutils-config -l and binutils is already set to the latest and greatest without any intervention from me. It seems that only gcc is not automaticaly updated to the newest build.
By the way, I think that this thread should be given Sticky status.  |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Mon Nov 14, 2005 3:07 am Post subject: |
|
|
Sticky? that's been recommended for these Guides many times before. I'm flattered,  but I don't have the authority to make anything sticky. You need to talk to somebody official about that.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
krizz
n00b
Joined: 15 Sep 2004
Posts: 26
|
| Posted: Mon Nov 14, 2005 11:25 pm Post subject: |
|
|
Hey Bob,
Nice tutorial, but the /usr/share/timezone directory is not available if I try to link the timezone.
Cheers,
-Krizz |
|
| Back to top |
|
|
krizz
n00b
Joined: 15 Sep 2004
Posts: 26
|
| Posted: Mon Nov 14, 2005 11:50 pm Post subject: |
|
|
| krizz wrote: | Hey Bob,
Nice tutorial, but the /usr/share/timezone directory is not available if I try to link the timezone.
Cheers,
-Krizz |
I'm sorry, I misread...stage3...  |
|
| Back to top |
|
|
ajburch
n00b
Joined: 07 Nov 2005
Posts: 1
Location: North Carolina
|
| Posted: Thu Nov 17, 2005 3:53 am Post subject: recompile time |
|
|
-->Bob,
What gives with the recompile time? I have a Pentium-M Thinkpad, a pretty nice laptop. I have been recompiling for 14 hours now. This was the dreaded step:
| Quote: | | emerge -e system && emerge -e system && emerge -P gcc |
<--AJ
_________________
<--AJ
Email and Systems Support
Wilmington, NC
--------------------------------------------
"Unreasonable People Rule the World!"
-------------------------------------------- |
|
| Back to top |
|
|
Frodg
l33t
Joined: 11 Feb 2004
Posts: 761
|
| Posted: Thu Nov 17, 2005 4:07 am Post subject: |
|
|
My, but aren't the young ones impatient...
You are recompiling all your programs several times so it will be a little while yet.
_________________
Aerosolo ergo sum - I spray therefore I am
Gentoo - Registered Linux User # 361400 |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Thu Nov 17, 2005 4:51 am Post subject: Re: recompile time |
|
|
| ajburch wrote: |
What gives with the recompile time? I have a Pentium-M Thinkpad, a pretty nice laptop. I have been recompiling for 14 hours now. This was the dreaded step:
| Quote: | | emerge -e system && emerge -e system && emerge -P gcc |
|
hehe. if you can't run with the big dogs, you might as well stay on the porch. 
maybe you missed this in the other threads:
| Stage 1/3 Guide wrote: | | WARNING: This is an ADVANCED installation method. The amount of time required for you to complete this type of installation will equal or exceed that of any other Gentoo installation method. Your time will be well invested, though, as the result will be a very stable Gentoo system. This installation method may prove to be somewhat difficult and cumbersome for users who are new to Gentoo. It will prove especially painful for users who plan to install Gentoo old hardware. |
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
Iron_DragonLord
Apprentice
Joined: 04 Nov 2004
Posts: 273
|
| Posted: Sun Nov 20, 2005 3:52 am Post subject: |
|
|
14 hours? Hahaha...
Took my server almost a whole week about a few months ago. No compaints though, it was just an old box I got for free and decided to give it a use.
Anyway, spiffy guide. |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Mon Nov 21, 2005 10:14 pm Post subject: |
|
|
Updated PDF now available.
Please click on the Ads by Google to show your support. It doesn't cost you anything, and it helps to keep the wheels turning!
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
zigver
Tux's lil' helper
Joined: 09 May 2003
Posts: 87
|
| Posted: Mon Nov 21, 2005 11:16 pm Post subject: |
|
|
| Bob P wrote: | | Please click on the Ads by Google to show your support. It doesn't cost you anything, and it helps to keep the wheels turning! |
Didn't need the pdf but clicked a couple ads. Your contributions to the Gentoo community are greatly appreciated. |
|
| Back to top |
|
|
glang
n00b
Joined: 10 Oct 2005
Posts: 27
|
| Posted: Tue Nov 22, 2005 4:58 pm Post subject: |
|
|
| Bob P wrote: | Updated PDF now available.
Please click on the Ads by Google to show your support. It doesn't cost you anything, and it helps to keep the wheels turning! |
Does google not suck anymore or did they eventually give you your $100? |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Thu Dec 01, 2005 7:12 am Post subject: |
|
|
| Iron_DragonLord wrote: | 14 hours? Hahaha...
Took my server almost a whole week about a few months ago. No compaints though, it was just an old box I got for free and decided to give it a use.
Anyway, spiffy guide. |
distcc for the win.
Actually, I'm right now installing gentoo on an extra partition and I'll use a statically-built partimage to send it to my old box. |
|
| Back to top |
|
|
COiN3D
Guru
Joined: 02 Aug 2004
Posts: 543
Location: Munich, Germany
|
| Posted: Sun Dec 11, 2005 10:24 am Post subject: |
|
|
Hi Bob P,
since GCC 3.4 has been marked as stable, there's now no need any longer to unmask it.
Just as information. 
_________________
e17 documentation | Be free and use Jabber as your IM! | Combine IRC and IM |
|
| Back to top |
|
|
glang
n00b
Joined: 10 Oct 2005
Posts: 27
|
| Posted: Sun Dec 11, 2005 9:09 pm Post subject: Re: recompile time |
|
|
| ajburch wrote: | -->Bob,
What gives with the recompile time? I have a Pentium-M Thinkpad, a pretty nice laptop. I have been recompiling for 14 hours now. This was the dreaded step:
| Quote: | | emerge -e system && emerge -e system && emerge -P gcc |
<--AJ |
I followed this guide on a pentium-m more than once, start to finish takes anything up to 24 hours, give it time, it is worth the wait. |
|
| Back to top |
|
|
mr2600
n00b
Joined: 22 Feb 2004
Posts: 54
Location: Florida
|
| Posted: Tue Dec 13, 2005 9:06 pm Post subject: |
|
|
| Bob P, I cannot express how much I like your guides. I just finished an install on a P4 3ghz Nocona, and... its quite fast! Only 51MB used on initial boot, I wish I could say the same for other distros. |
|
| Back to top |
|
|
dbasetrinity
Apprentice
Joined: 25 Jun 2005
Posts: 167
|
| Posted: Wed Dec 14, 2005 6:14 pm Post subject: |
|
|
Bob P I just wanted to say Great Guide also, Ive been using your guides for awhile now and Its ultimately sweet perfection
in a very unperfect world....
I'm hoping that soon ill see a new guide with the 2005.1 with GCC4.0.1... |
|
| Back to top |
|
|
front243
n00b
Joined: 05 Sep 2005
Posts: 33
Location: Denmark
|
| Posted: Thu Dec 15, 2005 12:52 pm Post subject: |
|
|
| Nice guide, I try to follow it on my new laptop. What are some good gcc 3.4.4 settings for a pentium-m processor? |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Thu Dec 15, 2005 11:24 pm Post subject: |
|
|
| dbasetrinity wrote: | Bob P I just wanted to say Great Guide also, Ive been using your guides for awhile now and Its ultimately sweet perfection
in a very unperfect world....
I'm hoping that soon ill see a new guide with the 2005.1 with GCC4.0.1... |
you need to look at Rockhopper! it uses 4.0.2.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
golding
Apprentice
Joined: 07 Jun 2005
Posts: 232
Location: Adelaide / South Australia
|
| Posted: Tue Dec 20, 2005 10:02 am Post subject: |
|
|
From the Gentoo Forums Thread (above)
| Quote: | Copyright (c) 2005 Bob Predaina. Released under the Creative Commons Attribution-ShareAlike license version 2.0. If you base a derivative work on this Guide, you MUST give credit to the Author in your document, and your document must contain a hyperlink that points to This URL. If you paraphrase sections of this Guide, no further attribution is required. OTOH, if you quote sections of this Guide, you must either: a) identify the quoted sections as quotes, with full citations of authorship and a hyperlink to this web page, or b) provide me with co-authorship status as a secondary author on your work.
|
From your web page
| Quote: | You may:
* Post a hyperlink to this web page.
* Download the PDF file for your own personal use.
You may not:
* Post a hyperlink that links directly to the Stage 1/3 Installation Manual.
* Distribute this document to a third party without the express written permission of the author.
* Post this PDF, a reproduction of its contents, or any of the content of this web site on the Internet, an Intranet, or any network server, including proxy servers.
* Charge a fee for the transfer of this document.
* Use this document in any commercial, business, governmental or military application without the express written permission of the author.
|
From the CC Plain English Page
| Quote: | Attribution-ShareAlike 2.0
You are free:
* to copy, distribute, display, and perform the work
* to make derivative works
* to make commercial use of the work
Under the following conditions:
by Attribution.
You must attribute the work in the manner specified by the author or licensor.
Share Alike.
If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one.
* For any reuse or distribution, you must make clear to others the license terms of this work.
* Any of these conditions can be waived if you get permission from the copyright holder.
Your fair use and other rights are in no way affected by the above. |
The text from the forum and the CC page are similar, however the text from your private site is not.
What is this? You're free, but, I'm just gonna put this chain around your neck ... hmm?
I can only conclude that the PDF, without actually having seen it, and the forum HowTo are very different. Due to the pdf sites licence requirements, I have chosen NOT to download it.
_________________
Regards, Robert
..... Some people can tell what time it is by looking at the sun, but I have never been able to make out the numbers. |
|
| Back to top |
|
|
greyhats
n00b
Joined: 07 Apr 2004
Posts: 27
|
| Posted: Thu Dec 22, 2005 7:28 pm Post subject: |
|
|
Hail Bob and everyone.
Just finish to install my system. It took me almost 2 days with lots of cafeine
So, like other said this guide ROCK, and I believe Im not the first one who said that.
So, here are the spec on what I've build my system:
Laptop IBM thinkpad T41.
processor 1600 GHZ pentium M
Disk 40 gig
Videocard ATI Radeon 7500
whatelse .. 512M ram for now planing to add another 512 soon.
For making the kernel, I did my lazy ass and went with genkernel. I changed the processor type for Pentium M.
Beside that I did follow the guide step by step including the coffee break and I'm up and runing.
Thanks for the nice guide. I'll buy you a root beer. |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Thu Dec 22, 2005 11:22 pm Post subject: |
|
|
thanks for the note. i'm always thirsty, so a root beer would be great. after you've recovered from the install, do take the time to build a custom kernel for your system. that's one of the best low-cost performance enhancements that you can add to your system! besides, after all that compiling that you've done, compiling a kernel won't seem to take long at all.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Fri Dec 23, 2005 7:28 pm Post subject: |
|
|
| golding wrote: | | I can only conclude that the PDF, without actually having seen it... |
Some people jump to conclusions.
You make giant leaps. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Documentation, Tips & Tricks
