>     To pass a line directly to ifconfig and prevent it from being
>>     interpreted as a packed format, use !ifconfig \$if <flags>."
> 
> Yes.
> 
>> (I think I may change my files to "!ifconfig ..." format
>> now, it's ugly but it will avoid errors; not least because
>> then I can use /prefix notation rather than netmasks).
> 
> Yes.  I'm switching to !ifconfig for everything but trivial addresses.


How about a minimal change to hostname.* processing that adds a keyword used
to pass the rest of the line to ifconfig.  Minimal change that is, IMHO,
less obnoxious that typing !ifconfig \$if.  Maybe something like

        pass <ifconfig args for interface>

--- netstart    Sun Dec 11 13:31:14 2011
+++ netstart.new        Tue Nov 27 10:57:27 2012
@@ -79,6 +79,9 @@
                "!"*) # parse commands
                        cmd="${af#*!} ${name} ${mask} ${bcaddr} ${ext1} ${ext2}"
                        ;;
+               "pass")
+                       cmd="ifconfig $if ${name} ${mask} ${bcaddr} ${ext1} 
${ext2}"
+                       ;;
                "dhcp")
                        [ "$name" = "NONE" ] && name=
                        [ "$mask" = "NONE" ] && mask=

Reply via email to