From: mandeepsandhu.chd@gmail.com (Mandeep Sandhu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: thinking of updating the canonical online udev document
Date: Tue, 26 Apr 2011 18:35:58 +0530 [thread overview]
Message-ID: <BANLkTinJjwF4swSRO_D60TVkC8T+FKwk5A@mail.gmail.com> (raw)
In-Reply-To: <20110426125445.GA6272@kroah.com>
> 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?
Well, I would! :)
We're working on an embedded platform and can't use a complete distro.
But we still want some good-bits from the desktop world, to be
available for our system. And udev is one such thing we're trying to
use (for USB plug and play kind of a feature).
Apart from having a custom vendor-supplied kernel, pretty much
everything else in the user-space has to be "hand-coded" by us.
Or is there another 'convenient' alternative?
Thanks,
-mandeep
next prev parent reply other threads:[~2011-04-26 13:05 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 [this message]
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
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=BANLkTinJjwF4swSRO_D60TVkC8T+FKwk5A@mail.gmail.com \
--to=mandeepsandhu.chd@gmail.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).