Right,
and thanks. Maybe that came from the tarball. I've corrected this but this doesn't solve the problem.
Frank
On Mon, 2005-01-31 at 14:02 +0100, Holly Bostick wrote:Frank Schafer wrote:cd /usr/src ls -l lrwxr-xr-x 1 root root 12 Jan 11 11:17 linux -> linux-2.6.10 drwxrwxr-x 19 500 500 4096 Jan 20 23:24 linux-2.6.10 drwxr-xr-x 18 root root 4096 Jan 15 14:25 linux-2.6.10-gentoo-r4 drwxr-xr-x 18 root root 4096 Jan 15 14:19 linux-2.6.9-gentoo-r13
Ummm.. hello... what is this?
drwxrwxr-x 19 500 500 4096 Jan 20 23:24 linux-2.6.10
neither root nor the root group own the kernel source?
That doesn't seem like a good thing.
Holly
So does this then mean that you did not emerge these vanilla sources via Portage (i.e., emerge development-sources or hardened-dev-sources), but rather downloaded the tarball manually?
In which case, is it possible that the kernel-source directory variable is not correctly set (i.e., set to the last kernel emerged by Portage), which would mean that the currently running kernel is not the one returned by ${KV}, because Portage doesn't know about the currently-running kernel)?
Basically, what is in fact the output of the $KV variable? What version folders exist in /lib/modules? Where is the ebuild really looking for the source files it needs to compile against? It seems to be time for a visual check of the existence and ownership of the files in question.
Also, did you adjust the ownership of that kernel source folder recursively (so that ownership of all the files inside the folder was changed as well)?
HTH, Holly
-- gentoo-user@gentoo.org mailing list
