Gentoo Linux/PPC 1.2 Installation Instructions Contents: 1.About the Install This new boot CD will boot any New World Macs. OldWorld style Macs will need to have a working MacOS partition, and use the Gentoo Installer.sit provided on the ISO. The ISO I downloaded, http://www.ibiblio.org/pub/Linux/distributions/gentoo/experimental/ppc/livecd/livecd-ppc-281202.iso did not have a file by this name, anything with a .sit extension, or anything I was able to open with Stuffit Exander. In addition, we provide built in kernel drivers for most Apple hardware, as well as tools to allow you to configure your network and establish outbound ssh connections and download files. To install from the build CD, you will need to have a PowerPC 603 or better processor on a PowerPC PCI based system or newer, This makes the Old World situation confusing. I have a 604 that's Old World (At this time Nubus machines are unsupported) and ideally at least 128 Megabytes of RAM. Less than this is possible, but the build process is awfully slow under those conditions and could die.) To begin the install process, first grab one of our CD ISO images from http://www.ibiblio.org/gentoo/releases/build/. In the case of Gentoo 1.4 you will find not only generic PPC images and stage tarballs, but also G4 optimized versions. I did not have anything in the stage directory on the CD I built, and used wget to get a tarball Now, let's quickly review the install process. We'll create partitions, create our file systems, and extract either a stage1, stage2 or stage3 tarball. If we are using a stage1 or stage2 tarball, we will take the appropriate steps to get our systems to stage3. Once our systems are at stage3, we can configure them (tweaking config files, installing a bootloader, etc) and boot them and have a fully-functional Gentoo Linux system. Depending on what stage of the build process you're starting from, here's what's required for installation: stage tarball requirements for installation 1 partition/file system setup, emerge rsync, bootstrap, emerge system, emerge ppc-sources, final configuration 2 partition/file system setup, emerge rsync, emerge system, emerge linux sources, final configuration 3 partition/file system setup, emerge rsync (optional), final configuration 2.Booting Once you've chosen the CD you want to use, go ahead and boot it either by holding down the 'C' key at bootup or by running the OldWorld installer and then launching BootX. You'll be greeted with a bunch of text and a boot: prompt at the bottom of the screen. At this prompt, hit enter, and Linux will begin to load from the CD. I'm not sure what settings were supposed to come with BootX, as I couldn't it from the CD and used a version I already had. I ran into a problem at this point. I tried following the install documentation I found and got some advice. At first I thought the documentation was suggesting I copy livecd.img to my harddrive, which resulted in a kernel panic. Next I tried to point to livecd.img on the CD. The installer either couldn't find it (if it was the Mac view of the disk) or I got an error that I was trying to get to something beyond the machine. So I copied the contents of the CD to the HD and pointed at it. I also increased the # you set in BootX (can't remember what it is now) to 24000. Next, you'll be greeted with a small list of commands available on the boot CD, Didn't get this. Got a prompt to log into the livecd. Took a few minutes to try root and enter. Once I did that it loaded modules and such, but did not ask me about it. I ended up at a prompt. including nano (a pico editor clone) and instructions for setting up the network. Then, you'll be prompted to select your preferred keymap, followed by PCI autodetection. The PCI autodetection process will automatically load the appropriate kernel modules for many popular PCI SCSI and ethernet devices. After this, you can hit enter to enter the minimal boot CD Linux environment. You should have a root ("#") prompt on the current console, and can also open new consoles by typing ctrl+alt-f2, ctrl+alt-f3 (on powerbooks/ibooks possible fn+ctrl+alt+f2), etc and then hitting enter. 3.Load kernel modules We're almost ready to begin installing Gentoo Linux, and for the most part the Gentoo PPC ISO kernel includes any drivers you will need on most standard Macs, but should we need any extras we have included a few modules as well. To view a list of all modules included look in /lib/modules/*/kernel/drivers/*. To load a particular module, type: Code listing 3.1 # modprobe modulename (replace modulename with your desired module) 4.Configure and Install networking The new boot CDs allow you to configure a working network, allowing you to use ssh, scp or wget as needed before even beginning the installation process. Even if you don't need to do these things now, you should go ahead and set up networking now. Once set up, Portage will be able to use your configured network once you are inside the chroot environment (required for installing Gentoo Linux). DHCP Network configuration is simple with DHCP; If your ISP is not using DHCP, skip down to the static configuration section below. Code listing 4.1: Network configuration with DHCP # dhcpcd eth0 Note: Some ISPs require you to provide a hostname. To do that, add a -h myhostname flag to the dhcpcd command line above. If you receive dhcpConfig warnings, don't panic; the errors are most likely cosmetic. Skip down to Network testing below. Static configuration We need to setup just enough networking so that we can download sources for the system build, as well as the required localhost interface. Type in the following commands, replacing $IFACE with your network interface (typically eth0), $IPNUM with your IP address, $BCAST with your broadcast address, and $NMASK with your network mask. For the route command, replace $GTWAY with your default gateway. Code listing 4.2 # /sbin/ifconfig $IFACE $IPNUM broadcast $BCAST netmask $NMASK # /sbin/route add -net default gw $GTWAY netmask 0.0.0.0 metric 1 Now, it's time to create the /etc/resolv.conf file so that name resolution (finding Web/FTP sites by name, rather than just by IP address) will work. Note: At the moment the only editor installed by default is nano, a small and very easy-to-use visual editor. Use nano with the -w option to turn off automatic line-wrapping. Here's a template to follow for creating your /etc/resolv.conf file: Code listing 4.3: /etc/resolv.conf template domain mydomain.com nameserver 10.0.0.1 nameserver 10.0.0.2 Replace 10.0.0.1 and 10.0.0.2 with the IP addresses of your primary and secondary DNS servers respectively. Network testing Now that your network has been configured, the /sbin/ifconfig -a command should show (hopefully!) that your network card is working (look for UP and RUNNING in the output). Code listing 4.4: /sbin/ifconfig for a working network card eth0 Link encap:Ethernet HWaddr 00:50:BA:8F:61:7A inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::50:ba8f:617a/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1498792 errors:0 dropped:0 overruns:0 frame:0 TX packets:1284980 errors:0 dropped:0 overruns:0 carrier:0 collisions:1984 txqueuelen:100 RX bytes:485691215 (463.1 Mb) TX bytes:123951388 (118.2 Mb) Interrupt:11 Networking is go! Networking should now be configured and useable. You should be able to use the included ssh, scp and wget commands to connect to other machines on your LAN or the Internet. 5.Set up partitions Now that the kernel can see our network card and disk controllers, it's time to set up disk partitions for Gentoo Linux. Here's a quick overview of the standard Gentoo Linux partition layout. We're going to create at least three partitions: a swap partition, a root partition (to hold the bulk of Gentoo Linux), and a special bootstrap partition. The bootstrap partition is designed to hold the YABOOT boot loader information. OldWorld users do not require this bootstrap partition as their machine is initally booted by MacOS, and BootX is used to initialize the linux kernel and init scripts. Now, on to file system types. Right now, you have four file system options: XFS, ext2, ext3 (journaling) and ReiserFS. ext2 is the tried and true Linux file system but doesn't have metadata journaling. ext3 is the new version of ext2 with both metadata journaling and ordered data writes, effectively providing data journaling as well. Either one of these is the recommended type to use for GentooPPC. ReiserFS and XFS are both newer high performance File systems, but are more experimental on PPC in general and are not reccomended. Note: At this point, create your partitions using mac-fdisk, mac-fdisk /dev/hdx (where x is your drive letter, a, b, c - /dev/sdx for scsi disks). You will need to make at a minimum a bootstrap partition (b in mac-fdisk) (New World users only), a swap partition (generally 2* ram in your box is good, however I would reccomend at least 512MB swap parititon if you plan on compiling any large packages), and a root partition. ? at the prompt of mac-fdisk will give you a list of options. The basics of mac-fdisk would be nice here. Like how to look at the partition map. Once you've created your partitions using mac-fdisk, it's time to initialize the file systems that will be used to house our data. Initialize swap as follows: Code listing 5.1 # mkswap /dev/hda3 You can use the mke2fs command to create ext2 file systems: Code listing 5.2 # mke2fs /dev/hda4 If you'd like to use ext3, you can create ext3 file systems using mke2fs -j: Code listing 5.3 # mke2fs -j /dev/hda4 Warning: Again, we do not recommend ReiserFS and XFS at this time. While ReiserFS and XFS have worked fine for many, file system corruption has been too common a problem with ReiserFS, XFS on PPC and the 2.4.x series kernels. Note: You can find out more about using ext3 under Linux 2.4 at http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html. 6.Mount partitions Now, we'll activate our new swap, since we may need the additional virtual memory that provides later: Code listing 6.1 # swapon /dev/hda3 Next, we'll create the /mnt/gentoo mountpoint, and we'll mount our file system to this mountpoint. Code listing 6.2 # mkdir /mnt/gentoo # mount /dev/hda4 /mnt/gentoo If you are setting up Gentoo Linux with a separate /usr or /var, these would get mounted to /mnt/gentoo/usr and /mnt/gentoo/var, respectively. 7.Mounting the CD-ROM Even though we've booted from the CD-ROM, the CD-ROM itself is not mounted under our minimal Linux boot CD environment. We'll need to mount it so that we can access the compressed build image tarball contained on the CD-ROM. To mount the CD-ROM, one typically types: Code listing 7.1 # mount /dev/cdroms/cdrom0 /mnt/cdrom -o ro -t iso9660 With the CD-ROM mounted, you should be able to see the stage???.tbz2 file(s) by typing ls /mnt/cdrom/build. Note: If you are unable to mount your cdrom, it is still possible to retrieve the stage1/2/3 from the ibiblio site using wget http://www.ibiblio.org/pub/Linux/distributions/gentoo/releases/build/1.2/stage1-ppc-1.2.tbz2 8.Unpack the stage you want to use Now it's time to extract the compressed stage tarball of your choice to /mnt/gentoo. Then, we'll chroot over to the new Gentoo Linux build installation. Important: Be sure to use the p option with tar. Forgetting to do this will cause certain files to contain incorrect permissions. Important: If you are using the "from scratch, build everything" install method, you will want to use the stage1-ppc-1.2.tbz2 image, however you'll also have a choice of a stage2 and stage3 image. These images allow you to save time at the expense of configurability (we've already chosen compiler optimizations and default USE variables for you.) The stage3 image now also includes a Portage tree snapshot, eliminating the need to do an emerge rsync later. Code listing 8.1 # cd /mnt/gentoo # tar -xvjpf /mnt/cdrom/build/stage?-*.tbz2 # mount -o bind /proc /mnt/gentoo/proc # cp /etc/resolv.conf /mnt/gentoo/etc/resolv.conf Code listing 8.2 # chroot /mnt/gentoo /bin/bash # env-update >>> Regenerating /etc/ld.so.cache... # source /etc/profile # After you execute these commands, you'll be "inside" your new Gentoo Linux environment. 9.Rsync Now, you'll need to run emerge rsync which will connect to rsync.gentoo.org and download the latest version of our Portage ports tree: Code listing 9.1 # emerge rsync The Portage tree will be downloaded; it's about 10Mb in size. Important: The address for the rsync server is currently rsync://rsync.gentoo.org/gentoo-portage. If you have trouble accessing Gentoo rsync, make sure you're using this address by setting it as the SYNC variable in your /etc/make.conf. Note: The rsync command can be configured to use an HTTP proxy if you are behind a firewall. To configure this item set RSYNC_PROXY="hostname:port" in /etc/make.conf or set it as an environment variable. 10.Progressing from stage1 to stage2 Important: If you are a stage2 or stage3 tarball, then we've already bootstrapped for you. There is no reason for you to bootstrap again, unless you decided to do an emerge rsync and want to ensure that you have an up-to-the-minute current Gentoo Linux system. Most people using stage2 or stage3 tarballs will not want to bootstrap again, since it can take up to an hour even on very fast machines. Now that you have a working copy of the Portage tree, people using stage1 to install will need to bootstrap their Gentoo Linux system as follows. First edit the file /etc/make.conf. In this file, you should set your USE flags, which specify optional functionality that you would like to be built into packages; generally, the defaults (an empty or unset USE variable) are fine. You also should set appropriate CHOST, CFLAGS and CXXFLAGS settings for the kind of system that you are creating (commented examples can be found further down in the file.) If necessary, you can also set proxy information here if you are behind a firewall. Code listing 10.1 # nano -w /etc/make.conf (Adjust these settings) Note: People who need to substantially tweak the build process should take a look at the /etc/make.globals file. This file comprises gentoo defaults and should never be touched. If the defaults do not suffice, then new values should be put in /etc/make.conf, as entries in make.conf override the entries in make.globals. If you're interested in tweaking USE settings, look in /etc/make.profile/make.defaults. If you want to turn off any USE settings found here, add an appropriate USE="-foo" in /etc/make.conf (to turn off the foo USE setting.) Now, it's time to start the "bootstrap" process. This process will last 1-4 hours depending on how zippy your machine is. During this time, the extracted build image will be prepped for compiling the rest of the system. The GNU compiler suite will be built, as well as the GNU C library. These are time consuming builds and make up the bulk of the bootstrap process: Code listing 10.2 # cd /usr/portage # scripts/bootstrap.sh The "bootstrap" process will now begin. Note: Portage by default uses /var/tmp during package building, often using several hundred megabytes of temporary storage. If you would like to change where Portage stores these temporary files, set a new PORTAGE_TMPDIR before starting the bootstrap process, as follows: Code listing 10.3 # export PORTAGE_TMPDIR="/otherdir/tmp" The bootstrap.sh will build binutils, gcc, gettext, and glibc, rebuilding binutils, gcc, and gettext after glibc is built. Needless to say, this process takes a while. Have a nice nap. Once this process completes, your system will be in a "stage2" state. 11.Progressing from stage2 to stage3 Note: If you haven't done so, please edit /etc/make.conf to your flavor. Once your build image has been bootstrapped and you're at stage2 (again, if you're using a stage3 tarball than these steps are not required) it's time to build or install the rest of the base system as follows: Code listing 11.1 # export CONFIG_PROTECT="" # emerge --pretend system [lists the packages to be installed] # emerge system Note: The export CONFIG_PROTECT="" line ensures that any new scripts installed to /etc will overwrite the old scripts (stored in sys-apps/baselayout), bypassing Portage's new config file management support. Type emerge --help config for more details. It's going to take a while to finish building the entire base system. Your reward is that it will be thoroughly optimized for your system. The drawback is that you have to find a way to keep yourself occupied for some time to come. The author suggests "Star Wars - Super Bombad Racing" for the PS2. When emerge system completes, you'll have a stage3 Gentoo Linux system. 12.Final steps: timezone Note: If you haven't done so, please edit /etc/make.conf to your flavor. At this point, you should have a stage3 system that's ready for final configuration. We'll start this process by setting the time zone. By setting the time zone before building the kernel we ensure that users get reasonable uname -a output. Look for your time zone (or GMT if you using Greenwich Mean Time) in /usr/share/zoneinfo. Then, make a symbolic link by typing: Code listing 12.1 # ln -sf /usr/share/zoneinfo/path/to/timezonefile /etc/localtime 13.Kernel, system logger, and cron You will now need to emerge the ppc kernel sources, this can be accomplished with emerge sys-kernel/ppc-sources. Once you have a Linux kernel source tree available, it's time to compile your own custom kernel: Code listing 13.1 # cd /usr/src/linux # make menuconfig # make dep && make clean vmlinux modules modules_install # cp vmlinux System.map /boot Note: You should _only_ use the sys-kernel/ppc-sources gentoo kernels on PowerPC based machines. Warning: For your kernel to function properly, there are several options that you will need to ensure are in the kernel proper -- that is, they should be enabled and not compiled as modules. You will need to enable the "Code maturity level options --> Prompt for development and/or incomplete code/drivers" option to see several of these selections. Under the "File systems" section, be sure to enable the Device File System (note that you don't need to enable the "/dev/pts file system support" option). You'll also need to enable the Virtual Memory File system. Also under Macintosh Device Drivers make sure to disable the default of Support for ADB raw keycodes. Also make sure to disable the Enhanced RTC option (in "Character devices") as it's not PPC friendly ATM. But turn on Support for /dev/rtc in "General setup". It's always a good idea to leave ext2 enabled whether you are using it or not. Users with OldWorld machines will want HFS support so they can copy compiled kernels to the MacOS partition. Important: If you have an IDE cd burner and/or DVD, then you need to enable SCSI emulation in the kernel. Turn on "ATA/IDE/MFM/RLL support" ---> "IDE, ATA and ATAPI Block devices" ---> "SCSI emulation support" (I usually make it a module), then under "SCSI support" enable "SCSI support", "SCSI CD-ROM support" and "SCSI generic support" (again, I usually compile them as modules). If you also choose to use modules, then echo -e "ide-scsi\nsg\nsr_mod" >> /etc/modules.autoload to have them automatically added at boot time. You should also add this line to your /etc/yaboot.conf file append="hdc=ide-scsi". Important: If you have an OldWorld machine you will need to mount your HFS (MacOS) partion, then copy your kernel over so BootX can load it at startup. BootX will automatically find kernels in the Linux Kernels folder in the Sytem Folder. This should be explained a lot more. Maybe move the /etc/fstab info up here, or this part down there. Tell people how to make an entry for their Mac partition, what the kernel is called and where to find it, and how to copy over Your new custom kernel (and modules) are now installed. Now you need to choose a system logger that you would like to install. We offer sysklogd, which is the traditional set of system logging daemons. We also have metalog. Power users seem to gravitate away from sysklogd (not very good performance) and towards metalog. If in doubt, you may want to try metalog, since it seems to be quite popular. To merge your logger of choice, type one of the next two lines: Code listing 13.2 # emerge app-admin/sysklogd # rc-update add sysklogd default or # emerge app-admin/metalog # rc-update add metalog default Warning: If you used the version 1.2 stage3 tarball you do not need to install a system logger. stage3-ppc-1.2.tbz2 includes sysklogd (although older and newer versions do not). If you would like to use metalog instead, you will first need to remove sysklogd: After installation is complete, prevent sysklogd from running at startup with rc-update del sysklogd default. Then emerge unmerge sysklogd to remove it. You will probably also have to manually delete the sysklogd configuration files in /etc (look for cfgpro in the file list while unmerging). To install metalog, run emerge metalog, then rc-update add metalog default. This warning should be above the instructions, otherwise people see it after they've started doing the other thing Important: Metalog flushes output to the disk in blocks, so messages aren't immediately recorded into the system logs. If you are trying to debug a daemon, this performance-enhancing behavior is less than helpful. When your Gentoo Linux system is up and running, you can send metalog a USR1 signal to temporarily turn off this message buffering (meaning that tail -f /var/log/everything/current will now work in real time, as expected), and a USR2 signal to turn buffering back on again. Now, you may optionally choose a cron package that you'd like to use. Right now, we offer dcron, fcron and vcron. If you don't know which one to choose, you might as well grab vcron. They can be installed as follows: Code listing 13.3 # emerge sys-apps/dcron # crontab /etc/crontab or # emerge sys-apps/fcron # crontab /etc/crontab or # emerge sys-apps/vcron # crontab /etc/crontab For more information how how cron works under Gentoo Linux, see this announcement. 14.Install additional packages If you're a laptop user and wish to use your pcmcia slots on your first real reboot, you'll want to make sure you install the pcmcia-cs package. Code listing 14.1 # emerge sys-apps/pcmcia-cs 15.Final steps: system configuration Final steps: /etc/fstab Your Gentoo Linux system is almost ready for use. All we need to do now is configure a few important system files and install the yaboot boot loader. The first file we need to configure is /etc/fstab. Remember to specify ext2 or ext3 file system types as appropriate. Use something like the /etc/fstab listed below, but of course be sure to replace "ROOT" and "SWAP" with the actual block devices you are using (such as hda2, etc.). Note that NewWorld users do _not_ add your bootstrap partition to this file. Code listing 15.1: /etc/fstab # /etc/fstab: static file system information. # # noatime turns of atimes for increased performance (atimes normally aren't # needed; notail increases performance of ReiserFS (at the expense of storage # efficiency). It's safe to drop the noatime options if you want and to # switch between notail and tail freely. # <fs> <mountpoint> <type> <opts> <dump/pass> /dev/ROOT / ext3 noatime 0 1 /dev/SWAP none swap sw 0 0 /dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0 proc /proc proc defaults 0 0 Remove the boot line from the /etc/fstab that's installed, add a line for the Mac partition, and explain that people have to replace ROOT and SWAP Final steps: set the root password Before you forget, set the root password by typing: Code listing 15.2 # passwd Final steps: /etc/hostname Edit this file so that it contains your fully-qualified domain name on a single line, i.e. mymachine.mydomain.com. Final steps: /etc/hosts This file contains a list of ip addresses and their associated hostnames. It's used by the system to resolve the IP addresses of any hostnames that may not be in your nameservers. Here's a template for this file: Code listing 15.3: /etc/hosts 127.0.0.1 localhost # the next line contains your IP for your local LAN, and your associated machine name 192.168.1.1 mymachine.mydomain.com mymachine Final network configuration Add the names of any modules that are necessary for the proper functioning of your system to /etc/modules.autoload file (you can also add any options you need to the same line.) When Gentoo Linux boots, these modules will be automatically loaded. Of particular importance is your ethernet card module, if you happened to compile it as a module: Code listing 15.4: /etc/modules.autoload sungem Edit the /etc/conf.d/net script to get your network configured for your first boot: Code listing 15.5 # nano -w /etc/conf.d/net # rc-update add net.eth0 default If you have multiple network cards you need to create additional net.ethx scripts for each one (x = 1, 2, ...): Code listing 15.6: Multiple network interfaces # cd /etc/init.d # cp net.eth0 net.ethx # rc-update add net.ethx default If you have a PCMCIA card installed, have a quick look into /etc/init.d/pcmcia to verify that things seem all right for your setup, then add Code listing 15.7 depend() { need pcmcia } on top of your /etc/init.d/net.ethx file, for the pcmcia drivers to be autoloaded whenever your network is loaded. Final steps: configure basic settings (including the international keymap setting) Code listing 15.8: basic configuration # nano -w /etc/rc.conf Follow the directions in the file to configure the basic settings. All users will want to make sure that CLOCK is set to his/her liking. International keyboard users will want to set the KEYMAP variable (browse /usr/share/keymaps to see the various possibilities). 16.Configuring the Boot Loader The main difference you'll find here from x86 Linux is the bootloader. NewWorld machines will use yaboot. OldWorld machines use BootX. yaboot for NewWorld machines Configuring yaboot is a lot like lilo: settings go in /etc/yaboot.conf - here is a sample: Code listing 16.1: /etc/yaboot.conf ## /etc/yaboot.conf ## ## run: "man yaboot.conf" for details. Do not make changes until you have!! ## see also: /usr/share/doc/yaboot/examples for example configurations. ## ## For a dual-boot menu, add one or more of: ## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ ## our bootstrap partition: boot=/dev/hda9 ##hd: is open firmware speak for hda device=hd: partition=11 root=/dev/hda11 delay=5 defaultos=macosx timeout=30 install=/usr/lib/yaboot/yaboot magicboot=/usr/lib/yaboot/ofboot ################# ## This section can be duplicated if you have more than one kernel or set of ## boot options ################# image=/boot/vmlinux label=Linux sysmap=/boot/System.map read-only ################## macos=/dev/hda13 macosx=/dev/hda12 enablecdboot enableofboot Once yaboot.conf is set up how you want it, you run mkofboot -v to install the settings in the bootstrap partition. Don't forget this! If all goes well, and you have the same options as me, your next reboot will give you a simple, five-entry boot menu. If you update your yaboot config later on, you'll just need to run ybin to update the bootstrap partition - mkofboot is for initial setup only. Note: Yaboot has some functionality for setting config at boot time, so take a look at http://penguinppc.org/projects/yaboot for more info. BootX for OldWorld machines Important: Follow these steps after you reboot your machine in the next step. Boot your machine in MacOS and open the BootX control panel. Select Options, and uncheck Used specified RAM disk. When you return to the BootX main screen, you will now find an option to specify your machine's root disk and partition. Fill these in with the appropriate values. BootX can be configured to start Linux upon boot. If you do this, you will first see your machine boot into MacOS then, during startup, BootX will load and start Linux. See the BootX home page for more information. Click on save settings. 17.Installation complete! Now, Gentoo Linux is installed. The only remaining step is to exit the chrooted shell, safely unmount your partitions and reboot the system: Code listing 17.1 # exit // This exits the chrooted shell; you can also type ^D # cd / # umount /mnt/gentoo/proc # umount /mnt/gentoo # reboot Note: After rebooting, it is a good idea to run the update-modules command to create the /etc/modules.conf file. Instead of modifying this file directly, you should generally make changes to the files in /etc/modules.d. 18.Extras Multiple mouse button emulation You may want to add these lines to an /etc/sysctl.conf to enable multiple mouse button emulation at each boot. The key values can be obtained with command line utility showkey. Here is a sample using F11 and F12. Code listing 18.1 # Enable mouse button emulation dev.mac_hid.mouse_button_emulation = 1 # Set 2nd button to 87 - F11 dev.mac_hid.mouse_button2_keycode = 87 # Set 3rd button to 88 - F12 dev.mac_hid.mouse_button3_keycode = 88 Gentoo-Stats The Gentoo Linux usage statistics program was started as an attempt to give the developers a way to find out about their user base. It collects information about Gentoo Linux usage to help us in set priorities our development. Installing it is completely optional, and it would be greatly appreciated if you decide to use it. Compiled statistics can be viewed at http://stats.gentoo.org/. The gentoo-stats server will assign a unique ID to your system. This ID is used to make sure that each system is counted only once. The ID will not be used to individually identify your system, nor will it be mached against an IP address or other personal information. Every precaution has been taken to assure your privacy in the development of this system. The following are the things that we are monitoring right now through our "gentoo-stats" program: * installed packages and their version numbers * CPU information: speed (MHz), vendor name, model name, CPU flags (like "altivec") * memory information (total available physical RAM, total available swap space) * PCI cards and network controller chips * the Gentoo Linux profile your machine is using (that is, where the /etc/make.profile link is pointing to). We are aware that disclosure of sensitive information is a threat to most Gentoo Linux users (just as it is to the developers). * Unless you modify the gentoo-stats program, it will never transmit sensitive information such as your passwords, configuration data, favorite movie... * Transmission of your e-mail addresses is optional and turned off by default. * The IP address your data transmission originates from will never be logged in such a way that we can identify you. There are no "IP address/system ID" pairs. The installation is easy - just run the following commands: Code listing 18.2: Installing gentoo-stats # emerge gentoo-stats // Installs gentoo-stats # gentoo-stats --new // Obtains a new system ID The second command above will request a new system ID and enter it into /etc/gentoo-stats/gentoo-stats.conf automatically. You can view this file to see additional configuration options. After that, the program should be run on a regular schedule (gentoo-stats does not have to be run as root). Add this line to your crontab: Code listing 18.3: Updating gentoo-stats with cron 0 0 * * 0,4 /usr/sbin/gentoo-stats --update > /dev/null The gentoo-stats program is a simple perl script which can be viewed with your favortive pager or editor: /usr/sbin/gentoo-stats. Where to go from here If you have any questions or would like to get involved with Gentoo Linux development, consider joining our gentooppc-user and gentooppc-dev mailing lists (there's a "click to subscribe" link on our main page). We also have a handy Desktop configuration guide that will help you to continue configuring your new Gentoo Linux system, and a useful Portage user guide to help familiarize you with Portage basics. Enjoy and welcome to Gentoo Linux! The Gentoo Linux/PowerPC FAQ covers frequently asked questions about running Gentoo Linux/PPC. The general Gentoo Linux FAQ might also help to get you started, although it is geared towards x86 installations. Gentoo on PPC (on forums.gentoo.org) is a open bulletin-board for discussion of all PowerPC issues. Also, there is usually a lively discussion on IRC. Join us on #gentoo-ppc on irc.freenode.net. Thanks and have fun with Gentoo! Reproducible: Always Steps to Reproduce: 1. 2. 3.
cleanup of old bugs. i think there is still some good info on oldworld machines below (in section 1 and 16) that could be moved to the ppc faq to supplement what is there now. the handbook says "We also provide limited support for OldWorld systems, IBM (RS/6000, iSeries, pSeries, ...) and Amiga systems. Be sure to read up on the Gentoo PPC FAQ before you begin." but the ppc faq has no info on how to boot with BootX, or set it up after install.
The information about BootX has been moved into the handbook itself. I would like to keep this bug with LATER for the planned special OldWorld CD. There are several good information.
I think we've included all of the useful information here and can close this bug.