Re: [RFC] bind and unbind drivers from userspace through sysfs

[Greg KH <greg@kroah.com>]

On Fri, Jul 01, 2005 at 11:25:30PM -0500, Dmitry Torokhov wrote:
> On Friday 01 July 2005 17:31, Greg KH wrote:
> > Putting it 
> > in every device directory would make the 20K scsi device people very
> > unhappy as I take up even more of their 31bit memory :)
> > 
> 
> I see. That would be an argument for folding all such operationsinto one
> attribute with bus-specific multiplexor. But really, 20K scsi people are
> probably better off without sysfs (they should still have hotplug events
> as far as I can see so hotplug/usev should still work).

The 20k scsi people need sysfs.  They did the backing store patches for
it, to make it work sane on their boxes.  They need persistant device
naming more than almost anyone else.  udev previously would not work
without sysfs.  For 2.6.12, it now almost can (haven't tried for sure,
but I think we are now there.)

> Just to reiterate - by beef is that if you put [un]bind into separate
> directory similar operations will be split across 2 subdirectories. 

But I didn't.  They are now both in the same directory.  Look at Linus's
tree :)

thanks,

greg k-h
-
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/