All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dale Amon <amon@vnl.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Dale Amon <amon@vnl.com>, SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: rfs xattr's, mkinitrd and other stories
Date: Wed, 10 Sep 2003 18:59:14 +0100	[thread overview]
Message-ID: <20030910175914.GP5397@vnl.com> (raw)
In-Reply-To: <1063213343.14458.35.camel@moss-spartans.epoch.ncsc.mil>

On Wed, Sep 10, 2003 at 01:02:23PM -0400, Stephen Smalley wrote:
> devfs will require a patch to support labeling, and appears to be
> obsolete in 2.6.

How so? It's still marked experimental in fact. devpts has been
made independant but I can't imagine why devfs would ever be
removed. If anything it is superseding the old static /dev.

As to the patch, I'm not sure what is needed there. I do know
I have an /etc/devfsd/conf.d/selinux that is used at boot time.
I've had some problems with it and disabled that temporarily to
avoid the /lib/devfsd/devfs-se.so error messages at boot time.

So what next? Try to get Richard Gooch's attention? 
 
> The mkinitrd script needs to copy the policy file and load_policy
> program onto the initrd, and the /linuxrc script that is placed on the
> initrd needs to mount selinuxfs and run load_policy before the root
> filesystem is mounted.

I'm still worried about what happens after the next apt-get or dselect
If it restores the standard mkinitrd during an upgrade and I don't
notice before rebooting... could be nasty.

I supposed I could make it /usr/local/sbin/mkinitrd if the path 
search order during early boot up happens to include that before
/usr/sbin.

That's why I'm wondering what Colin or Russ' thoughts are on the
matter.

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2003-09-10 17:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10 16:48 rfs xattr's, mkinitrd and other stories Dale Amon
2003-09-10 17:02 ` Stephen Smalley
2003-09-10 17:59   ` Dale Amon [this message]
2003-09-10 18:17     ` Stephen Smalley
2003-09-10 19:03 ` Chris PeBenito
2003-09-10 19:10   ` Dale Amon
2003-09-10 19:38     ` Chris PeBenito
2003-09-10 19:43       ` Dale Amon
2003-09-10 19:11   ` Stephen Smalley
2003-09-10 22:30 ` Colin Walters
2003-09-10 22:50   ` Dale Amon
2003-09-10 23:05   ` Dale Amon
2003-09-10 23:34     ` Dale Amon
2003-09-10 23:48       ` Dale Amon
2003-09-11  0:48       ` Russell Coker
2003-09-11 11:47         ` Stephen Smalley
2003-09-11 13:18           ` Russell Coker
2003-09-12 14:21         ` Dale Amon
2003-09-12 15:00           ` Russell Coker
2003-09-12 16:06             ` Dale Amon
2003-09-12 16:24               ` Dale Amon
2003-09-12 17:44               ` Russell Coker
2003-09-11 11:42       ` Stephen Smalley
  -- strict thread matches above, loose matches on Subject: below --
2003-09-13 11:55 Dale Amon

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=20030910175914.GP5397@vnl.com \
    --to=amon@vnl.com \
    --cc=sds@epoch.ncsc.mil \
    --cc=selinux@tycho.nsa.gov \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.