Keyur Desai writes: > > OK. Then what are users told? > > We will be delivering both nbtd(1M) and nbt(4) man pages and that end > users will have access to them. (I might have caused some confusion by > stating that man pages were included for completeness purposes)
I see ... In that case, I'd recommend paring down the information (particularly about the exit codes) so that it's clear that the intended administrative interface is SMF. The goal I'm aiming at here isn't that private interfaces are necessarily "secret," but rather that we don't document and advertise them in a way that could lead users into depending on them. > In addition to the man pages being delivered, the Windows > Interoperability documentation (Getting Started Guide, Admin Guide and > Troubleshooting Guide) will be updated to cover these changes. Does smb(4) or some other existing man page need a pointer to the nbtd page? (Not that I care much, but "nbtd" is a pretty obscure name for the service. "nbt" would be better, and just plain "netbios" would probably be even better still ... though I realize it doesn't provide _all_ of NetBIOS.) -- 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
