Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Towards 2015.05-rc1
Date: Wed, 22 Apr 2015 20:09:31 -0300	[thread overview]
Message-ID: <55382A2B.1090108@zacarias.com.ar> (raw)
In-Reply-To: <55381E27.4020502@mind.be>

On 04/22/2015 07:18 PM, Arnout Vandecappelle wrote:

>  Since udev rules are IMHO a lot more complicated than mdev rules and you
> usually don't need that complexity in embedded systems, I think there really is
> a case to be made for avoiding full udev. Of course, it's always possible to
> remove the udev start script in a post-build script (which effectively makes
> udev dead code), but it is definitely nice to know which packages will work
> without udev running. So that's what I would like this libudev stuff to do.
> 
>  For example, I have one system that used to be based on mdev. Now we have to
> add modem-manager to it, and modem-manager depends on udev. So I've enabled
> udev, but now I have to replace the mdev rules with udev rules and I probably
> also have to get rid of some of the default udev rules which are not appropriate.

There's also usbutils which now requires the udev hwdb and libudev.
I expect to see this kind of requirement for other packages in the
future, the latest pciutils for example benefits with the same trickery,
and though it still works without it i wonder for how long.
Regards.

  reply	other threads:[~2015-04-22 23:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-19 20:00 [Buildroot] Towards 2015.05-rc1 Thomas Petazzoni
2015-04-19 20:14 ` Bernd Kuhls
2015-04-19 21:02   ` Thomas Petazzoni
2015-04-20 22:04     ` Peter Korsgaard
2015-04-22 21:47       ` Bernd Kuhls
2015-04-22 22:18     ` Arnout Vandecappelle
2015-04-22 23:09       ` Gustavo Zacarias [this message]
2015-04-20 20:31 ` Arnout Vandecappelle

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=55382A2B.1090108@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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