From: Natanael Copa <natanael.copa@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] udev
Date: Wed, 21 Jun 2006 00:06:25 +0200 [thread overview]
Message-ID: <1150841185.14055.5.camel@localhost> (raw)
In-Reply-To: <1150838835.28592.5.camel@localhost>
On Tue, 2006-06-20 at 17:27 -0400, Ned Ludd wrote:
> On Tue, 2006-06-20 at 23:14 +0200, Natanael Copa wrote:
> > On Tue, 2006-06-20 at 14:00 -0700, Morgan, Austin D. wrote:
> > > Is anyone useing udev in their embedded systems? If not what has become the
> > > defacto standard for filling /dev? I hate to manually create all the nodes
> > > although it is probably the most efficient use of space.
> >
> > I am using udev. When I get time I will look at how to replace it with
> > busybox's mdev.
>
> mdev is the route to go for dynamic device nod creation for
> embedded/busybox 2.6 based systems. but be sure you still have
> the base nods urandom,zero,stdin,stdout,stderr,null,ttyS0 there anyway.
I needed those before udev got started to so thats no difference.
> Example conf used when I initially slapped the conf logic together.
> Not sure how much Rob changed it however from where I left off.
> I think he only extended on it allow it to shell out etc..
> http://tinderbox.dev.gentoo.org/misc/mdev.conf
Thank you very much! I really appreciated that one.
How does it work with hotplugging? I currently use:
echo /sbin/udevsend > /proc/sys/kernel/hotplug
--
Natanael Copa
--
gentoo-embedded@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-20 22:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 21:00 [gentoo-embedded] udev Morgan, Austin D.
2006-06-20 21:08 ` Henrik Brix Andersen
2006-06-20 21:14 ` Natanael Copa
2006-06-20 21:27 ` Ned Ludd
2006-06-20 22:06 ` Natanael Copa [this message]
2006-06-20 22:31 ` Mike Frysinger
2006-06-20 21:26 ` Anish Patel
-- strict thread matches above, loose matches on Subject: below --
2006-06-20 21:53 Morgan, Austin D.
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=1150841185.14055.5.camel@localhost \
--to=natanael.copa@gmail.com \
--cc=gentoo-embedded@lists.gentoo.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