From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevsynthesize as a udevstart+coldplug replacement
Date: Wed, 24 Aug 2005 20:24:51 +0000 [thread overview]
Message-ID: <20050824202451.GC10689@vrfy.org> (raw)
In-Reply-To: <20050823191542.GA29091@vrfy.org>
On Wed, Aug 24, 2005 at 11:31:19AM +0200, Marco d'Itri wrote:
> On Aug 23, Kay Sievers <kay.sievers@vrfy.org> wrote:
>
> > Here is "udevsynthesize" a possible replacement for the udevstart/coldplug
> > combination we currently have. Usually very early in the boot process, it
> What are the benefits of using C instead of shell scripts?
Nobody knows. I like it, probably. :)
I like to connect directly to the daemon socket and it was easy to do, cause
it's was a bit similar to udevstart.
> An obvious disadvantage is that it would be harder to add support for
> new bus types.
Sure, it's easier to copy another *.rc script than to add a *_handler(),
but udev has a release frequency high enough, that I don't think this would
be a real problem.
We will need to find out _what_ we need to do on coldplug, and not _how_ to do
it, right?
Kay
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-08-24 20:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 19:15 udevsynthesize as a udevstart+coldplug replacement Kay Sievers
2005-08-23 19:46 ` Mika Penttilä
2005-08-23 20:03 ` Kay Sievers
2005-08-23 20:09 ` Mika Penttilä
2005-08-23 20:47 ` Per Svennerbrandt
2005-08-24 3:50 ` Alexander E. Patrakov
2005-08-24 9:29 ` Marco d'Itri
2005-08-24 9:31 ` Marco d'Itri
2005-08-24 11:14 ` Olivier Blin
2005-08-24 19:37 ` Kay Sievers
2005-08-24 19:52 ` Olivier Blin
2005-08-24 20:05 ` Kay Sievers
2005-08-24 20:09 ` Kay Sievers
2005-08-24 20:18 ` Marco d'Itri
2005-08-24 20:18 ` Thierry Vignaud
2005-08-24 20:24 ` Kay Sievers [this message]
2005-08-24 20:27 ` Kay Sievers
2005-08-24 20:36 ` Kay Sievers
2005-08-24 20:40 ` Marco d'Itri
2005-08-24 20:42 ` Olivier Blin
2005-08-24 21:19 ` Thierry Vignaud
2005-08-25 6:43 ` Christian Zoz
2005-08-25 8:24 ` Marco d'Itri
2005-08-25 10:31 ` Christian Zoz
2005-08-25 10:36 ` Marco d'Itri
2005-08-25 18:20 ` Bill Nottingham
2005-08-25 18:33 ` Marco d'Itri
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=20050824202451.GC10689@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.