From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev - advanced user query options
Date: Tue, 20 Jan 2004 00:08:32 +0000 [thread overview]
Message-ID: <20040120000832.GB5656@kroah.com> (raw)
In-Reply-To: <20040111023300.GA4762@vrfy.org>
On Mon, Jan 19, 2004 at 08:23:35PM +0100, Olaf Hering wrote:
> On Mon, Jan 19, Greg KH wrote:
>
> > On Mon, Jan 19, 2004 at 10:11:19AM +0100, Olaf Hering wrote:
> > > On Fri, Jan 16, Greg KH wrote:
> > >
> > > > I agree. I envision that when udev splits up into a daemon and sending
> > > > program, it will also spin off a "query the database" program to handle
> > > > this.
> > >
> > > udev? daemon? huh?
> >
> > udev will be split into a daemon one of these days. It's needed to make
> > sure we act apon hotplug events in the proper order.
>
> How does a daemon help in that situation?
We can reorder events to their proper order.
> event foo
> SEQNUM=1 ACTIONd
> SEQNUM=2 ACTION=remove
> SEQNUM=3 ACTIONd
>
> How will you make sure that #2 is processed before #3, even if #3
> arrives earlier? And why would it matter for mknod?
Sleep until we see #2. The devices could be different or we don't want
to add and then remove a node that we should have removed and then
added.
> I bet that a simple record '#3 add' in the database will make sure that
> #2 is handled as bogus event.
But we got #2 after #3, right? We already added the node. Now we
remove it? What if it was pointing to a different device?
Anyway, a small daemon should work nicely to handle stuff like this.
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
prev parent reply other threads:[~2004-01-20 0:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 2:33 [PATCH] udev - advanced user query options Kay Sievers
2004-01-11 2:37 ` Robert Love
2004-01-11 3:17 ` Kay Sievers
2004-01-12 18:05 ` David Zeuthen
2004-01-12 21:21 ` Greg KH
2004-01-12 21:22 ` Greg KH
2004-01-12 23:56 ` Kay Sievers
2004-01-13 1:04 ` Greg KH
2004-01-13 1:21 ` Kay Sievers
2004-01-13 4:35 ` Kay Sievers
2004-01-13 18:29 ` Greg KH
2004-01-13 19:47 ` Greg KH
2004-01-15 13:54 ` Olaf Hering
2004-01-15 20:56 ` Greg KH
2004-01-15 21:16 ` Kay Sievers
2004-01-15 21:21 ` Greg KH
2004-01-16 9:49 ` Olaf Hering
2004-01-16 9:57 ` Kay Sievers
2004-01-16 21:54 ` Greg KH
2004-01-19 9:11 ` Olaf Hering
2004-01-19 17:47 ` Greg KH
2004-01-19 19:23 ` Olaf Hering
2004-01-20 0:08 ` Greg KH [this message]
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=20040120000832.GB5656@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.