From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: what is the precise udev event that handles miscdevices?
Date: Wed, 1 Apr 2015 14:45:40 +0200 [thread overview]
Message-ID: <20150401124540.GA16117@kroah.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1504010806440.15199@localhost>
On Wed, Apr 01, 2015 at 08:18:13AM -0400, Robert P. J. Day wrote:
> On Wed, 1 Apr 2015, Greg KH wrote:
> > In fact, no one does this anymore, and people run systems without
> > udev and have dynamic device nodes just fine. And have been doing
> > so for years, udev isn't needed for device nodes anymore, if that's
> > all you care about.
>
> yup, i can see that now. although i would *think* that you could
> still use udev to go above and beyond just creating device files, to
> do things like create symlinks, run arbitrary programs and so on. but,
> yes, for just straight device file manipulation, devtmpfs is
> sufficient.
Yes, your persistent device names (the whole reason udev was created in
the first name) are still created by udev, as that is best left up to
userspace. Those are symlinks to the device nodes devtmpfs created.
Also, sometimes you want different group/user permissions on device
nodes from what the kernel provides (the kernel doesn't know the group
file), so udev will modify the mode and owners of some nodes as well.
good luck!
greg k-h
prev parent reply other threads:[~2015-04-01 12:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 11:43 what is the precise udev event that handles miscdevices? Robert P. J. Day
2015-04-01 11:55 ` Greg KH
2015-04-01 12:04 ` Robert P. J. Day
2015-04-01 12:19 ` Sudip Mukherjee
2015-04-01 12:34 ` Robert P. J. Day
2015-04-01 11:59 ` Greg KH
2015-04-01 12:18 ` Robert P. J. Day
2015-04-01 12:45 ` Greg KH [this message]
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=20150401124540.GA16117@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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).