Gentoo is a species of small fast penguin, pronounced "gen-too" (The "g" in "gentoo" is a soft "g", as in "gentle".)

Gentoo Linux is a fast, modern distribution with a clean and flexible design -- in this respect, Gentoo may appeal to Slackware, Linux From Scratch or BSD users. Unlike most Linux distros, Gentoo has a package system reminiscent of BSD's ports, meaning the packages are continually updated to the lastest versions.

The build .tbz2 file is a minimal set of system files that is necessary for allowing a user to bootstrap and install Gentoo Linux. The build .iso is a complete, bootable CD image that contains a system kernel, a reasonably complete set of kernel modules, necessary system tools such as mkfs and networking support, as well as the .tbz2 minimal-system tarball. Most users will install Gentoo Linux by burning the .iso file onto a CD, booting off of the CD, and installing from within the minimal linux environment provided by the Gentoo boot CD. It is possible, however, for users to install Gentoo Linux directly from an already-existing Linux distribution. Such users need only download the .tbz2 file, install the contents on a spare partition (making sure to use the p flag when untarring the tarball!), chroot, and install in the usual fashion.

The .tbz2 minimal-system tarball only needs to be revised when there have been significant changes to the core Gentoo Linux system (such as baselayout changes, or a new profile), and as such .tbz2 updates are relatively rare. The .iso file tends to get updated whenever we discover that somebody has hardware that won't boot from our .iso. Since new kernel modules and patches are constantly being generated, this situation probably won't stabilise anytime soon.

Make sure the second IDE port is set to CDROM (it unsets itself if the device isn't attached on boot) then do the following at the isolinux boot: prompt:

boot: rescue ide2=0x180,0x386

If you are using a 1.0_rc5 or earlier boot CD, apart from thinking about downloading the latest iso, type gentoo instead of rescue, above.

When you use any optimizations beyond -O3, you're really taking the risk of having broken packages. Very aggressive optimizations sometimes cause the compiler to streamline the assembly code to the point where it doesn't quite do the same thing anymore. A possible setting based on Loc-Dog (on IRC)'s CFLAGS is -O3 -mcpu=i686 -march=i686 -fforce-addr -fomit-frame-pointer -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -falign-functions=4, which is about as much as I'd want to push global optimization settings. Beyond this, it's best to use ultra-high optimizations only with specific packages where you really need that extra 2%, (eg graphics and various multimedia programs), and where you can easily test the package to ensure that it hasn't been optimized into oblivion.

Please try first to compile with CFLAGS -march= -O2 before reporting a bug

The default password is blank; hit enter.

You can use passwd to change the password for the user you are logged into. for extra options and setting, please see man passwd once you've completed the install.

Everyone seems to think that i shouldn't be using root for everyday use, how can i add another user?

The command adduser gentoo will add a user called gentoo. The next step is to give this user a password and passwd will do exactly that.

Insteed of adduser you can also use:

# useradd gentoo -m -G users,audio,wheel -s /bin/bash

For security reasons, users may only su to root if they belong to the wheel group. To add a username to the wheel group, issue the following command as root:

# usermod -G users,wheel username

If you're using 1.0_rc5 or greater, you don't need to do anything special to get devfs working; it's already active (you did make sure that devfs was built into the kernel, didn't you?). However, if you are using a version of Gentoo Linux prior to version 1.0_rc5, add devfs=mount to your GRUB kernel boot options so that the line looks something like kernel /boot/boot/bzImage devfs=mount foo=bar The kernel will then mount the /dev devfs filesystem automatically at boot-time.

Under Gentoo Linux 1.0_rc6 and later, you can disable devfs by passing the gentoo=nodevfs to the kernel.

If you are using 1.0_rc6 or later, then you can just use ln -s to make the usual symbolic link from /dev/mouse, and it will be preserved between reboots.

All other users need to edit /etc/devfsd.conf and add these lines:

REGISTER        ^misc/psaux$    CFUNCTION GLOBAL symlink misc/psaux mouse
UNREGISTER      ^misc/psaux$    CFUNCTION GLOBAL unlink mouse

If you are not using the devfs PS/2 mouse /dev/misc/psaux device, adjust the misc/psaux strings above accoringly. You'll then want to killall -HUP devfsd to get devfsd to reread /etc/devfsd.conf.

During installation the grub boot files are copied to /boot/grub (/boot/boot/grub in Gentoo Linux 1.0_rc5 and earlier.) Grub automatically looks in the /boot/grub directory on the boot partition. (We strongly recommend having a separate no-auto boot partition mounted at /boot, since that way it is much more difficult to clobber your kernel and boot info by accident.) The above error generally arises from (a) not using a separate boot partition, (b) forgetting to mount the boot partition at /boot before either unpacking the build snapshot or running emerge --usepkg system, or (c) forgetting the notail option when mounting a ReiserFS /boot partition. You can get more information on grub, including how to debug grub from the grub prompt, by reading the IBM developerWorks Grub tutorial.

