** Reply to message from Uncle Meat <[EMAIL PROTECTED]> on Fri, 25
Aug 2000 23:30:45 -0500 (CDT)
> On 26-Aug-2000 Statux spoke something to the effect:
> >> use and incorporate that into the new kernel? It's sort of redundant
> >> that
> >> everytime I want to put a new kernel on my system I have to remember
> >> what
> >> kind of sound card/net card I use and compile that in. Isn't there a way
> >> to
> >> capture your current config and use it? I could use a few tips here..
> >
> > Redundant? No. It's just common sense to know everything that's in your
> > system. You want to be a real Linux user, don't you? Well Linux isn't
> > going to do it for you, now is it? :)
>
> Well, there _is_ a way, sorta.
>
> After making a configuration in a source tree for the kernel, there will be
> a file in the top of the directory called .config which is _usually_
> suitable for the next upgrade. But, one needs to be certain to open the
> configuration menus and be sure that nothing new has been added or changed.
>
> I use this method all of the time. It rarely fails. I just make sure to do
> a 'make xconfig' then save and exit. The save and exit has turned out to be
> important as I've had more errors when I failed to do it than when I made
> the effort. <snip>
Rather than your way or using "make oldconfig", I go into
/usr/src/linux/arch/i386 (or whatever platform you are on) and do a "mv
defconfig defconfig.old" and then "cp /usr/src/linux/.config defconfig"
This makes your latest kernel configuration the default for another run
through. Note however that for new kernels, I go through every
configuration option again....call me paranoid.
Jack Bowling
Prince George, BC
mailto:[EMAIL PROTECTED]
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list