Richard L. Hamilton writes: > But just maybe there are times when being able to simply _understand_ > something private, without necessarily having to dig into C source code, > might not be a bad idea, if only to be aware that it's something that has to > be done, and where it's being done, so that one can for example (as in your > case?) be aware of its necessary place in the sequence of events before and > after.
And, for that purpose alone, I'd recommend finding a way to make as many detailed design documents public and accessible as possible. That's where this sort of documentation belongs -- in its proper context as an implementation detail of the system, and not in a man page where it will (inevitably) be confused with a supported feature, and hurt someone. What's next? A man page for ip_wput_local(9F)? -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> 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 _______________________________________________ opensolaris-discuss mailing list [email protected]
