Too restrictive permissions on some files prevent non-root build (with KBUILD_OUTPUT) [bug 2669]

Too restrictive permissions on some files prevent non-root build (with KBUILD_OUTPUT) [bug 2669]

[Kalin KOZHUHAROV]

I still cannot understand which is better to post bugs here or on the bugzilla, so I'll try both this time.

http://bugzilla.kernel.org/show_bug.cgi?id=2669

The problem is that several files were not world readable and this prevents non-root builds by using the new KBUILD_OUTPUT variable.

For 2.6.6 the files in question can be found by:
cd /sometempdir
tar xjf linux-2.6.6.tar.bz2
find linux-2.6.6 ! -perm -004 -exec ls -l {} \;

I guess the one that most people need is the linux-2.6.6/drivers/char/agp/isoch.c

To fix your tree you can (safely?) use:
find /usr/src/linux-2.6.6 ! -perm -004 -exec chmod o+r {} \;

No idea how exactly the tarball is build, but there can be a check proces like the above before making it final.

Kalin.

-- 
||///_ o  *****************************
||//'_/>     WWW: http://ThinRope.net/
|||\/<" 
|||\\ ' 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Re: Too restrictive permissions on some files prevent non-root build (with KBUILD_OUTPUT) [bug 2669]

[Pascal Schmidt]

On Thu, 13 May 2004 15:30:14 +0200, you wrote in linux.kernel:

> For 2.6.6 the files in question can be found by:
> cd /sometempdir
> tar xjf linux-2.6.6.tar.bz2
> find linux-2.6.6 ! -perm -004 -exec ls -l {} \;

This can only be a problem when unpacking as root, otherwise all
files are owned by the user running tar, anyway. I guess most
people don't do their kernel work as root... and why should they?

The simple workaround is to unpack the tar archive as the user
planning to run the compile.

-- 
Ciao,
Pascal

Re: Too restrictive permissions on some files prevent non-root build (with KBUILD_OUTPUT) [bug 2669]

[Kalin KOZHUHAROV]

Pascal Schmidt wrote:
> On Thu, 13 May 2004 15:30:14 +0200, you wrote in linux.kernel:
> 
>>For 2.6.6 the files in question can be found by:
>>cd /sometempdir
>>tar xjf linux-2.6.6.tar.bz2
>>find linux-2.6.6 ! -perm -004 -exec ls -l {} \;
> 
> 
> This can only be a problem when unpacking as root, otherwise all
> files are owned by the user running tar, anyway. I guess most
> people don't do their kernel work as root... and why should they?
> 
> The simple workaround is to unpack the tar archive as the user
> planning to run the compile.
> 

Well, I guess you are right, but I prefer (and usually do) a single source tree in /usr/src/linux-2.6.6 as for the kurrent kernel and then other users (i.e. non root) compile with the KBUILD_OUTPUT in other directories.

Why?

Because I compile all my kernels on a single machine (but with distcc running on 4+ boxes) and then install it on the other machines.

Even if these file permissions are note a "real bug" there is no point in only some files being non-world readable (some in the Documentation/ as well).

Kalin.

-- 
||///_ o  *****************************
||//'_/>     WWW: http://ThinRope.net/
|||\/<" 
|||\\ ' 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^