* [Buildroot] $udevroot
@ 2011-08-11 14:32 Sven Neumann
2011-08-11 15:00 ` Yegor Yefremov
2011-08-11 23:10 ` Diego Iastrubni
0 siblings, 2 replies; 4+ messages in thread
From: Sven Neumann @ 2011-08-11 14:32 UTC (permalink / raw)
To: buildroot
Hi,
we are facing some problems with device nodes since the udev update. Now
I am trying to understand how the whole device management works
nowadays.
First thing that made me wonder is the following output on startup:
Populating using udev: done
This is from /etc/init.d/S10udev and it looks like $udevroot is not set
here. Is that just a cosmetic issue or an indicator that something is
severily broken?
Sven
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Buildroot] $udevroot
2011-08-11 14:32 [Buildroot] $udevroot Sven Neumann
@ 2011-08-11 15:00 ` Yegor Yefremov
2011-08-11 17:32 ` Sven Neumann
2011-08-11 23:10 ` Diego Iastrubni
1 sibling, 1 reply; 4+ messages in thread
From: Yegor Yefremov @ 2011-08-11 15:00 UTC (permalink / raw)
To: buildroot
Hi Sven,
> we are facing some problems with device nodes since the udev update. Now
> I am trying to understand how the whole device management works
> nowadays.
What problems are you facing?
> First thing that made me wonder is the following output on startup:
>
> Populating using udev: done
>
> This is from /etc/init.d/S10udev and it looks like $udevroot is not set
> here. Is that just a cosmetic issue or an indicator that something is
> severily broken?
Actually we don't need this output any more, because /dev/ is already populated due to devtmpfs.
Yegor
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Buildroot] $udevroot
2011-08-11 15:00 ` Yegor Yefremov
@ 2011-08-11 17:32 ` Sven Neumann
0 siblings, 0 replies; 4+ messages in thread
From: Sven Neumann @ 2011-08-11 17:32 UTC (permalink / raw)
To: buildroot
On Thu, 2011-08-11 at 17:00 +0200, Yegor Yefremov wrote:
> > we are facing some problems with device nodes since the udev update. Now
> > I am trying to understand how the whole device management works
> > nowadays.
>
> What problems are you facing?
Well, I went with the default of using a static device table and
obviously I need to add some device files that are otherwise missing.
But I'll now to try to use udev instead.
Thanks,
Sven
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Buildroot] $udevroot
2011-08-11 14:32 [Buildroot] $udevroot Sven Neumann
2011-08-11 15:00 ` Yegor Yefremov
@ 2011-08-11 23:10 ` Diego Iastrubni
1 sibling, 0 replies; 4+ messages in thread
From: Diego Iastrubni @ 2011-08-11 23:10 UTC (permalink / raw)
To: buildroot
On Thu, Aug 11, 2011 at 5:32 PM, Sven Neumann <s.neumann@raumfeld.com>wrote:
> Hi,
>
> we are facing some problems with device nodes since the udev update. Now
> I am trying to understand how the whole device management works
> nowadays.
>
> First thing that made me wonder is the following output on startup:
>
> Populating using udev: done
>
> This is from /etc/init.d/S10udev and it looks like $udevroot is not set
> here. Is that just a cosmetic issue or an indicator that something is
> severily broken?
>
Please add "udevadm trigger" after running udev, and tell us if this works.
This worked for me, and if this fixes it for you, we can add it to the git
repository.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110812/f8d238e7/attachment.html>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-08-11 23:10 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-08-11 14:32 [Buildroot] $udevroot Sven Neumann
2011-08-11 15:00 ` Yegor Yefremov
2011-08-11 17:32 ` Sven Neumann
2011-08-11 23:10 ` Diego Iastrubni
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox