With latest from Rawhide, running strict/permissive:
Each boot, something is relabeling /etc/fstab from etc_t to tmp_t.
I suspect fstab-sync, which seems to be run just after hald is started (from hald? /etc/hal/device.d/50-fstab-sync.hal ?)
Of course, if you forget to restore it before rebooting in strict/enforcing mode, the boot fails trying to read /etc/fstab, and puts you into 'disk doctor' mode.
This doesn't happen if you boot in strict/enforcing mode, since the policy prevents this from running and doing damage.
I noticed a bugzilla against hal: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131187
Anyone else seeing this? Does this happen in targeted policy?
tom
