[Buildroot] $udevroot

[Buildroot] $udevroot

[Sven Neumann]

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

[Buildroot] $udevroot

[Yegor Yefremov]

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

[Buildroot] $udevroot

[Sven Neumann]

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

[Buildroot] $udevroot

[Diego Iastrubni]

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>