From: Johannes Erdfelt <johannes@erdfelt.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: cleaning up udev nodes after crash
Date: Sat, 03 Jan 2004 07:15:21 +0000 [thread overview]
Message-ID: <20040103021521.A30988@sventech.com> (raw)
In-Reply-To: <20040103060624.46377.qmail@web14909.mail.yahoo.com>
On Fri, Jan 02, 2004, Greg KH <greg@kroah.com> wrote:
> On Fri, Jan 02, 2004 at 10:27:27PM -0800, Jon Smirl wrote:
> > The tip about putting udev on a tmpfs should probably go into the documentation.
> > Is there any reason not to recommend always putting udev on a tmpfs?
>
> People who care about extended attributes of device nodes, like to keep
> their /dev on a filesystem that supports them (ext2, ext3, etc.)
Won't this be a problem when the kernel switches to dynamic major/minor
numbers?
I wouldn't want to open up /udev/dsp just to find out it's actually
/udev/kmem this boot.
JE
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-01-03 7:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 6:06 cleaning up udev nodes after crash Jon Smirl
2004-01-03 6:15 ` Dave Dodge
2004-01-03 6:27 ` Jon Smirl
2004-01-03 6:56 ` Greg KH
2004-01-03 6:57 ` Greg KH
2004-01-03 7:15 ` Johannes Erdfelt [this message]
2004-01-03 22:06 ` Greg KH
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=20040103021521.A30988@sventech.com \
--to=johannes@erdfelt.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).