On Sun, Dec 06, 2009 at 08:28:37AM -0600, Manoj Srivastava wrote: > All right. At this point, we don't know why this is happening, > except that it is a sed call that is producing these warnings. So, > there is code in sed that probably needs to be modified (though it > might be some other library as well). We should involve an expert on > sed internals to help us move the diagnosis of the problem further > along. > > Reassigning, in the hope that it gets either a fix, or > reassigned to the package where it belongs.
The warning indicates that is_selinux_enabled() returns true and that getfilecon() returns -1 and errno is set to ENODATA. So I suppose the question is why is_selinux_enabled() would return true on a system where it's not enabled. > > sed: warning: failed to get security context of /tmp/grub.zAsxTyPc8P: No > > data available > > sed: warning: failed to get security context of /tmp/grub.zAsxTyPc8P: No > > data available > > > > IMO such warnings should never be generated on a system that does not > > have selinux installed and active. > > > > The chroot was created on an amd64/lenny host system that does not use > > selinux. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
