Summary: | /etc/init.d/net.eth0 with dhcpcd config doesn't start due do /run migration ~amd64/selinux | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Amadeusz Sławiński <amade> |
Component: | SELinux | Assignee: | Sven Vermeulen (RETIRED) <swift> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | selinux |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | sec-policy r15 | ||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 424173 |
Description
Amadeusz Sławiński
2012-07-17 10:00:41 UTC
I notice two things. One is that the scripts are trying to create directories in /var/run (not /run). If you create "/var/run/dhcpcd" manually and run "restorecon -R /var/run/dhcpcd", does that fix the problem(s)? As the directory in /var/run is static (not regenerated during each boot) that might solve this (short-term). Regarding the /run, are the logs you show for the /run location or still for /var/run? The problem is that on new installs /var/run is linked to /run which is tmpfs so as far a I can tell all dirs gets recreated every reboot % ls -l /var | grep run lrwxrwxrwx. 1 root root 9 Jul 14 14:34 lock -> /run/lock lrwxrwxrwx. 1 root root 4 Jul 14 14:34 run -> /run I hate it, but you're right. recent stage3s have /var/run symlinked to /run Will be fixed in rev15 in hardened-dev overlay In main tree, ~arched stabilized |