From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] /run/udev missing ?
Date: Mon, 15 Aug 2011 11:05:39 +0200 [thread overview]
Message-ID: <878vqvgi3g.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1313396462.31752.3.camel@sven> (Sven Neumann's message of "Mon, 15 Aug 2011 10:21:01 +0200")
>>>>> "Sven" == Sven Neumann <s.neumann@raumfeld.com> writes:
Hi,
Sven> Yes, and it looks like linux/linux.mk is responsible for making sure
Sven> that the kernel is configured as expected. As far as I can see this
Sven> works just fine.
Indeed, if you build your kernel with buildroot.
Sven> Still it may be desirable to run udev and use static device
Sven> management at the same time. At least this used to work and I
Sven> would like to make it work again.
What would the advantage of this be? This is not how udev is normally
used nowadays (devtmpfs was explicitly made to fix various issues with
the initial static /dev and handover to udev) on PCs.
Compared to udev, devtmpfs is very lightweight. I would recommend pure
devtmpfs (no mdev/udev) to people using static /dev today.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-08-15 9:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 8:29 [Buildroot] /run/udev missing ? Sven Neumann
2011-08-14 6:43 ` Peter Korsgaard
2011-08-15 8:21 ` Sven Neumann
2011-08-15 9:05 ` Peter Korsgaard [this message]
2011-08-15 9:34 ` Sven Neumann
2011-08-15 12:10 ` Peter Korsgaard
2011-08-15 14:01 ` Sven Neumann
2011-08-15 14:18 ` Daniel Mack
2011-08-15 14:24 ` Baruch Siach
2011-08-16 8:40 ` Sven Neumann
2011-08-16 11:59 ` Diego Iastrubni
2011-08-16 12:44 ` Michael S. Zick
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=878vqvgi3g.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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