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

[Dmitry Torokhov <dtor_core@ameritech.net>]

On Friday 01 July 2005 23:51, Greg KH wrote:
> 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.)

I believe you can make it work ;)

> 
> > 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 :)
> 

You misunderstood me. I know that both bind and unbind are in the same
directory. I am talking about reconnect/rescan being in one directory
while bind/unbind are in the other while they all perform related
operations.

-- 
Dmitry