On Sat, May 10, 2008 at 8:13 PM, Daniele Maccari <[EMAIL PROTECTED]> wrote:
> Michael Homer wrote:
>> On 5/10/08, Daniele Maccari <[EMAIL PROTECTED]> wrote:
>>
>>> Ok, I finally solved the problem (if right or wrong, I don't know).
>>> Attached you'll find the patch, please let me know.
>>> This way files on which current user has no permissions should be
>>> correctly managed, as well as globbing (which sudo prevents from
>>> working, since the command is first parsed by shell, and the permission
>>> problem arises).
>>>
>> If it's unpacking with bad permissions just fix them in the hook. The
>> directories should be g+rx. I'm puzzled as to why it wouldn't compile
>> as root then, though.
>> -Michael
>>
> Ok, playing a bit I found out that changing opt and usr directories'
> permission to a+rx apparently solved the problem.
> In the recipe there was though a "chmod -R a+rX usr/share" command,
> which honestly I couldn't understand.
+X is "give execute permission iff the file is a directory (or already
has execute permission for some user)". Which should be sufficient for
everything to work, so I'm puzzled that it wouldn't.
Adding "-R ${SUDO_USER:-`whoami`}" to the cpio command should be the
next step if that still doesn't work.
> It remains the fact, as you pointed out, that in the previous case also
> compiling as root gave problems. Permissions was like these:
> drwx--S--- 4 gobo sys 4096 2008-05-10 10:11 usr
>
> Note the capitalized S for usr and opt group permissions. I can't really
> figure out the problem.
Capital S (in ls output) means the setuid bit is set but the
corresponding execute bit isn't. setgid doesn't do anything for a
directory as far as I know, so it doesn't hurt, but +x is necessary
for the directory to be readable.
It also might help if you posted the recipe you're working with for
others to try or take a look at.
-Michael
_______________________________________________
gobolinux-devel mailing list
[email protected]
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
