> So maybe the nice friendly presentation doesn't need to be here. Maybe > it doesn't need to be in the "default" output at all. (Whatever that > means.) > > AFAICT, the sites that tune these values *usually* have some harebrained > idea that turning off autonegotiation and forcing a fixed speed/duplex > setting is a good idea. > > MAYBE, we can provide a short cut for these users in the UI... e.g. > "force-link-speed-duplex" magic property or somesuch. > > For example, the output could show: > > LINK SPEED DUPLEX MODE > bge0 1G full autonegotiated > hme0 100M half forced > > Users who want the full control, as well as the full output, could > access the properties directly. > > Thank God they finally required full-duplex and autonegotiation for 10G. > > Thoughts?
Would the properties still end up in the show-linkprop output? If so, even well-behaved admins are still subjected to a mountain of properties that they shouldn't even be using, which seems bad. Or are you proposing some way to hide these properties? (I'm nervous about that as well.) If we're sure this stuff will be off the beaten path, maybe we could reduce the number of properties to just `cap', `advcap', and `lpadvcap' (or somesuch) with a commas-separated list of values? -- meem
