From: russell@coker.com.au (Russell Coker) Date: Mon, 25 Jul 2011 22:39:27 +1000 Subject: [refpolicy] new refpolicy release In-Reply-To: <1311596233.7563.7.camel@localhost.localdomain> References: <201107241559.02111.russell@coker.com.au> <4E2D5DA9.7060901@tresys.com> <1311596233.7563.7.camel@localhost.localdomain> Message-ID: <201107252239.27504.russell@coker.com.au> To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com On Mon, 25 Jul 2011, Dominick Grift wrote: > > > As an aside, what's the status of systemd policy? > > > > There isn't one upstream. The last time it was discussed, I suggested > > that it was so different and did so many more things that it should > > probably be its own module. I haven't heard or seen anything since then. > > I started working on it and gotten pretty far until i tried shutdown. > That is when i hit issues. > > Kernel logging is stopped pretty early and so i could not determine what > all systemd needs to shutdown properly. Spend about a week just trying > various things but could not get it to work. Gave up. Could you please post what you did to the list so others can work on it without reinventing any wheels? > In the mean time new functionality was added to systemd like supports > for multi seat and there more to come. What is "multi seat"? -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/