On Thursday 19 August 2004 8:32 am, Alan Stern wrote: > On Thu, 19 Aug 2004, Alexander N. Kozhushkin wrote: > > > 3. The call completes without waiting for the device. The file > > descriptor has been unusable for I/O operations on the device since > > the disconnection, therefore the result of the call is not affected > > if the device has been connected again. The result of the call > > depends on the kind of the called function and other conditions. > > However, the 'close' function closes the file, and there are system > > calls which produce a specific error code in such situations. > > As I understand it, the kernel should always use your option 3.
Certainly USB should do it that way in 2.6, although the device drivers can try to implement other behavior. I think that's made a big improvement in robustness. Other hotpluggable busses (or 2.4) may not act quite the same. - Dave ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
