On Mon, Jul 09, 2001 at 08:57:59AM +0100, jac1 wrote:
> Why go to all this bother?
> If you compile a kernel or modules regularly then don't do the 'make clean' or
> 'make mrproper' bits. These just delete the *.o files. If you don't do this,
> the next time you compile the kernel or modules, the makefile will see that
> some of the *.o files already exist and will skip on to the next stage until
> it finds code that hasn't been compiled before. It is only when you are fully
> satisfied with your kernel and modules should you do the 'makr clean' step
I can't think of 2 reasons. I generally don't compile my own kernel, I
prefer to stick with the distro's own but sometimes I want to update a
single module, so I don't have the compiled one lying about.
The other reason is if you build a lot of different kernels (possibly
Kevin's case given that he stores and names his config files, I dunno). They
start taking up plenty of space and this way you only have to keep the
config file,
Fergal
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
