On Fri, 2006-11-17 at 15:48 +0000, Ian Malone wrote: > The 'correct' solution seems to be to use chcon -t texrel_shlib_t on > every file that has this problem (use dmesg to hunt them down). I'm not sure I'd do that on "every" file that generates that warning. Some of them probably shouldn't be allowed to do that, that's why there's a restriction for that sort of thing. -- (Currently testing FC5, but still running FC4, if that's important.) Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
