Hmm,
I did the build step as root. (so I probably thought the permissions  
where set OK)

So that means if I use -U,
the build will only at install phase set the permissions ?
(Is that to prevent having privileged executables in non-secure locations ?)

thilo


cube@cubidou.net wrote:

>On Thu, Oct 14, 2004 at 11:15:11PM +1000, thilo wrote:
>  
>
>>Not quite
>>I run
>>build.sh -U ../obj -T ../tools
>>build.sh -U -T ../tools  ../obj install=/
>>
>>but:
>>bash-2.05# ls -l  obj/destdir.i386//usr/bin/su
>>-r-xr-xr-x  1 root  wheel  19488 Oct 11 00:53 obj/destdir.i386//usr/bin/su
>>bash-2.05#
>>
>>already did not have them
>>    
>>
>
>Of course it did not, you compiled with -U.  That's why it is _critical_
>to pass it to install=/, too, so that the build system will look at the
>METALOG file to set correct permissions.
>
>  
>
>>Is there already a script that fixes them ?
>>    
>>
>
>Check if the METALOG file contains the correct permissions:
>
>./usr/bin/su type=file mode=04555 uname=root gname=wheel [...]
>
>If it is correct, do the install step again, making sure you use -U.  You
>can try building the sets, too (using 'sets' target), and check if the
>permissions are correct in there, too.
>
>Quentin Garnier.
>
>  
>