Re: /etc/init.d/network is too simple?
On Fri, Apr 16, 1999 at 10:45:16PM +0200, Piotr Roszatycki wrote:
> > In my /etc/init.d/network, I use commands like this:
> >
> > ifconfig eth0 down
> > ifconfig eth1 down
> [...]
> > This guarantees that running /etc/init.d/network flushes all my network
> > settings and restores them to defaults. Since I do a lot of experimentation
> > (working on the Tunnel Vision VPN software, etc) this saves me a lot of
> > time.
>
> This way doesn't make possible to restart only one interface.
> I think, our goals are:
> * starting/stoping choised interface(s)
> * easy configuration (ip and netmask, broadcast and network are calculated)
> * support for multialiasing, traffic shaper, multisubnets on one device
> * setting routing table and proxyarp table
> * ip-up.d and ip-down directory like in ppp package.
> * possibility of including raw shell commands (ifconfig, route)
> It is hard to make, isn't it?..
I don't think the added complexity is worth it. Since you can restart _all_
your interfaces in a few milliseconds (unless you have an _awful_ lot of
interfaces, in which case you can write your own script to meet your special
needs), any extra stuff in /etc/init.d/network is just a waste.
I really hate Red Hat's network start scripts. Under the pretense of being
more flexible, they severely restrict what I can do without hacking things
to pieces. In Debian, I simply edit /etc/init.d/network and tell it exactly
what I want to run.
Now, if you have _dynamic_ interfaces to worry about (to me, that includes
dhcp, pcmcia, ppp, etc) they don't belong in /etc/init.d/network anyway.
I'm not against some kind of plan to manage those more easily. The PPP
ip-up.d/ip-down.d dirs are great, and maybe it makes sense to extend the
concept somehow.
I hope we don't overcomplicate things like pcmcia does. With "schemes,"
configuration files that are really big shell scripts, and other weird
stuff, it makes me dizzy just finding the line that sets my pcmcia
ethernet's IP address.
I'm not against a more complex config scheme, but just keep _static_
configuration in one place (/etc/init.d/network) and _dynamic_ configuration
elsewhere. Most systems have little or no dynamic configuration, so we
should keep those systems as simple as possible.
Have fun,
Avery
Reply to: