On Wed, 12 Aug 1998, James Maddison wrote:
> I'm starting to get a little frustrated with this issue. Probably
> because I'm confused somewhere here. I am trying to build a custom
> kernel, and I can do that fine. The problem is that the new kernel
> modules don't seem to install correctly. I still have symbolic links to
> all the old modules.
>
I don't know how the standard redhat RPMs work, but I don't have any
symlinks to kernel modules anywhere. The modules are in
/lib/modules/<kernel version>/. ISTR that the redhat initscripts do
something wierd with /lib/modules/prefered or something... ?
> As root (not su'd to root) I enter the /usr/src/linux directory. Then I
You don't actually need to be root at all, but that's a side issue.
> 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.
IMHO menuconfig is easier to use (and faster), but it is entirely a matter
of personal prefernce. Also, you only need to make mrproper once, and
[menu|x]config if you are actually changing anything, but again it won't
stop it working.
>
> The following is what I do next:
>
> make dep
> make clean
(you only need to do these two if you have changed the config, but they
won't stop it working. If you don't do them it saves a lot of time on the
rest of the compile)
> 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
>
No, it is right. Basically you are deleting the old backup before
doing...
> mv /lib/modules/2.0.35-2 /lib/modules/2.0.35-2-old
to make a backup of you current config.
> 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
That looks like you are doing all the right things.
>
> 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.
>
Where exactly are these symlinks, and what are the complaints at boot
times.
> 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
Heheh. I once reconfigure 2.0.32 without a monitor...
> 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.
>
> 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.
>
locate reads from a database that is only updated once a day/week/whatever
so it won't reflect recent changes - use find instead to see them (but it
takes longer to run).
> 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?
>
There should be no problem with deleting everything in /lib/modules and
then recompiling. But if you do this, be warned that if something goes
horribly wrong (like a badly timed powercut...) then you will likely not
be able to boot until you have done make modules_install.
HTH
--
Mike <[EMAIL PROTECTED]>
Either one of us, by himself, is expendable. Both of us are not.
-- Kirk, "The Devil in the Dark", stardate 3196.1
