On Mon, Apr 03, 2006 at 09:51:29PM +0100, Julian Gilbey wrote: > severity 333441 important > thanks > > On Sat, Oct 29, 2005 at 01:29:28AM +0200, Erich Schubert wrote: > > Hi, > > this is caused by /selinux not being mounted. This dir can only be > > mounted if the kernel has selinux enabled already. > > There is a bootstrapping issue with selinux right now: if you enable it > > without having a policy, sysvinit will panic. > > I'm not sure about the best way to handle it. A week ago I would have > > suggested to default to 19, but 2.6.14 was now uploaded to unstable > > which should have policy version 20... I don't know a way to detect the > > selinux version of a kernel which is not running with selinux=1 > > I hit the same bug. It makes the package basically uninstallable from > an SELinux-disabled kernel. > > While I can't give any useful suggestions how to fix this bug, > selinux-basics has just hit testing, and this is how I bumped into > this. > > Maybe there is some way the kernel can be patched to be able to report > on this, or maybe there's some other way...
something that happened to work here: reboot with SELinux enabled in permissive mode. Pay attention to the default kernel setting, to the kernel option and to the option on /etc/selinux/config (this last defaults to enforcing and makes init to halt on the boot sequence; then it need to be changed to permissive) trying to help, rollingbits -- ,-. rollingbits -- [EMAIL PROTECTED], [EMAIL PROTECTED] \`' [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] ` Get my public GPG key in http://rollingbits.tripod.com/mykey.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
