Date: Thu, 19 Jun 2003 17:05:42 -0700 (PDT)
From: Linus Torvalds <torvalds@transmeta.com>
To: Steven Dake <sdake@mvista.com>
cc: Werner Almesberger <wa@almesberger.net>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] udev enhancements to use kernel event queue
In-Reply-To: <3EF24A70.4010608@mvista.com>
Message-ID: <Pine.LNX.4.44.0306191700010.1987-100000@home.transmeta.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1375
Lines: 32


On Thu, 19 Jun 2003, Steven Dake wrote:
>
> A serialization methodology can be built on /sbin/hotplug, but it has 
> all of the problems that Linus previously talked about for a kernel 
> event queue.  The difference is that the problem is moved to userland.

Having event ordering is a trivial matter, and I'm not against adding a
sequence number to /sbin/hotplug as part of the environment, for example. 

What I worry about is the situation where one big deamon handles 
everything, which makes it impossible to "hook in" to the thing without 
understanding the one big thing.

The thing that makes /sbin/hotplug so wonderful is that it's stateless,
and if you want to hook into it, it's absolutely _trivial_.  Look at the 
default script there in redhat-9 for example, and it's obvious how to hook 
up to certain events etc.

And why do people care about serialization anyway? Really? The whole 
notion is ludicrous. /sbin/hotplug _shouldn't_ be serialized. 
Serialization is bad. You should look at whatever problems you have with 
it now, and ask yourself whether maybe it should be done some other way 
entirely.

		Linus

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/