Disable MPS 1.4 (multi-processor-system) in the BIOS or switch this function to 1.1. By using this option you just switch the MPS version. The Multi-Processor-System will still work properly. Make sure to boot Gentoo Linux with the following boot option, noapic.

They exist in our portage tree as ebuild autobuild scripts; we are primarily a ports-based distribution, meaning that we provide scripts (.ebuild files) and a special system (Portage) so that you can build apps from sources. We generally only build binaries for releases and snapshots. The Development HOWTO covers the contents of an ebuild script in detail. For full binary ISO releases, we create a full suite of binary packages in an enhanced .tbz2 format (.tar.bz2 compatible with meta-information attached to the end of the file.)

In one sentence, because Portage is much better in so many ways. One of the design philosophies of the .ebuild syntax was to make it an analog of what you'd type to install the program manually, thus making Portage very easy to learn and modify to your needs. We also have OpenBSD-style "fake" installs, safe unmerging, system profiles, package masking, a real dependency system, and lots of other good stuff.

Portage features the best of apt and ports; for example, USE options, a full dependency system, safe installs and uninstalls, and a true package database. Think of Portage as the best of both worlds; a ports system with the sensibilities and safety of a Linux package management system built-in.

The Portage User Guide details how to install and uninstall packages, and update Portage.

/etc/make.conf should be modified to override global and profile-specific default options used to compile and merge packages. The most common options are as follows:

As of Portage 1.5 onwards, /etc/make.defaults is antiquated; if you have portage-1.5-r1 or above installed then you can safely delete it. This file has been replaced by /etc/make.profile/make.defaults (/etc/make.profile should actually be a symlink to, /usr/portage/profiles/default), which contains system profile-specific default settings. The priority order of the various configuration files is as follows (highest first):

1. Environment variables
2. /etc/make.conf, for your use
3. /etc/make.profile/make.defaults, for profile-specific defaults
4. /etc/make.globals, for global defaults (settings not specified in any other place come from here)

YES! Type emerge --update system (use it with --pretend first) to update all core system packages, and use emerge --update world (again, use it with --pretend first) to do a complete system upgrade of all installed packages.

Portage now includes config file management support by default. Type emerge --help config for more details. The (overly) simple answer is that if a package installs foo somewhere under /etc, and another foo already exists there, then the new foo will instead be renamed to ._cfgxxxx_foo in that directory. A useful tool for examining and updating any protected config files is etc-update, which is now part of Portage.

