[Slackbuilds-users] Suggestion for packages which require a startup file.

Robert Kelsen rkelsen at optusnet.com.au
Sun Jun 20 13:00:06 UTC 2010

> Let's see -
> A single rc.blah file, and edit rc.local{shutdown}.
>  or
> A single rc.blah, with a link to init.d, then links from that linked
> link to different run levels, a K{ill} link to stop the script in the
> proper run levels, and a S{tart} link to start the script in the
> proper run levels, along with figuring out the K/S number to get the
> order correct.
> I'm not entirely sure which one is easier to manage, maintain, and update ;-)

Tough crowd!

You've overcomplicated things a bit there.  

Have you ever actually seen this in operation on Slackware?

What I'm talking about actually makes packaging these things easier.

The rc.sysvinit script under Slackware is one of the last things to run
at boot up, by which time all of the important stuff has already been

You don't need thousands of symlinks.  You just need one.  Try it.

If you want to see a working example of what I mean, I've uploaded a package 
which I created that contains a simple script that loads a driver for my on 
board sensors.  You can download it and dissect it to see how I've used this 
functionality to simplify the packaging task.

The package is here:


md5sum: 343a1e639d9d3ae56b366beb0798200e
length: 1036

> "Then why are there all of these /etc/rc.d/rc*.d directories?"
> To provide compatibility to those proprietary packages that like to
> unnecessarily complicate things. At least Virtual Box gets this right.

"Right" is a subjective term... :)

And besides, this is just for the few additional things that require a
boot up script.  I'm not trying to advocate that you should switch your
whole setup.  That would be ridiculous.


More information about the SlackBuilds-users mailing list