From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: what is the precise udev event that handles miscdevices?
Date: Wed, 1 Apr 2015 08:04:16 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1504010756400.14774@localhost> (raw)
In-Reply-To: <20150401115506.GA20827@kroah.com>
On Wed, 1 Apr 2015, Greg KH wrote:
> On Wed, Apr 01, 2015 at 07:43:05AM -0400, Robert P. J. Day wrote:
> >
> > i can trivially create misc character devices, and i know special
> > device files for them will automatically show up under /dev, but what
> > is the precise udev event/rule that comes into play for this?
>
> There isn't one.
>
> Gee, this is going to be easy :)
don't get smug. :-) i had sort of concluded there was no actual udev
rule i could point at, so it's just the case that udev processes those
events internally? is this written down anywhere? everyone happily
explains how misc devices get their /dev file automatically, but no
one i've seen goes that extra step to explain how that happens.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2015-04-01 12:04 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 [this message]
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
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=alpine.LFD.2.11.1504010756400.14774@localhost \
--to=rpjday@crashcourse.ca \
--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).