To:                     [EMAIL PROTECTED]
Date sent:              Thu, 23 Dec 1999 03:04:37 EST
Subject:                Re: Compilation problems
From:                   [EMAIL PROTECTED]

> I don't mean to insult you, but if I might save you a bit of grief, I'll
> risk it.  And you did ask in linux-newbie, so maybe you're not too used
> to messing with kernels.
> 
> It seems to me the weakest section of the linux README is the part
> dealing with lilo.  One nice thing about lilo is you can have several
> images to in /etc/lilo.conf, and choose which one at boot time.  I
> always make a new kernel with make zImage, then copy
> /usr/src/linux/arch/i386/boot/zImage to /boot/<different name>.  The
> name is completely up to you, it doesn't have to be zImage, or vmlinuz.
> Of course, each image needs a unique label = associated with it.
> I called the 2.0.36 kernel with the threads patch Wine36.  I'm a cocky
> so-and-so, and I always put a new kernel first in /etc/lilo.conf to make
> it the new default, leaving the old one in case I goofed, but it would
> make sense to put it last so you wouldn't get it except by choosing it
> when you boot.  Don't forget to run /sbin/lilo after, and watch for
> error messages. :-)
> 
> If you use or test with a boot floppy, that's a good way, too.
> 
> Lawson
>         >< Microsoft free environment
> 
> This mail client runs on Wine.  Your mileage may vary.

Hi Lawson!

Nice to hear from you again. But I don't think you intended this 
message to get to me. Anyway, you gave this tip to someone else 
on the list a couple of days ago, and I have already used it. I think 
it is a great tip.

I have another question. The only problem I've found with the new 
kernel is that when it comes to the "Checking module 
dependencies ..." part, it prints a message saying it can't find "char-
major-10". I tried a grep on the entire filesystem looking for "char-
major-10" but my computer hung up. Any ideas about what I can 
do to solve this problem?

As I've told you before, I left the old kernel on my lilo.conf. Now I 
can decide which kernel I want to use at boot time. However, when 
I use the old kernel it gives me all kinds of error messages about 
not being able to find certain modules. I guess that when I 
compiled and installed the new kernel I broke the references to the 
old kernel. I don't want to fix this, because the old kernel is going 
to take a hike to the oblivion soon, but I'd like some pointers to 
docs or an explanation on how the "module references" system 
works.

Thanks in advance,

Jerem�as Galletti

Reply via email to