On 2012-02-16, Markus <li...@neuronenwerk.de> wrote: > On Thu, 16 16:53 , Jan Stary wrote: >> > > What's the >> > > advantage over symlinking /etc/hostname.athn0 appropriately, if you want >> > > to use netstart? >> > >> > It's easier to issue a "sh /etc/netstart athn0.home" on the >> > commandline than unlinking and relinking files before calling >> > netstart. >> >> So, you find it a reasonable price to have an unsupported /etc/netstart >> for not having to painstakingly type this? >> >> # ln -sf /etc/hostname.athn0.here /etc/hstanme.athn0 >> # sh /etc/netstart > > Well, as you might have gathered by the fact that I sent a diff, > I took into account that this small change could go into > netstart to just support such operations out of the box. > > It's however not up to me to decide this. If the majority of > relevant people do think this is bloat, I can get along with > it. Consider it a suggestion. On the other hand, it would not > harm nor complicate netstart really.
I only see this as being marginally useful as-is. Why would you want to configure every network interface individually? You might as well just use a separate script in that case. I'd rather have an option to specify this be used for *all* hostname.if files so you could "sh /etc/netstart -s mobile" etc. Or maybe easier to have "netstart -d /etc/net/home" etc to look in a different directory (though this has implications for /etc/security and changelist). With either of these, it would probably make sense to add "netstart_flags" support to rc.conf/rc as well.
