[svlug] Writing start-up scripts...

[Rick Moen]

begin Dagmar d'Surreal quotation:

> After a lot of anguishing about how the heck I was going to design the
> init scripts for a five interface box I was running about a year ago, I
> came to the painful conclusion that putting configuration information into
> /etc/syscconfig/network was pretty much the only way to go.

I call it painfully incompetent.  Trying to understand what the hell the
init scripts do becomes a protracted exercise in dereferencing
variables.

Sometimes I get so annoyed at it that I rip all that crap out and
replace it with the straightforward ifconfig and route statements that
God Intended.

> Trying to work out an elegant way to be able to bring up and put down
> (heh) interfaces in a manner that would take into account both firewalling
> tables and the possibility of transient interfaces (modem being a good
> example, 802.11 via PCMCIA being even more evil) as well as network
> services bound to their respective interfaces, using
> /etc/sysconfig/network/${INTERFACE_NAME}/${SEVERAL_DIFFERENT_FILES} was
> the only way I could conveniently access organize the data so that one
> dinky little shell script (only about 40K) could parse and deal with it
> all.

"ifconfig [interface] down" works in one direction, and standard
ifconfig and route statements in the other.  No?  You honestly prefer to
parse configuration files?

-- 
Cheers,                                Before enlightenment, caffeine.
Rick Moen                              After enlightenment, caffeine.
rick at linuxmafia.com