Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: buildroot@busybox.net
Subject: [Buildroot] What to do about systemd/udev/eudev?
Date: Tue, 05 Mar 2013 22:22:36 -0600	[thread overview]
Message-ID: <1362543756.7276.13@driftwood> (raw)
In-Reply-To: <CALo-6+izu2DJE6+PGDSFqQLz9tA=dF7DxEOS2rVcrdGjMwcapg@mail.gmail.com> (from charles.krinke@gmail.com on Tue Mar  5 09:04:45 2013)

On 03/05/2013 09:04:45 AM, Charles Krinke wrote:
> As a user working on an AM3517 project with buildroot, I am having
> trouble seeing anything wrong with the existing implementation of
> mdev. We have 802.11 and USB disks that are plugged in and removed and
> the mdev subsystem seems to be working fine.
> 
> Having other alternatives is nice, but I hope we do not remove the
> existing mdev which appears to work fine in embedded systems.
> 
> Charles

The existing mdev does work great. (solar at gentoo and myself designed  
it, Denys has extended it quite a bit since then.) This would be an  
extension for those other packages.

(It may be posible to just call some notify program and not modify mdev  
at all.)

Rob

> On 3/5/13, Rob Landley <rob@landley.net> wrote:
> > On 03/04/2013 12:21:56 PM, Thomas Petazzoni wrote:
> >> However, if an application relies on libudev to get notifications  
> of
> >> devices appearing/disappearing, or other services, then of course,  
> it
> >> cannot work with mdev.
> >
> > Notifications are pretty straightforward. Should be possible for  
> mdev
> > to poke something simple and a shim library to provide the right
> > interface...
> >
> > Rob
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
> >
> 
> 
> --
> Charles Krinke
> 

  parent reply	other threads:[~2013-03-06  4:22 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 [this message]
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=1362543756.7276.13@driftwood \
    --to=rob@landley.net \
    --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