Re: RFC: new network config

[Steve Dunham <dunham@cse.msu.edu>]

Christian Hammers <ch@lathspell.westend.com> writes:

> On Sun, Feb 07, 1999 at 03:50:39PM +0000, Alexander Koch wrote:
> > > iface=eth0 ip=192.168.1.1 mask=255.255.255.0 ipx_net=00000010
> > > iface=eth1 dhcpclient=true
> > > iface=eth2 ip=172.16.0.0 prefix=/16
> > > iface=sm0  ip=44.1.2.3 mask=255.255.255.0 callsign=VK3TYD delaystartup=true
> > 
> > Looks awful. Hard to maintain if you edit this line with vi and
> > word wrap or something anyway. Besides, what is the problem with

> Ok, it is really a matter of taste.
> 
> But just before I thought you have convinced me, I got another idea:
> What about the following. It looks nearly exact like the nameD way you
> proposed but it has the following advantages:

> a) it is as good readable like the BIND (with '{' and '}') way
> b) it is a common unix standard, too
> c) it gives you the possibility to work with one-liner, too

> interface eth2 \
> 	ip=192.168.1.1 \
> 	netmask=255.255.255.0 \
> 	ipx_net=0x000010

> interface eth2 \
> 	dhcpclient=true
> 

Take off the \ at the end of the lines.  (Also a common Unix standard
used in email - lines that begin with whitespace are a continuation of
previous lines.)


Steve
dunham@cse.msu.edu