From: Ian Campbell <ijc@hellion.org.uk>
To: Joshua Brindle <method@gentoo.org>
Cc: Luke Kenneth Casson Leighton <lkcl@lkcl.net>,
SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: udev and .dev...
Date: Thu, 29 Jul 2004 15:14:11 +0100 [thread overview]
Message-ID: <1091110451.7878.87.camel@icampbell-debian> (raw)
In-Reply-To: <4108EE75.6040109@gentoo.org>
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.
An excerpt from the Debian udev initscript:
# /.dev is used by /sbin/MAKEDEV to access the real /dev directory.
# if you don't like it just remove it.
[ -d /.dev ] && mount --bind /dev /.dev
echo -n "Mounting a tmpfs over /dev..."
mount -n -o size=$tmpfs_size,mode=0755 -t tmpfs none /dev
echo "done."
Ian.
--
Ian Campbell
Current Noise: Faith No More - Woodpecker From Mars
I must get out of these wet clothes and into a dry Martini.
-- Alexander Woolcott
--
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.
next prev parent reply other threads:[~2004-07-29 14:14 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 [this message]
2004-07-29 20:15 ` Luke Kenneth Casson Leighton
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=1091110451.7878.87.camel@icampbell-debian \
--to=ijc@hellion.org.uk \
--cc=lkcl@lkcl.net \
--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.