Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] What to do about systemd/udev/eudev?
Date: Mon, 04 Mar 2013 20:31:34 +0100	[thread overview]
Message-ID: <87ppzf9d2h.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20130303195436.49654719@skate> (Thomas Petazzoni's message of "Sun, 3 Mar 2013 19:54:36 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 Thomas> So in fact building udev only without systemd doesn't seem like
 Thomas> a good idea moving forward. Therefore, I see two options:

 Thomas>  (1) Follow the upstream decision, and simply make udev available only
 Thomas>      if the init system is systemd. Unlike some other distributions, we
 Thomas>      never had the the desire of fighting against upstream. If someone
 Thomas>      is dissatisfied with decisions made by upstream projects, then
 Thomas>      that someone should go upstream and fix the problem here.

 Thomas>      This is the solution I would personally prefer. If some were using
 Thomas>      udev for some reason and mdev doesn't work for them, then we can
 Thomas>      probably help make mdev better where needed.

 Thomas>  (2) Package eudev and use it for non-systemd systems, and use the
 Thomas>      built-in udev for systemd systems. There is of course the problem
 Thomas>      that udev is not stand-alone: it provides a library, and there are
 Thomas>      some uncertainties on whether the libudev library will remain
 Thomas>      source-compatible between eudev and system's udev.

 Thomas> Thoughts?

I think option (1) is the best as well.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2013-03-04 19:31 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
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 [this message]
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=87ppzf9d2h.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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