From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: devfs gone, and now?
Date: Sat, 26 Jun 2004 13:26:42 +0000 [thread overview]
Message-ID: <40DD7992.9000801@backtobasicsmgmt.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0406260838290.12525@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
> devfs is tagged obsolete and I'm worrying about what modules will now do,
> because with devfs they could create a node in /dev whenever they were loaded,
> and remove that, if unloaded. That's now missing, or is there an udev solution?
Yes, read the udev documentation.
> As I currently see it, udev creates a "static" device node in /dev which
> persists even across reboots, so if you load a lot of modules which create a
> lot of block/char/etc. devices in /dev, they would probably be removed upon
> 'rmmod', but not if you just reboot.
No, read the udev documentation. Everything you've described here works
perfectly with udev.
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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-06-26 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 6:41 devfs gone, and now? Jan Engelhardt
2004-06-26 13:26 ` Kevin P. Fleming [this message]
2004-06-26 13:48 ` Olivier Mehani
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=40DD7992.9000801@backtobasicsmgmt.com \
--to=kpfleming@backtobasicsmgmt.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 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.