floyd@barrow.com (Floyd L. Davidson) wrote in message news:<87r7on9taq.fld@barrow.com>...
> Also, I don't recall that you mentioned which kernel you are
> using, but the 2.6 kernels can be configured to put a config.gz
> pseudo file into /proc. Using that configuration certainly
> makes it easy to keep track of which config file is which!

What's the name of the documentation file for this? I'd like
to know more of this.

> There is essentially *never* any reason for most people to do a
> "make mrproper". It returns the kernel directory to the
> condition it was in the distribution archive. Unless you are a
> kernel developer, and have made changes to the source code which
> need to be archived, that is a worthless condition.

I've been wondering about these for years, so now I'll ask.
What exactly is the difference between mrproper and clean?

As for the kernel tree, once a kernel has been compiled and installed,
am I assuming right that there is nothing that uses the kernel
source tree and that it could either be cleaned or deleted? (I'm not
considering or talking about certain programs that rightly or
wrongly need the current kernel tree to compile,
just the system itself.)

ton