On Thu, Jun 16, 2005 at 02:04:04PM -0700, David Wolfskill wrote: > On Thu, Jun 16, 2005 at 01:50:33PM -0700, Brooks Davis wrote: > > ... > > > Agreed. There's actually some demand for a default for wired interfaces > > as well. If nothing else I know the EmuLab people would like one > > so they didn't have to use their own scripts to configure all the > > interfaces. I've thought about it a bit. I'm leaning towards a > > default_ifconfig variable plus a new magic ifconfig_<if> option NONE to > > cause the default option not to be used. > > >From the perspective that NIC-specific variables are of the form > "ifconfig_${NIC}" (e.g., ifconfig_lo0; ifconfig_ed0; ifconfig_xl0), > might it make at least as much sense to call it "ifconfig_default" (or > something similar)? I'm divided on that one. The problem is that users may want to name an interface "default" and this would break that. I like the symetry and the sort order of ifconfig_default, but I'm concerned about exceptions to the namespace as well. I'm somewhat tempted by ifconfig_DEFAULT. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:36 UTC