From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: about split the udev
Date: Fri, 23 Jan 2004 00:34:08 +0000 [thread overview]
Message-ID: <20040123003408.GB16052@kroah.com> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8402D4EE96@PDSMSX403.ccr.corp.intel.com>
On Fri, Jan 23, 2004 at 12:01:29AM +0100, Kay Sievers wrote:
>
> Here is the next updated updated version to apply to the lastet udev.
> I've added infrastructure for getting the state of the IPC queue in the
> sender and set the program to exec by the daemon. Also the magic key id
> is replaced by the usual key generation by path/nr.
Very nice, I applied this.
> It looks promising, I use it on my machine and my 4in1 USB-flash-reader
> connect/disconnect emits the events "randomly" but udevd is able to
> reorder it and calls our normal udev in the right order.
Hm, how are you supposed to start up udevd? like:
./udevd ./udev
?
> Should we start the daemon if noone listens, when the sender is called?
Yes.
> Should we convert our udev to a daemon, or stay with the exec?
I don't know. I was thinking of turning our udev into the daemon, but
with this structure we might not need to. Let's play around with this
current structure for a bit now and see how it works out.
thanks,
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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:[~2004-01-23 0:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 7:53 about split the udev Ling, Xiaofeng
2004-01-12 9:36 ` Martin Waitz
2004-01-12 13:54 ` Kay Sievers
2004-01-12 16:23 ` Martin Waitz
2004-01-12 16:28 ` Robert Love
2004-01-12 17:51 ` David Zeuthen
2004-01-13 1:12 ` Greg KH
2004-01-13 1:29 ` Greg KH
2004-01-13 19:05 ` Tristan Wibberley
2004-01-13 20:36 ` Greg KH
2004-01-15 14:36 ` Ling, Xiaofeng
2004-01-15 21:45 ` Greg KH
2004-01-21 13:38 ` Kay Sievers
2004-01-22 0:27 ` Kay Sievers
2004-01-22 1:08 ` Kay Sievers
2004-01-22 23:01 ` Kay Sievers
2004-01-23 0:34 ` Greg KH [this message]
2004-01-23 1:00 ` Kay Sievers
2004-01-23 3:37 ` Kay Sievers
2004-01-23 3:46 ` Greg KH
2004-01-23 3:58 ` Kay Sievers
2004-01-23 4:04 ` Greg KH
2004-01-24 16:06 ` Ling, Xiaofeng
2004-01-24 16:57 ` Kay Sievers
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=20040123003408.GB16052@kroah.com \
--to=greg@kroah.com \
--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.