[Pkg-sysvinit-devel] Bug#330592: sysvinit: init panic after creating directory /selinux/

[Ernest jw ter Kuile]

Hi,

On Sunday 22 October 2006 16:11, you wrote:
> Can you still reproduce this bug? If so it would be interesting to get a
> bit more information, for instance a full log of the crashing startup.

No, I cannot. 

I checked, but could not find, if a /selinux/ not found error was still given during boot. So
message is gone. I don't know when that happened, nor do I know if that happen because 
of a kernel upgrade, or a debian update.

But then, my system has been updated many times since that bug report.

I added the directory /selinux/ and rebooted, but system did not care.
I removed directory again.



> It would also be good to have some information about your system when it
> is running normally. For instance all the information in /selinux and
> /etc/selinux/.

Well, since your asking, I don't have any selinux policy installed currently, nor did 
I have it then (when I did the bug report). The only thing I do have and had then as 
wel was libselinux1 and libsepol1, as they are in the required category.

> Any information you could provide would be useful,

Would it help if I did install a policy, and send you an install report ?	

Cheers,

Ernest.