> Why is the ifconfig keyword to add an interface to a bridge "add" and the
> keyword to add an interface to a trunk "trunkport"?
{ "add", NEXTARG, 0, bridge_add },
..
{ "trunkport", NEXTARG, 0, settrunkport },
The ifconfig argument grammar is driven by a flat table, as a result
it is difficult to share keywords. There are a few hacks, not sure if
we need more.
Also for a time, brconfig was a completely seperate program, and in part
it was trying to escape from making ifconfig more complex. Then we gave
up because having two programs operating on interfaces was worse.
