From: "Morgan, Austin D." <AUSTIN.D.MORGAN@saic.com>
To: gentoo-embedded@lists.gentoo.org
Subject: RE: [gentoo-embedded] udev
Date: Tue, 20 Jun 2006 14:53:40 -0700 [thread overview]
Message-ID: <F23B2C80E3825F47B93655363249D0570C7868@0695-its-exmp01.us.saic.com> (raw)
That is exacctly what I was looking for. Thank you very much. The problem
with a swiss-army knife is sometimes it is hard to figure out what all tools
are included.
Austin
-----Original Message-----
From: gentoo-embedded+bounces-919-AUSTIN.D.MORGAN=saic.com@gentoo.org on
behalf of Ned Ludd
Sent: Tue 6/20/2006 4:27 PM
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] udev
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.
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
--
Ned Ludd <solar@gentoo.org>
Gentoo Linux
--
gentoo-embedded@gentoo.org mailing list
next reply other threads:[~2006-06-20 21:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 21:53 Morgan, Austin D. [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2006-06-20 22:31 ` Mike Frysinger
2006-06-20 21:26 ` Anish Patel
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=F23B2C80E3825F47B93655363249D0570C7868@0695-its-exmp01.us.saic.com \
--to=austin.d.morgan@saic.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