From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Nottingham Date: Tue, 06 Apr 2004 20:49:24 +0000 Subject: Re: udev and the kernel's idea of a device Message-Id: <20040406204923.GD4853@nostromo.devel.redhat.com> List-Id: References: <20040406192223.GA4853@nostromo.devel.redhat.com> In-Reply-To: <20040406192223.GA4853@nostromo.devel.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Greg KH (greg@kroah.com) said: > > > Ick. That just doesn't make much sense. > > > > And yet, there are drivers that do that. > > Which ones? I'd be glad to go fix that up. Ah, I was thinking end_request, but that got fixed in 2.6. That will teach me to talk without checking. > > > As it is very simple > > > to translate from the kernel device name to the real /dev name at any > > > point in time using udevinfo, why is that not sufficient? > > > > Requires integrating udevinfo into various random userland apps... > > it's certainly doable, but it just doesn't seem very clean. > > I agree, but what random userland apps are you talking about? Off the top of my head, iostat, cdrom capability checkers, fbset and friends, etc. But, in the long run, see below. > Can you think of a cleaner suggestion? Drill HAL throughout the entire OS. :) Bill ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ 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