After doing a default install of FC4T3 I relabeled the file system. Ideally such an operation should be a no-op as the install should have used the same labels that the relabel operation does. Below is part of the output of setfiles when performing the relabel. It seems that the pyo files were created by a post-install script in the rpm package or by a system boot script. Could someone please advise on what programs are likely to need the access to create such files? setfiles: relabeling /usr/share/printconf/util/cups_import.pyo from system_u:object_r:usr_t to system_u:object_r:printconf_t setfiles: relabeling /usr/share/printconf/util/backend.pyo from system_u:object_r:usr_t to system_u:object_r:printconf_t setfiles: relabeling /usr/share/printconf/util/scan_usb_devices.pyo from system_u:object_r:usr_t to system_u:object_r:printconf_t setfiles: relabeling /usr/share/printconf/util/printconf_conf.pyo from system_u:object_r:usr_t to system_u:object_r:printconf_t -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-devel-list
