The only reason a recompile is likely to break a working system is if
the kernel is misconfigured. If the kernel was recompiled without some
option that the original kernel had compiled in it could cause
problems
Andy
On 21 Nov 2000 01:43:32 GMT, un...@physics.ubc.ca (Bill Unruh) wrote:
>In <8vceuc$so9$1...@news.cis.ohio-state.edu> ree...@cis.ohio-state.edu (doug reeder) writes:
>
>
>>I'm recompiling the 2.2.12 kernel to enable support for a
>>parallel port printer. Unfortunately, this breaks everything
>>that's compiled as a modules.
>
>ALL distributions that I have every heard of support parallel port
>printers out of the box. What made you think you should recompile?
>Despite what some of the ancient and outdated howtos say, you almost
>never should recompile your kernel. You will almost always make things
>worse, rather than better.
>(Yes, it is possible to recompile one's kernel and have it work.
>)
>
> The only reason a recompile is likely to break a working system is
> if the kernel is misconfigured. If the kernel was recompiled without
> some option that the original kernel had compiled in it could cause
> problems
One piece of advice I usually give to users of the Debian GNU/Linux
system is to start from the .config used to build the installed
kernel, which is stored in /boot. That way you're less likely to
forget to install, say, your SCSI disk driver.
The other thing is to use make-kpkg, which makes building and
installing kernels a breeze, and also does nice stuff like storing
your .config in /boot.