William Keaney schrieb:
On Wed, Oct 1, 2008 at 2:45 AM, Markus Bartl
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
wrote:
Hi Folks!
Im now able to boot up in enforcing mode and log in to my system.
What i still get is
Sep 30 10:20:01 odin type=1400 audit(1222762783.108:5): avc:
denied { read write } for pid=1278 comm="modprobe"
path="/dev/null" dev=tmpfs ino=1330
scontext=system_u:system_r:insmod_t
tcontext=system_u:object_r:device_t tclass=chr_file
...
Sep 30 10:20:01 odin type=1400 audit(1222762796.338:19): avc:
denied { write } for pid=2882 comm="runscript.sh"
name="resolv.conf" dev=sda3 ino=1999328
scontext=system_u:system_r:initrc_t
tcontext=system_u:object_r:net_conf_t tclass=file
Sep 30 10:20:01 odin type=1400 audit(1222762801.746:21): avc:
denied { search } for pid=3681 comm="syslog-ng" name="lib"
dev=sda3 ino=770262 scontext=system_u:system_r:syslogd_t
tcontext=system_u:object_r:var_lib_t tclass=dir
Sep 30 10:35:05 odin type=1400 audit(1222763686.716:3): avc:
denied { write } for pid=1150 comm="bash" name="null" dev=tmpfs
ino=1330 scontext=system_u:system_r:initrc_t
tcontext=system_u:object_r:device_t tclass=chr_file
Im not quite sure if the /dev/null thing is really a problem, but
the reslov.conf thing is one, because i dont get an IP from DHCP
later on during boot.
Again any ideas are welcome.
Regards,
Markus
The /dev/null thing is due to a temporary mislabeling of the nodes
under /dev/ during udev initialization. I have submitted a patch to
Chris PeBenito that should fix this.
Will
Ok thats one thing.
But the real nasty thing is the denial of write access to resolv.conf
which leads to an improper network configuration.
I would really be happy about any suggestions.
Markus
