Vasumathi Sundaram writes: > > I am working on cleaning up the ndd status reports and moving them to > mdb as macros. (CR > *http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=4616660)*
Yay! > The ndd report for ip_ill_status does not give much information except > for the ill address, read queue and the write queue pointers; and for > ip_ipif_status, it displays the local address, mtu, flags and zone for Interface name seems sort of important here. Other than that, I'm reasonably happy with that little bit of information; I can always use ::print to extract details. > each ip interface which can already be seen with ifconfig. In many cases, there should be an analog of the command line tools inside mdb (e.g., "::ifconfig"), if there isn't one already. It's not a complete duplicate as it shouldn't allow changes (that wouldn't really make sense), and (unlike a user utility) it _should_ print internal pointers where meaningful. The reason for having these is to simplify support and bug filing. If there are dcmds that are similar enough to user-level features, then users who are less intimate with the stack will be encouraged to use them and report things that they find. I realize that might be "not this project," but it's something to think about when you're doing this. If the functionality you're going to add would be subsumed by "::ifconfig -a", then I think that just doing the latter would be better in the long term. -- 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 _______________________________________________ networking-discuss mailing list [email protected]
