According to James Maddison: While burning my CPU.
>
> Here's what I'm doing which is straight from the RedHat manual and from
> my reading of Kernal HOWTOs and other related HOWTOs.
>
> As root (not su'd to root) I enter the /usr/src/linux directory. Then I
> issue a "make mrpoper" from there. Fine. Then I "startx" so that I can
> use xconfig. Then I type xconfig from there to start making the config
> file for the new kernel. I select all my options from there, then choose
> save and exit. All is fine so far.
>
> The following is what I do next:
>
> make dep
> make clean
> make boot
> make modules
> rm -rf /lib/modules/2.0.35-2-old
>
> NOTE: The above step trouble me. I don't think it's correct. I think
> it should be 2.0.35-2 instead of the same with the -old extension. I
> believe I've tried this both ways though, with the same result
>
> mv /lib/modules/2.0.35-2 /lib/modules/2.0.35-2-old
> make modules_install
> mv /boot/vmlinuz /boot/vmlinuz.old
> cp /usr/src/linux/arch/i386/boot/zImage /boot/vmlinuz
> pico /etc/lilo.conf (to edit the file and check config)
> /sbin/lilo
>
> Okay, all my symbolic links for the modules still refer to the old
> kernel, in this case, 2.0.35-2. Argh! So I get a few complaints in the
> boot messages about that.
Well as far as i recall redhat 5.1 uses rather a different system for
pointing to modules ie, a symlink to the "prefered version number" which is
gained at boottime i think in /etc/rc.d/rc.sysinit and makes a symbolic
link at boottime to match the kernel version number.
So possably by changing the symlink you mess up the boot sequence, thats
just a thought.
If that is correct then that would explane one of your problems.
Now the other thing you are doing is mv /boot/vmlinuz /boot/vmlinuz.old now
that is possably a symlink also, now here you have a few options,
1) remove the symlink in /boot 'rm vmlinuz' copy the new image to boot as
vmlinuz-2.0.35-1 now link it with 'ln -s vmlinuz-2.0.35-1 vmlinuz'
Doing this does not remove the old image, so allowing you to use it in other
ways.
You can do the same with the System.map, but that is not a must as you
possably will never need to use the System.map anyway.
2) Copy the new image to /boot call it what you like, edit /etc/lilo.conf
and enter a complete new entry for the new image, rerun lilo, and at boot
time you can chose between the old image and the new image.
>
> This whole process takes maybe 20 minutes start to finish (I've been
> through the danged config screens so many time now I can do it in my
> sleep). Plus my AMD K6 300 clocked at 342mhz (66 X 5, turbo enabled)
> with 64mb of SDRAM zips right along through the compiling, etc.
Try closing X first before you start to compile, you will then see a quicker
compile.
>
> So it's not a big deal to do this until I get it right...I just want it
> to work correctly dang it. The really strange thing is that I did a
> "locate sound.o" because I downloaded and installed the OSS sound config
> trialware, and I get symbolic links to kernels 2.0.34-6 and 2.0.35.2
> coming up, even after I recursively deleted the directories.
They sound like symlinks then..
>
> How do I get rid of those? I'm assuming that if I can get this right
> that those links will be taken care of. How can I remove them? Is there
> a way to view all the symoblic links that I'm interesed in for the
> kernel and modules? Can I just clean out all the old kernel stuff and
> modules and make the kernel and modules so that I don't have all that
> crap lying around in the directories?
Like i said above i think the boot process will make the nessascary symlink
to the modules, check th script first.
I dont have 5.1 but i have seen a boot script sent to me by
[EMAIL PROTECTED] when he was having a simalar sort of boot
problem.
Of course i cannot say "this is your answer" as i dont have 5.1 here, but it
must be worth a try at least.
>
> Help! :-)
>
> James
>
--
Regards Richard.
[EMAIL PROTECTED]
