From: Nathanael D. Noblet <nathanael@gnat.ca>
To: buildroot@busybox.net
Subject: [Buildroot] Using udev, non-static /dev, and ramfs (or tmpfs)
Date: Sat, 21 Oct 2006 19:19:06 -0600 [thread overview]
Message-ID: <1161479946.4306.3.camel@iridium.gnat.ca> (raw)
In-Reply-To: <20061021183403.GA21456@reid1.localdomain>
On Sat, 2006-10-21 at 11:34 -0700, don wrote:
> I see that /etc/init.d/S10udev tries to use "/sbin/udevstart", but
> I don't have that.
>
> Would I be better off to keep things static?
I've been using udev for a bit (I think I added the original patch for
it). Since then a few things have changed. I've cleaned it up a bit
lately and have some patches for udev to fix exactly what you just
described. I'm not completely done yet, however here is a patch that
should fix most of that. Its created in the udev directory itself so as
not to pick up all the other changes in limbo.
--
Nathanael D. Noblet <nathanael@gnat.ca>
Gnat Solutions, Inc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: udev.patch
Type: text/x-patch
Size: 3260 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20061021/5b5e602f/attachment.bin
prev parent reply other threads:[~2006-10-22 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 18:34 [Buildroot] Using udev, non-static /dev, and ramfs (or tmpfs) don
2006-10-21 20:22 ` Rob Landley
2006-10-22 1:19 ` Nathanael D. Noblet [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=1161479946.4306.3.camel@iridium.gnat.ca \
--to=nathanael@gnat.ca \
--cc=buildroot@busybox.net \
/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