From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: thinking of updating the canonical online udev document
Date: Tue, 26 Apr 2011 06:32:54 -0700 [thread overview]
Message-ID: <20110426133254.GC14149@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1104260903450.10339@localhost6.localdomain6>
On Tue, Apr 26, 2011 at 09:06:02AM -0400, Robert P. J. Day wrote:
> On Tue, 26 Apr 2011, Greg KH wrote:
>
> > On Tue, Apr 26, 2011 at 08:12:44AM -0400, Robert P. J. Day wrote:
> > >
> > > [not sure if this is the right forum for this, but i suspect others
> > > on this list might be interested so ... there you go.]
> >
> > The linux-hotplug at vger.kernel.org list is where this should be
> > discussed, please take it there.
> >
> > > as part of a device driver course i may very well be teaching in the
> > > near future (still waiting to hear), i'm thinking of adding a sizable
> > > section on how udev works (after i figure all that out, of course.)
> > >
> > > currently, the canonical udev document is this one:
> > >
> > > http://reactivated.net/writing_udev_rules.html
> >
> > That doc could almost be removed entirely now, as no one should need
> > to mess with udev rules "by hand" anymore thanks to devtmpfs and the
> > default udev rules that are in all distros (with one notable
> > exception.)
> >
> > What is your goal in redoing this? Why would a user/developer ever
> > need to mess with udev on their own anymore?
> >
> > Ideally, it should all "just work" now, and I think it does given
> > your previous emails about the confusion as to how your driver was
> > automagically creating the correct device nodes without any help
> > from you :)
>
> so you don't see much need for that level of detail for udev
> anymore? at the very least, i can see the need for what i asked about
> before -- how a misc device suddenly showed up under /dev, and with
> what properties.
You want a "how does this all work" type document, which is aimed for a
developer, not a user, right? That's different from the above mentioned
document in quite a number of ways.
> is there a doc explaining that somewhere? because i definitely went
> looking before i asked that question here.
I wrote something like that a long time ago for LDD3 and later updated
it for lwn.net I think, if you want to start with that.
good luck,
greg k-h
prev parent reply other threads:[~2011-04-26 13:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 12:12 thinking of updating the canonical online udev document Robert P. J. Day
2011-04-26 12:41 ` Compiling single module Ezequiel García
2011-04-26 13:29 ` Greg KH
2011-04-27 9:44 ` Tayssir Alkowatly
2011-04-27 16:27 ` Mulyadi Santosa
2011-04-26 12:54 ` thinking of updating the canonical online udev document Greg KH
2011-04-26 13:05 ` Mandeep Sandhu
2011-04-26 13:31 ` Greg KH
2011-04-26 13:59 ` Mandeep Sandhu
2011-04-26 13:06 ` Robert P. J. Day
2011-04-26 13:32 ` 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=20110426133254.GC14149@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).