> I suppose you could argue that the project teams that integrate
> devices needing object reuse into Solaris are not responsible.
> Please convince your (and my) director that the responsibility
> lies somewhere else.
Gary,
There are two possibilities here, neither of which justifies delaying
this case.
Either:
1) there is no actual object reuse issue associated with scanners than
can be dealt with in software (rather than operational procedures like
signs reminding users to remove their documents from the scanner).
or:
2) There is an object reuse issue with the inclusion of ugen devices in
our default logindevperm by PSARC 2005/187 ("libusb should just work");
that inclusion allows the console user raw access to *any* USB device
lacking a more specific driver. Any object reuse issue present with
libsane/sane is ALSO present with just raw ugen. No change to the code
this project intends to deliver can fix this hypothetical object reuse
issue that exists today.
This project does not make this hypothetical problem worse. This
project cannot make this hypothetical problem better.
- Bill
