All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: Joshua Brindle <method@gentoo.org>, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: udev and .dev...
Date: Thu, 29 Jul 2004 21:15:19 +0100	[thread overview]
Message-ID: <20040729201519.GH9950@lkcl.net> (raw)
In-Reply-To: <1091110451.7878.87.camel@icampbell-debian>

On Thu, Jul 29, 2004 at 03:14:11PM +0100, Ian Campbell wrote:
> On Thu, 2004-07-29 at 13:32, Joshua Brindle wrote:
> > Why not have a minimal /dev for init and friends and mount the ramfs for 
> > udev on top of it? it's much easier to deal with 1 /dev and this is 
> > pretty standard anyway.
> 
> I believe what happens is that the on disk dev does live at /dev and the
> udev initscript bind mounts it to /.dev before mounting the rams over
> the top so that you can still get at the on disk version.
 
  presumably in order to sort it out (for admin purposes)

 and in this case, thank goodness for that, because otherwise
 it would be necessary to terminate udev in order to set the
 selinux permissions on the "real" /dev.

 l.

--
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:[~2004-07-29 20:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-29  9:14 udev and .dev Luke Kenneth Casson Leighton
2004-07-29 12:32 ` Joshua Brindle
2004-07-29 14:01   ` Luke Kenneth Casson Leighton
2004-07-29 14:14   ` Ian Campbell
2004-07-29 20:15     ` Luke Kenneth Casson Leighton [this message]
2004-07-29 15:09 ` Erich Schubert
2004-07-29 17:03   ` Stephen Smalley
2004-07-29 20:37     ` Luke Kenneth Casson Leighton
2004-07-29 20:13   ` Luke Kenneth Casson Leighton

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=20040729201519.GH9950@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=ijc@hellion.org.uk \
    --cc=method@gentoo.org \
    --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.