Bug#753727: [DSE-Dev] Bug#753727: reason for this

2014-07-05 Thread Russell Coker
On Sat, 5 Jul 2014 14:12:49 Laurent Bigonville wrote: > But this means that we could drop the telinit u from the libsepol > postinst script, correct? Yes. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/ -- To UNSUBSCRIBE, email to debian-bugs-di

Bug#753727: [DSE-Dev] Bug#753727: reason for this

2014-07-05 Thread Laurent Bigonville
Le Sat, 05 Jul 2014 20:11:44 +1000, Russell Coker a écrit : > On Sat, 5 Jul 2014 11:03:32 Laurent Bigonville wrote: > > Quickly looking a the libsepol case, I'm not sure why we are > > re-executing init in this case at all. sysvinit doesn't seems to use > > any of its symbols and libselinux itsel

Bug#753727: [DSE-Dev] Bug#753727: reason for this

2014-07-05 Thread Russell Coker
On Sat, 5 Jul 2014 11:03:32 Laurent Bigonville wrote: > Quickly looking a the libsepol case, I'm not sure why we are > re-executing init in this case at all. sysvinit doesn't seems to use > any of its symbols and libselinux itself is statically linked against > it. > > Or did I overlooked somethin

Bug#753727: [DSE-Dev] Bug#753727: reason for this

2014-07-05 Thread Laurent Bigonville
Le Sat, 05 Jul 2014 11:46:08 +1000, Russell Coker a écrit : > > The current version of libselinux1.postint runs "telinit u" to tell > > init to re-exec itself. This was added so the system can shutdown > > cleanly when sysvinit is the active PID 1. > > AFAIK that was never the case. > > The rea