khelben1979 schrieb:
> LewsTherinTelemon;1905263 Wrote:
>> Rather than clicking everything in menuconfig, you can save the config
>> to reuse next time, or check and see if you already have a config from
>> your existing kernel to re-use.
Btw you can recover the config your running kernel was built with
by the command “zcat /proc/config.gz”.
> I’ve tried reusing the config file from an existing config file which I
> had when I compiled an older kernel and in this case I’m not sure if
> this is a good thing to do.
In my experience starting from a working config (for example the
one of the currently running kernel) is the best way for creating
a new working config.
> I mean, what if the newer kernel has features which the older kernel
> didn’t have for instance. What are the risks of using an older config
> file together with a newer version of the Linux kernel?
The risk is almost zero. If you run “make oldconfig” over a working
config from an older kernel and answer all questions with their default
(just hit Enter) everything will be set in a backward compatible way
and you’ll almost certainly end up with a kernel that works. You can
then start poking around the new config options to see if there’s
anything worth changing.
> I also don’t understand why it has gotten harder to compile kernels
> after version 2.6.5 was released.
IMHO it hasn’t. It’s gotten easier. Nowadays compiling a vanilla
kernel is almost as simple as compiling an application. Try this:
wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.27.8.tar.bz2
tar -xvjf linux-2.6.27.8.tar.bz2
cd linux-2.6.27.8
← install any patches you like →
zcat /proc/config.gz > .config
make oldconfig
← type Enter to everything you do not understand →
make
sudo make modules_install install
← type root password when prompted →
And voilà, on the next reboot you’ll find a shiny new boot menu entry
for kernel 2.6.27.8 above the previous ones.
Finally, a piece of advice I find sadly lacking in many of the HOWTOs
that have already been cited in this thread: If you compile a vanilla
kernel, do not unpack it to /usr/src, and neither unpack nor compile
it as root. Instead, work under your regular user account, and below
your home directory as described above. Only the last step (install)
needs root privileges, which you can safely acquire temporarily with
sudo.
HTH
T.
–
Tilman Schmidt
Phoenix Software GmbH
Bonn, Germany
often refers to this link (YAM) :