Yes, but it is not trivial. First do man ebuild followed by ebuild foo-x.y.z.ebuild unpack. Then cd to /var/tmp/portage/foo-x.y.z/work. You can manually perform the ./configure and make steps yourself (you'll have to do both, since Portage does not separate the configure and build steps). To have Portage finish the installation (so that you can easily remove it later, should you desire to do so, and it will be registered in Portage as a possible dependency) you first need to touch /var/tmp/portage/foo-x.y.z/.compiled (tricking Portage into thinking that ebuild foo-x.y.z.ebuild compile has completed), followed by ebuild foo-x.y.z.ebuild merge.

If you're behind a firewall that doesn't permit rsync traffic, then you can use emerge-webrsync which will fetch and install a Portage snapshot for you through regular HTTP. emerge-webrsync uses wget to download, so proxy is fully supported.

~# emerge-webrsync

(First download the snapshot and place it in /usr)
~# cd /usr
~# mv /usr/portage/distfiles /usr/distfiles-temp
~# rm -rf /usr/portage
~# tar xvjf portage-foo.tbz2
~# mv /usr/distfiles-temp /usr/portage/distfiles

Edit the PROXY settings in /etc/make.conf. If that doesn't work, edit /etc/wget/wgetrc and edit http_proxy and ftp_proxy appropriately.

There's a program called unison that works under both UNIX and Win32, available from http://www.cis.upenn.edu/~bcpierce/unison/.

Definitely. You can run emerge --pretend package to see what programs are going to be installed. To find out the sources for those packages and where to download the sources from, you can run emerge -fp package. Download sources and bring them on any media home. Put the sources into /usr/portage/distfiles and run emerge package to see it picking up the sources you just brought in!

Yes, you can safely delete these files. But if you are on a slow connection, such as a modem, you might want to keep the archives if possible; often several ebuilds will be released for the same version of a specific piece of software - if you have deleted the archive and you upgrade the software it will have to be downloaded from the internet again.

Solution:

# emerge unmerge blackdown-jre blackdown-jdk   
# CONFIG_PROTECT="" emerge blackdown-jdk 
		

This is most probably because your user account doesn't have a valid shell specified. Check for your user entry in /etc/passwd and see if it ends in /bin/bash (or any other shell). If it doesn't, you must set a shell for the user. This is done using the usermod command, like this ;

# usermod -s /bin/bash myuser

Your /tmp directory has the wrong permissions (it needs the sticky bit set). Type the following as root:

# chmod 1777 /tmp

Edit the KEYMAP variable in /etc/rc.conf. Then either reboot or restart the keymaps script: /etc/init.d/keymaps restart.

/etc/resolv.conf has the wrong permissions; chmod it as follows:

# chmod 0644 /etc/resolv.conf

You need to add --login to the first line in /opt/kde2.1/bin/startkde , so that it reads as follows:

#!/bin/sh --login

This fix has been added to recent versions of KDE.

You need to add that user to the cron group.

If you log on graphically, or want numlock to be activated when you issue startx, then you must emerge numlock and add /usr/X11R6/bin/numlockx to /etc/X11/xinit/xinitrc (for startx) or /etc/X11/xdm/Xsetup_0 (for any graphical login manager).

If you work in commandline, you only need to rc-update add numlock default and numlock will be activated on the next reboot.

If your ReiserFS partition is corrupt, try booting the Gentoo Linux boot CD and run reiserfsck --rebuild-tree on the corrupted filesystem. This should make the filesystem consistent again, although you may have lost some files or directories due to the corruption.

To view multilog (Gentoo Linux 1.0_rc5 and earlier) timestamps, you need to pipe the current log through the tai64nlocalcommand:

# tai64nlocal < /var/log/syslog.d/current | less

Or, alternatively, if you want to "tail" the log:

# tail -f /var/log/syslog.d/current | tai64nlocal

For bugs within a specific program, contact the program's author. Otherwise, use our Bugzilla bug tracker at http://bugs.gentoo.org. You can also visit us in #gentoo on the FreeNode IRC network.

New releases are announced on the gentoo-announce mailing list, In reality the packages themselves are updated shortly after the main authors release new code. As for when new Cd images etc are released, that tends to be whenever there are any major updates to the base code, or when new modules get added.

Head over to http://bugs.gentoo.org and submit a new bug of the type "ebuild". Attach your ebuild to the bug report.

Submit a new bug over at http://bugs.gentoo.org and add it to the "Docs-user" product, "Gentoo Linux FAQ" component.

Export WANT_AUTOMAKE_1_4=1 for all KDE projects before running make -f Makefile.cvs. Also, for KDE2 apps export WANT_AUTOCONF_2_1=1, and for KDE3 apps export WANT_AUTOCONF_2_5=1.

Console beeps can be turned off using setterm, like this ;

# setterm -blength 0

# setterm -blength 0 >/dev/vc/1

http://cr.yp.to/daemontools.html

The official Gentoo documentation can be found on http://www.gentoo.org; general Linux information is at http://www.linuxdoc.org.

Yes! Fresh CDRs are available for $5 USD apiece from Cheapbytes.

There are also CDs for sale at tuxcds for a very good price. These people also bounce back a portion of the profits to the Gentoo project, so buy them while they are hot!

The mailing list administrators have decided to go with minimal munging (altering of mail headers), which means that they have decided against altering headers to have replies go to the mailing list. There are various reasons for this. For example, if a subscriber has a full mailbox, the entire list receives notice of this every time that something is posted. Most GUI based mailers have a "reply to all" function. This will ensure that your reply goes to the mailing list as well as the original poster. Most users of text based emailers already know the methods to use, but if you don't, in Pine, there is a "reply to group" option. Setting Mutt to reply to the list is covered in the unofficial documentation at forums.gentoo.org. Some list members do not like this method, but it was very heavily discussed when it went into effect, with arguments on both sides. Eventually the list administrators decided to keep it this way. Discussing it on the mailing list will sometimes bring a polite explanation and other times a rather brusque comment to check the archives. Although the administrators regret the inconvenience that it may cause some users, it is felt that at present it is preferable to the alternative for several reasons, many of these covered here. (There are other eloquent arguments in favor of munging, and yes, the list administrators have seen them.)

A good first step is to browse through the relevant doumentation here, failing that, the various Gentoo Linux mailing lists listed on Google. To search through the Gentoo mailling lists, just enter "lists.gentoo.org foo" to search for "foo". If all else fails, or you just want to hang out with Gentoo folks, visit us on irc: #gentoo on irc.freenode.net.