From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] What to do about systemd/udev/eudev?
Date: Mon, 04 Mar 2013 20:12:29 +0200 [thread overview]
Message-ID: <5134E40D.6@petroprogram.com> (raw)
In-Reply-To: <CAKAx1cjwOtqE9ZK1RnB0=wWXhVw+8end_j8roL8RZ9aZwAj=EQ@mail.gmail.com>
4.3.2013 12:53, Lionel Orry kirjoitti:
> Another note, Funtoo Linux (a gentoo derivative) team is experimenting
> with usage of mdev as a complete udev replacement for the whole
> distro. It seems to work and tries to prove the scalability of mdev
> which sounds promising. Here are some files resulting from these
> attempts:
>
> - mdev from busybox configured for funtoo (1 tiny patch and simple
> configuration in the ebuild):
> https://github.com/slashbeast/foo-overlay/tree/master/sys-fs/mdev-bb
> - repository for notes and mdev config/init scripts (may be worth a
> look at mdev.conf and mdev.init):
> https://github.com/slashbeast/mdev-like-a-boss
>
> What I wanna say, is that it *may* sound reasonable to strongly
> suggest people to stick with mdev as much as they can.
>
> Cheers
> Lionel
Yes, I for one can confirm that if you don't need anything else than to
populate /dev with nodes and maybe few
symlinks then mdev is perfectly fine.
I have run buildroot xorg with mdev without any problems.
*But* ... (and this is a big but) I have not tested how it reacts to
kernel events after boot when you *plug/unplug* devices and if mdev
is capable of *running programs/scripts when some event happens*.
If Funtoo can make it work and make it also work seamlessly with all the
other crazy stuff (network-manager, and some other
gnome stuff) then I will kick out udev from my system in a nanosecond :-)
Regards
Stefan
next prev parent reply other threads:[~2013-03-04 18:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 12:09 [Buildroot] [PATCH 1/1] Updated systemd to version 197 Olivier Schonken
2013-03-03 18:54 ` [Buildroot] What to do about systemd/udev/eudev? Thomas Petazzoni
2013-03-04 10:16 ` Kevin Chadwick
2013-03-04 10:53 ` Lionel Orry
2013-03-04 18:12 ` Stefan Fröberg [this message]
2013-03-04 18:21 ` Thomas Petazzoni
2013-03-04 18:25 ` Stefan Fröberg
2013-03-04 18:30 ` Thomas Petazzoni
2013-03-05 18:08 ` Stefan Fröberg
2013-03-05 18:51 ` Thomas Petazzoni
2013-03-05 8:21 ` Rob Landley
2013-03-05 15:04 ` Charles Krinke
2013-03-05 18:15 ` Thomas Petazzoni
2013-03-06 4:22 ` Rob Landley
2013-03-04 18:37 ` Baruch Siach
2013-03-04 19:08 ` Stefan Fröberg
2013-03-04 19:30 ` Peter Korsgaard
2013-03-05 8:24 ` Rob Landley
2013-03-05 6:40 ` Arnout Vandecappelle
2013-03-05 18:55 ` Thomas Petazzoni
2013-03-06 7:52 ` Arnout Vandecappelle
2013-03-06 8:24 ` Thomas Petazzoni
2013-03-06 8:40 ` Arnout Vandecappelle
2013-03-04 19:31 ` Peter Korsgaard
2013-03-04 19:52 ` Kevin Chadwick
2013-03-04 20:14 ` Thomas Petazzoni
2013-03-04 19:47 ` Attila Kinali
2013-03-04 20:17 ` Thomas Petazzoni
2013-03-05 9:53 ` Attila Kinali
2013-03-05 18:19 ` Thomas Petazzoni
2013-03-05 18:37 ` Stefan Fröberg
2013-03-07 18:45 ` [Buildroot] [PATCH 1/1] Updated systemd to version 197 Stefan Fröberg
2013-03-07 19:20 ` Stefan Fröberg
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=5134E40D.6@petroprogram.com \
--to=stefan.froberg@petroprogram.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox