On Thu, Feb 16, 2012 at 11:49:03AM +0100, Markus wrote:
> occasionally I'm in the situation where having multiple
> configurations for a single network interface are handy to have.
> Most seamlessly, [multiple wifi networks] could be handled by using an
> arbitrary extension to the hostname.if files, separated by and
> additional dot (e.g. hostname.athn0.home, hostname.em0.bak20120223).
>
> Below a diff to /etc/netstart is attached, that strips the
> suffix including the dot from hostname.if.suffix (if it is
> present) and otherwise allows such files to be used. I tried
> to change the code of netstart as minimally as possible.
>
> An interesting side-effect is the ease with which wifi cell
> changes can now be handled by ifstated.
>
> I'd suppose that this must scratch the itch of other users, too.
> However as this is only a rough guess, I'm curious to hear some
> opinions on it.
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? What's the
advantage over symlinking /etc/hostname.athn0 appropriately, if you want
to use netstart?
Maybe I just don't get it.
> @@ -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.
Joachim
--
PotD: graphics/libkexiv2 - kde wrapper around exiv2
http://www.joachimschipper.nl/
