by jdos2 » 06 Jan 2005, 02:21
My personal steps (learned from Slackware, 1995):
1. Get the kernel sources. I'm at 2.6.10. The GLibC with YDL is FINE for it.
2. Gunzip and untar in /usr/src, and the create a symbolic link to "linux" in that same directory.
3. Enter the linux directory and "make mrproper."
Now, I have some choices, and when I'm lazy (most of the time) I'll copy a config file from /boot that matches my running (and assumed working) kernel into my /usr/src/linux directory, as .config.
4. I usually run "make menuconfig" and flow through the options. Remember, Olde Linux Hands, that this is NOT i386 Linux, and the Kernel can be large. Compile in what you need, module what's optional, and You Are There.
5. Compile (make all)
6. Install the modules (make module_install)
7. Install the Kernel (cp vmlinux /boot)
8. Adjust yaboot.conf to include the appropriate info about your kernel- the image is, of course, /boot/vmlinux. Don't worry about an initrd, this isn't i386 and your filesystems that are needed for boot really should be compiled in anyway.
9. Run /sbin/ybin.
10. Reboot. At the second stage loader, press <Tab> and you will see your kernel image listed, assuming that you correctly entered the info in your yaboot.conf (it's really easy to make a typo; if you don't see your kernel, betcha you did)
11. Enjoy your new kernel.
Piece of cake, and really, standard practice for any Linux admin. Any admin user should be good enough at it that they can upgrade, in my opinion. Then again, I hate precompiled binaries and prefer to work with gcc 3.4.3... But the installation of the latter is rather more involved.
JD