On Feb 16 15:16:51, Markus wrote: > On Thu, 16 13:03 , Joachim Schipper wrote: > > > > I'm sorry, but how does this work? It reads as if netstart now > > recognizes /etc/hostname.athn0.home as an alternative to > > /etc/hostname.athn0, but how does it figure out whether to use > > /etc/hostname.athn0.home or /etc/hostname.athn0.work? > > The idea is to be able to issue "sh /etc/netstart athn0.home" > and start the interface in question with the configuration > preseent in /etc/hostname.athn0.home. > > It does not find out anything by itself. Unless you call > netstart explicitly with those suffixed names, it will always take > hostname.athn0 by default. This way, this approach doesn't > interfere with the expected behaviour, yet provides a way to use > subconfigurations of interfaces in a convenient way. > > > 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 > > > @@ -104,7 +112,7 @@ > > > else > > > alias= > > > fi > > > - cmd="ifconfig $if $af $alias $name" > > > + cmd="ifconfig 4raw $if4 $af $alias $name" > > ^ ^ > > > case "$dt" in > > > dest) > > > cmd="$cmd $dtaddr" > > > > > > Those should be `, obviously. > > Interesting. That must have been wrapped up after I attached the > diff. See the original at http://flash.target23.de/doc/netstart.diff > > Regards, > /Markus
