On Sun, 02 Jul 2000, Karl J. Runge wrote:
> The tips I use are:
>
> 1) Learn enough about lilo.conf(5) to know how to boot multiple
> linux kernels. That way, if you totally hose things you can
> ALWAYS get back to your old kernel by typo "old" (or whatever tag
> you put in lilo.conf) at LILO's "boot:" prompt.
>
> 2) It really helps to build a new kernel version *different*
> kernel version from the one you are currently running. That
> way the /lib/modules/2.X.Y module dirs are completely
> orthogonal to eachother and you'll never clobber them.
Number 2 is the one I need to figure out (I think). I know how to have
multiple kernels, but the old kernels always complain that the libraries and
System/map don't match. I can do this, I just can't do it right.
> > I
STRONGLY recommend 1). I can't see how people build new kernels w/o > it
(driving w/o brakes IMHO). If you want me to send along my > lilo.conf, let me
know. >
> Karl Runge
>
>
> On Sun, 2 Jul 2000, Tom Rauschenbach <[EMAIL PROTECTED]> wrote:
> >
> > I need to rebuild my kernel to get support for my Zip drive. I'm very
> > reluctant to do this since it took me months to get 16 bit sound to work.
> > If any one has tip on kernel rebuilding I'd love to start a thread on this. How
> > does one specify *changes* to the kernel. Discussion of System.map and modules
> > are especially welcome. Especially if you know what System.map does and even
> > more welcome if you know how to have more than one kernel/set of
> > modules/version of glibc at the same time.
--
Standard is better than better. If your web page cares what browser I'm using
it's broken.
[EMAIL PROTECTED]
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
