Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 47604

Summary: Emerge system fails with OSError 13 - permission denied
Product: Gentoo Linux Reporter: Arno <roefs>
Component: [OLD] UnspecifiedAssignee: solar (RETIRED) <solar>
Status: RESOLVED INVALID    
Severity: minor    
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Arno 2004-04-12 06:35:58 UTC
I have a Debian stable system installed. I have 2 different kernels installed, one 2.4.22 and one 2.4.25-grsecurity. I'm trying to install Gentoo in a chroot. First I tried it running the grsecurity kernel, arriving at the 'emerge system' step, this resulted in a OSerror 13: permission denied. I have tried stages 1,2 and 3, all the same error. With kernel 2.4.22, all is fine. It figures that grsecurity is enforcing some security on the chroot that prevents the emerge. This might not be a Gentoo bug, but I thought it was useful as a bug anyways, I found very little info on it on the forums.

Reproducible: Always
Steps to Reproduce:
1. Boot grsecurity kernel, unpack a stage
2. Chroot a shell to install map
3. emerge system

Actual Results:  
OSError 13: permission denied (while performing a chmod operation it seems)

Expected Results:  
Emerge the system.

Really nothing particular, I did not change any settings.
Comment 1 solar (RETIRED) gentoo-dev 2004-04-12 10:35:46 UTC
This should do the trick for ya.

sysctl -a | grep chroot | sed s/' = 1'/=0/g | grep =0 | xargs -n1 sysctl -w

If that does not work then chances are you did not compile your grsec 
kern on deb with Sysctl support. If that is the case then your going to 
need to build a kernel either without the chroot options enabled or 
rebuild with sysctl support so these values can be changed on the fly.
Comment 2 solar (RETIRED) gentoo-dev 2004-04-27 21:23:31 UTC
Arno must of followed instructions and been so happy with his install that he/she 
forgot to come back and comment on this bug :)

Changing resolution to INVALID
Comment 3 Arno 2004-04-28 02:01:55 UTC
Oh hehe, sorry :) 
I booted a non-grsec kernel and installed Gentoo from there, that went fine. I just think maybe there could be a warning somewhere in the Gentoo install manual, that the grsec chroot is too restrictive to install Gentoo on. As the OSerror 13 is quite cryptic.