Description of problem: /dev/fd0 seem to have the wrong type set which gives problems to kduzu during startup and pcmcia during shutdown. policy-1.11.2-1 udev-023-2 kernel-2.6.5-1.322 kudzu-1.1.54-1 Apr 14 13:32:37 hummer kernel: audit(1081963949.525:0): avc: denied { read } for pid=725 exe=/usr/sbin/kudzu name=fd0 dev=hda10 ino=524779 scontext=system_u:system_r:kudzu_t tcontext=system_u:object_r:device_t tclass=blk_file There is also a message that "cannot stat /dev/fd0" brw-rw---- root floppy system_u:object_r:device_t /dev/fd0 brw-rw---- root floppy system_u:object_r:removable_device_t /dev/fd0CompaQ brw-rw---- root floppy system_u:object_r:removable_device_t /dev/fd0d360 And this occurs when I stop pcmcia: Apr 14 13:40:17 hummer kernel: audit(1081964417.410:0): avc: denied { search } for pid=3050 exe=/usr/sbin/updfstab name=root dev=hda10 ino=65281 scontext=root:system_r:updfstab_t tcontext=root:object_r:staff_home_dir_t tclass=dir Apr 14 13:40:17 hummer kernel: audit(1081964417.411:0): avc: denied { getattr } for pid=3050 exe=/usr/sbin/updfstab path=/dev/fd0 dev=hda10 ino=524779 scontext=root:system_r:updfstab_t tcontext=system_u:object_r:device_t tclass=blk_file
Any chance this is left over from the bad udev command. If you relabel the dev directory setfiles /etc/security/selinux/file_context /dev and then reboot, does the file come back. I saw this before I updated the udev version, but after doing the relabel, I have not seen it since. Dan
It must have been udev or whatever because after running setfiles, /dev/fd0 was correctly maked and kudzu came up fine on reboot. Since test3 seems to ave slipped from the 19th to the 29th, I think I will grab a snapshot of development in a couple of days (when the XFree86->Xorg settles down) and see what a fresh install looks like.