From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Date: Thu, 08 Jan 2004 03:43:50 +0000 Subject: Re: removable media revalidation - udev vs. devfs or static /dev Message-Id: List-Id: References: <200401012333.04930.arvidjaar@mail.ru> <20040103055847.GC5306@kroah.com> <20040108031357.A1396@pclin040.win.tue.nl> <20040108034906.A1409@pclin040.win.tue.nl> <20040108043506.A1555@pclin040.win.tue.nl> In-Reply-To: <20040108043506.A1555@pclin040.win.tue.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Andries Brouwer Cc: Greg KH , Andrey Borzenkov , linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org On Thu, 8 Jan 2004, Andries Brouwer wrote: > > I am even happy in a somewhat more general situation that you are. > If the kernel autopartitions (and make recognition of new partitions > hotplug events so that udev can create the device nodes), all is well. Yes. We _could_ do that, by just making a "we noticed the disk change" be a hotplug event. However, I'm loath to do that, because some devices literally don't even have an easily read disk change signal, so what they do is - assume the disk _always_ changed on open - do a quick IO to verify it and I'd be nervous about that kind of thing resulting in hotplug being called constantly if somebody rude just has an endless loop of "open()/close()". Linus ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ 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