Garrett D'Amore writes: > I've seen hardware implementations where "active scanning" cannot be > done while connected.
What about the questions I asked? What's the purpose of forcing a disconnect in the library itself _after_ doing a scan? Why do we do that? If there are interlocks between scanning and either the connect process itself or the entire connected state, then what part of the system should be responsible for enforcing those restrictions? Right now, it looks like it's left up to the application program -- which, for dladm(1M), means that the user typing the command has the responsibility. I don't think that makes sense. At a minimum, I think we're lacking some archtecture here. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
