On Fri Sep 03 1999 at 12:28, kiko wrote:
> On Fri, 27 Aug 1999, Pedro Brandao wrote:
>
> This is easy.
>
> > I have two questions
> > 1. Is init levels the correct place to put this initialization, or I
> > should only launch/stop the daemons in init and do the interface
> > configurations in /etc/sysconfig/network-scripts/ ?
>
> I'd certainly say the rc is the 'right' way to go. sysconfig is a RH
> nightmare concocted by linuxconf, and I'd recommend steering clear of that
> path, for it leads to madness. The rc scripts work fine once you've got
> hold of the small issues (see below).
That smells of total ignorance.
RedHat have implemented the way it is _supposed_ to happen. It's
inherited by linuxconf, not a result of it.
It's not called SysVinit for no good reason.
The right way to do it is to leave the init.d/* scripts alone, manage
the symlinks in rc?.d/* and put all the local config stuff in
/etc/sysconfig/
> Read into /etc/rc.d/rc to figure it out. I hate Redhat.
After using it in a large-ish corporate environment, including
producing redhat distribution cdroms for students, I have to disgree.
RedHat is brilliant.
However, it's not the only way to go. Doing it your own way isn't the
way, nor is slackware (which is a REAL backward step - unless you use
if for specific reasons, eg, hacker value for those who know exactly
what they are doing).
Cheers
Tony
