Point taken, guide has been edited to show this step as 'Optional'. thank you!

still i wonder why you're keeping the " /usr/src/linux-symlink " myth alive ?
i know , even reading the howtos on the ati-site , they advice to check it.
but the build-script uses the " /lib/modules/2.6.10/build " link, which is used by everyone.

it's just a tip.
as any step you can skip is just one less to take.

egag

/usr/src/linux is a myth?
and nobody told me :[


actually, i had thought that it didn't have anything to do with
the kernel compilation...but that it was for easy linking to the
source for third party software compilations. oh well...

I dont trust this guy any farther than i can throw him... not to mention his kernel compile proceadures... wait.. nvm disregard that I thought that was Bill Gates :D

either way.. I see no problem compiling a kernel in /usr/src... I also see no problem compiling it as root... maybe if you are hooked up to the net with no firewall.. but I still doubt anything bad can happen. Although it is what he recommends he doesnt provide any reason why you should not do it.

It has to do with the philosophy that if it doesn't have to be done as root it shouldn't be. Less chance for error and other such trouble.

it's adviced in general not to run a Linux system as root.
that's reason enough..
but also , people following this howto will be ( nearly ) new to kernel compiling and maybe even Linux.
as root you can cause alot of prob's , so i wouldn't advice them to run as root.
( just use "su" when needed and "exit" to get out again )

and for the dir ( /usr/src or ~/ ): you'll have to copy a config file into the src-dir as a starting point and
users don't have wite permissions in /usr.


@acidjuice

there's a typo " Now let's start the operations. Let's move into the /usr/etc directory " , i think it has to be " /usr/src "
and as i read it, it's not clear when and how to copy the config file to the source-tree.
maybe add that command also.

egag

oh , acidjuice, just one more thing,

-------------
The following are my recommended points to follow. Definitely not exhaustive. One last thing: this worked for me. It doesn't mean that it will work for you. Upgrading a kernel may result in the total mess up of your system.
--------------

i think that sound really scary......
if someone follows this guide, there's allways the old kernel to boot.
maybe a more general warning that being "root" you can harm the system or so....

just to make people trust this howto ( as they should... :) )

egag

The statutory warning is always necessary :)

this note has been added to the guide.

absolutely. however i prefer a scared noob to an angry noob wanting to bang my head on a wall :)

i've added your remark to the guide :)

thank you.

absolutely. corrected.

I just used this guide to install the 2.6.10 kernel on my system, and it worked great! However, immediately after I tried to install the nvidia drivers and found out that they search for the file /usr/src/linux-2.6.10/.config. It might be appropriate to change the commands from mv to cp when moving the files to /boot to prevent these kinds of problems. The config files are small enough that duplicate copies wouldn't hurt.

Heck of thing you guys are doing here.
I'll be building one of these kernels in a couple weeks.
I can't wait !

Thanks to all involved.

This is the first time I had seen this, my /etc/modprobe.conf now looks much less sparce.

Thanks

Samac

real glad to read it :)you shouldn't leave the old .config as it points to the old kernel, and the driver might therefore not work. i think it actually points to /usr/src/.config. i personally have modified it to point at /usr/src/config instead (which is one of the symlinks in the optional part of the guide). not sure if this is the best way to go, though.

any input on this welcomed, so i can adjust this guide before final release.