Summary: | Add note about grsec-kernels, chroots and Gentoo Instalation | ||
---|---|---|---|
Product: | [OLD] Docs-user | Reporter: | Christian Korff <christian.korff> |
Component: | Handbook | Assignee: | Docs Team <docs-team> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Christian Korff
2004-07-06 05:31:00 UTC
Since I´ve got some system trouble I decided to do a stage1 installation.
Everything went okay until emerge system:
# USE="-X -java" emerge system
Calculating system dependencies ...done!
>>> emerge (1 of 84) sys-devel/patch-2.5.9 to /
Traceback (most recent call last):
File "/usr/bin/emerge", line 2599, in ?
mydepgraph.merge(mydepgraph.altlist())
File "/usr/bin/emerge", line 1551, in merge
retval=portage.doebuild(y,"clean",myroot,self.pkgsettings,edebug,cleanup=1)
File "/usr/lib/portage/pym/portage.py", line 2159, in doebuild
os.chmod(mysettings["T"],06770)
OSError: [Errno 13] Permission denied: '/var/tmp/portage/patch-2.5.9/temp'
The trouble was a chmod command:
# chmod 06770 /var/tmp/portage
chmod: changing permissions of `/var/tmp/portage': Permission denied
So the issue is the grsec Patch.
You should maybe add a note about this issue. If someone running a grsec Linux with chroot restrictions he/she may get a issue on emerge system.
To solve this issue is simple:
chmod 06770 /mnt/gentoo/var/tmp/portage
(where /mnt/gentoo is the pfad to the installation, and of course this needs to be done outside the chroot)
I think you should add a note about this issue.
I I´m sorry. I´m just clicked Commit too early. My solution of this problem doesn´t work. But I think it still needs a note, so that nobody tries this again. It seems that it couldn´t be solved and it´s just not working. Running a grsec system with chroot restrictions isn't something Gentoo documents. If you have chroot restrictions I think we can safely assume that the user knows what the restrictions are and that, because Gentoo requires "chroot /mnt/gentoo", this restrictions can cause security measures to take action. Since this issue doesn't come up with "regular" installations I don't want to add anything related to this to the installation instructions. If it happens with many users though it might reach the Gentoo FAQ. |