From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] /run/udev missing ?
Date: Mon, 15 Aug 2011 16:01:02 +0200 [thread overview]
Message-ID: <1313416862.29966.2.camel@sven> (raw)
In-Reply-To: <874o1iho3k.fsf@macbook.be.48ers.dk>
On Mon, 2011-08-15 at 14:10 +0200, Peter Korsgaard wrote:
> >>>>> "Sven" == Sven Neumann <s.neumann@raumfeld.com> writes:
>
> Hi,
>
> >> Compared to udev, devtmpfs is very lightweight. I would recommend
> >> pure devtmpfs (no mdev/udev) to people using static /dev today.
>
> Sven> Well, we need udev to load the firmware of our Wifi module. Of
> Sven> course I can try to switch to dynamic device management, but I
> Sven> thought I'd rather point out that a setup broke that the
> Sven> buildroot configuration allows and that used to work.
>
> Sven> If this is not supposed to work, then it should probably be
> Sven> disallowed in the buildroot configuration. In other words, if
> Sven> udev is selected, static device management should not be
> Sven> selectable.
>
> Ahh yes, good idea - Fixed in git.
Hmm, not really was I was asking for in the first place. But I guess
I'll have to deal with your decision then to drop support for this
configuration...
Still I wonder why udevd is looking for "/run/udev". Shouldn't this
be /var/run/udev ? Looks to me like udevd is configured with a wrong
prefix for the run directory.
Sven
next prev parent reply other threads:[~2011-08-15 14:01 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
2011-08-15 9:34 ` Sven Neumann
2011-08-15 12:10 ` Peter Korsgaard
2011-08-15 14:01 ` Sven Neumann [this message]
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=1313416862.29966.2.camel@sven \
--to=s.neumann@raumfeld.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.