> To continue with the Slackware vs Red Hat comparison, let us contrast
> their network startup. In slackware, this is handled by
> /etc/rc.d/rc.inet[1,2], called in that order. These are human readable;
> all network variables used (including those set by install scripts) are
> set directly in the scripts where they are used. Consequently, the
> scripts are trivial to modify by hand and you can read them and see how
> they work at a glance. rc.inet1 is really totally trivial and yet
> totally effective at starting up a network -- ifconfig, route, done.
> rc.inet2 is messier, but still pretty readable and easy to change if you
> know /bin/sh at all (and even if you don't).
>
Can you tell me how you start/stop/restart a service on Slackware,
which may require a series of commands in the correct order? On RedHat,
you can do
# cd /etc/rc.d/init.d
# ./service start|stop|restart
It is that easy. Also I can start/stop a network interface with
# ifup/ifdown eth0
Everything is automatic. My ifup even knows Linux 2.0/2.1/2.2 since
some network commands are changed. Try that in Slackware.
H.J.
