> That aside, I think we've got a fair bit to cover here, and we can > either turn /usr/sbin into a trashcan by flooding it with *adm > utilities, each with a tiny view of the Universe, or we can put > natural groupings together, and live with the complexity there.
Yes, and as I said I think those natural groupings come down to close examination of the administrative objects and actions. To my knowledge, no one has done that at this point. That is, we need to look at the ndd tunables and other mechanisms used to administer those layers, along with RFEs to administer those layers, and get a feel for the lay of the land. > In this case, I see supporting the TCP/IP family of transport and > network layer protocols in one place as a good thing, just as dladm is > a good way to handle all of the datalink layer protocols. > > We don't want to have wifiadm, so why should there be tcpadm? As above, there's no wifiadm because the objects and actions overlap sufficiently to benefit from putting under the dladm umbrella. -- meem
