From: Gene Heskett <gene.heskett@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6.29-rc1 vs selinux
Date: Fri, 16 Jan 2009 03:21:26 -0500 [thread overview]
Message-ID: <200901160321.26749.gene.heskett@gmail.com> (raw)
One of the things that was bugging me was that after having booted 2.6.29-rc1,
rebooting to 2.6.28 final always caused an automatic relabel, which on this
box with a bit over a terrabyte in drives, takes an extra 20 minutes to do.
So I grepped the .config's and there is no mention of SELINUX in the output of
a make oldconfig for 2.6.29-rc1, based on a 2.6.28 .config input.
I see the security/selinux directory still exists in the src tree. Is this a
kconfig bug, or is selinux outta here?
Thanks.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Bushydo -- the way of the shrub. Bonsai!
next reply other threads:[~2009-01-16 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 8:21 Gene Heskett [this message]
2009-01-16 13:51 ` 2.6.29-rc1 vs selinux Stephen Smalley
2009-01-16 13:58 ` Stephen Smalley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200901160321.26749.gene.heskett@gmail.com \
--to=gene.heskett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox