On Mon, 07 Jun 2004 03:07:06 +0000, Robert D. De Mars wrote:
> This is what I do.
>
> 1. Log in as root

Why?!? There is no any need to do typical compiling jobs as root. The
more you use that root account the more potential risks you face:
risk of you typing something wrong, risk of someone else having typed
something wrong, or worse: a deliberate trojan.

> 2. Download the full kernel source code from

If a vulnerability existed in your FTP/HTTP client, a hostile server
could exploit you. This kind of thing happens to Windows/MSIE users
every day.

> www.kernel.org. The current stable kernel at this time is 2.6.2.

?!?!? It's 2.6.6, as the OP noted.

The rest of this is basically good advice, however:

> option. Since my kernel source code is in /root/linux-2.6.2, I
> will save my output files to /root/build/kernel. I believe an
> added bonus to this option is the next time I run "make mrproper"
> in my new /root/linux-2.6.2 kernel source, I believe my .config
> file will remain safely in /root/build/kernel for future purposes

Unless you use the O=/output/dir with that. Also, all your object files
remain, so what you might have wanted from running mrproper in the
first place is not achieved. I'd say that the O=/output/dir benefit is
that you don't need to run make clean or mrproper. If you're doing a
different ARCH or dramatically different configurations, specify a
different output directory.
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply