Adam Getchell <[EMAIL PROTECTED]> wrote:
>First, thanks to all that responded with help for compiling the kernel. With
>this help, I was able to successfully compile and install a working kernel.
And doesn't that make you feel good! Woo-hoo!!!
>Here are my notes I collected on the process, from FAQs, the README, and your
>commentary. I'm interested to know if I've got the procedure down, and more
>importantly, what steps are/are not optional.
>Kernel numbering convention (<kernel number>): kernel-version.YYYY.MM.DD.V
> Example: 2.2.13-20.1999.11.19.2
This was my numbering/dating convention and now that I've re-read the
message I send I realize there should be dashes between the date and not
dots like so: kernel-version.YYYY-MM-DD.V FYI - this is a numbering
convention I made up for my own use - don't know if anyone else uses it or
not. If it helps you, use it. If not, feel free to make up your own. ;-)
><your root mount point>: location of /boot/
I'm not sure what this is refering to...
>Optional steps in ()'s. Steps I'm not sure are optional are not have ?
>Kernel assumed to reside in /boot/
It's normally there, although I supposed if you edited /etc/lilo.conf you
could put it elsewhere.
>unpack sources in /usr/src
Or use the RPM which should put them there by default.
>(make mrproper)
I generally do 'make clean' and 'make mrproper'. They're probably
unnecessary if you know your kernel build tree is clean - I usually do it
just to be on the safe side.
>make config/menuconfig/xconfig depending on preference
> (if xconfig, save kernel config file as config-<kernel number>)
Again, my own made-up numbering scheme. You can save your config file when
using menuconfig or xconfig, but not config.
>(inspect Makefile)
Especially if you need to enable SMP support.
>make dep
>make clean
>make bzimage/bzdisk
I *think* it's 'make bzImage' but I can't remember off the top of my head.
>make modules
>(backup modules directory if same kernel version)
Only if you want to keep old modules to go with your old kernel(s)
>make modules_install
You'll also need make sure the soft link in /lib/modules is pointing to the
correct modules directory if you're using my kernel/modules numbering
scheme. Otherwise you'll get unresolved module depencencies.
>make install
>(make checkconfig)
>(make checkhelp)
Never used these three. Maybe someone else can shed some light on what
they're for.
>cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-<kernel number>
>edit lilo.conf
> add image-/boot/vmlinuz-<kernel number>
> label=linux
> root=/dev/<your root mount point>
> read-only
> modify previous label=linux to label=linux.old, etc.
>lilo
I'd run lilo -v (for verbose) just to be on the safe side. When the 2.2.x
kernels began getting too large for lilo to handle without 'make bzImage'
running lilo in verbose mode warned me - otherwise I wouldn't have known
until I rebooted, which could have been messy.
>(rm -rf /usr/include/linux /usr/include/asm) ?
>(ln -sf /usr/src/linux/include/linux /usr/include/linux) ?
>(ln -sf /usr/src/linux/include/asm /usr/include/asm) ?
Never run these three either.
>(depmod -a) ?
Don't think this is necessary - I believe it gets done during bootup.
>cp /usr/src/linux/System-map /boot/System.map-<kernel number>
>rm /boot/System.map
>ln -s System.map-<kernel number> System.map
I don't think this is necessary either. As above, I think it gets sorted
out during boot.
-Eric
Eric Sisler
Library Computer Technician
Westminster Public Library
Westminster, CO, USA
[EMAIL PROTECTED]
Linux - don't fear the Penguin.
Want to know what we use Linux for?
Visit http://gromit.westminster.lib.co.us/linux
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
