From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Perez-Gonzalez, Inaky" Date: Fri, 11 Apr 2003 22:59:36 +0000 Subject: RE: [ANNOUNCE] udev 0.1 release Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org > From: Greg KH [mailto:greg@kroah.com] > > > From: Greg KH [mailto:greg@kroah.com] > > > > > > But I can do a lot to prevent losses. A lot of people around here point > > > to the old way PTX used to regenerate the device naming database on the > > > fly. We could do that by periodically scanning sysfs to make sure we > > > are keeping /dev in sync with what the system has physically present. > > > That's one way, I'm sure there are others. > > > > This might be a tad over-simplification, but sysfs knows by heart when > > anything is modified, because it goes through it's interface. If we > > only care about, for example, devices, we could hook up into > > device_create() [was this the name?]; line up in a queue all the > > devices for which an plug/unplug event hasn't been delivered to user > > space and create symlinks in /sysfs/hotplug-events/. > > > > Each entry in there is a symlink to the new device directory, named with an > > increasing integer for easy serialization. When the event is fully > > processed, remove the entry from user space. >=20 > Um, how do you show a symlink to a device that is no long there when the > device is removed? :) Broken link - removal event [my fault, should have explained]; still, this is kind of broken because of what you mention in the next paragraph and because it limits you to just two types of events - addition and removal. I like better the having of a file where you can get events from (that at the end goes with the select() thingie). > In the end, it's a nice idea, but the current one is much simpler, and > works today :) Sure - let's just not forget it and build on top of it little by little. I=F1aky P=E9rez-Gonz=E1lez -- Not speaking for Intel -- all opinions are my= own (and my fault) ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger= =20 for complex code. Debugging C/C++ programs can leave you feeling lost and=20 disoriented. TotalView can help you find your way. Available on major UNIX = and Linux platforms. Try it free. www.etnus.com _______________________________________________ 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