# slackwareland
# just installed a new qpopper!
killall inetd
inetd
# looks like I changed some apache crap
kill -HUP `cat /home/apache/conf/httpd.pid`
# i'm gonna restart sendmail
ps fax|grep accepting
kill <pid>
sendmail -bd
# i think I'll change what daemons i start when i boot this puppy. i'll
# probably add ntpd, add test sendmail that i'm experimenting with,
# remove an ip, add a new subnet, and change my gateway.
vi /etc/rc.d/rc.inet1
vi /etc/rc.d/rc.inet2
welcome to a day in the life of a slackware machine... i'd rather hack
around my slackware box than a redhat beast. some of those restarts
probably took less time than redhat. i can easily write a script to do
anything i think is too time-consuming. editing my startup info was
probably a good 15 minutes quicker than trudging through the redhat init
system. i think redhat is fine in a server environment where you want all
your machines to be similar and you need to be able to pass of
administration to some other bozo any time. for my workstation, where
about 15% of all the programs on the machine (no, seriously) have been
hand compiled for some reason or another, and I make changes to my
configuration every couple hours, it's going to be slackware until the day
I die.
---
[EMAIL PROTECTED]
On Tue, 26 Jan 1999, H.J. Lu wrote:
> > 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.
> -====---====---====---====---====---====---====---====---====---====---====-
> to unsubscribe email "unsubscribe linux-admin" to [EMAIL PROTECTED]
> See the linux-admin FAQ: http://www.kalug.lug.net/linux-admin-FAQ/
>
