On Wed, 2009-09-09 at 12:21 +0530, Didar Hossain wrote: > On Wed, Sep 9, 2009 at 4:02 AM, John Horne<john.horne@xxxxxxxxxxxxxx> wrote: [snipped] > > However, and I don't know why, selinux objects when exim checks the /boot partition. I > > suspect an selinux boolean may be required to allow exim to look at /boot. > > But, why check "/boot"? As far as I understood from the statvfs(2), it > accepts a path to get the information. "/boot" is not something that > Exim will use as a spool directory. Or am I missing something!? > > > (When I installed F11 I used ext4 for the root partition, so I had to > > create a separate /boot partition using ext3.) > > As said, because /boot is a separate partition. Statvfs looks at all the partitions, not just the one containing the path, as far as I can tell (look at strace output and you will see /proc/mounts being checked, and then a stat of each partition). This is also why I was getting the same errors for my other partitions. However, once I set their context to the same as /usr (although I could have chosen some other directory context), the errors for those partitions went away. If /boot wasn't a separate partition then the problem wouldn't appear, but since /boot must be ext3, and because I have / as ext4, so /boot must be a separate partition. The system is looking at /boot, but for some reason it is throwing up an selinux error. That's the bit I don't understand (unless the 'boot_t' context is somewhat specific about who can look at /boot, but then why aren't errors shown if I simply try and do 'ls -l /boot'?). John. -- John Horne Tel: +44 (0)1752 587287 University of Plymouth, UK Fax: +44 (0)1752 587001 -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
