1of12 wrote:
The Slackware website is correct, your interpretation of it is wrong. It says nothing about not using sysvinit.
System V Compatibility
Since version 7.0, Slackware includes System V init compatibility. Many other Linux distributions make use of this style instead of the BSD style. Basically each runlevel is given a subdirectory for init scripts, whereas BSD style gives one init script to each runlevel.
How and why do you include compatibility with something you're supposedly already using?
Before 7.0 Slackware didn't understand the directory-based runlevel approach of sysvinit. After rc.sysvinit was included, it does.
1of12 wrote:If you can invoke init from the terminal as root to change run levels, then you are running sysvinit
1of12 wrote:sysvinit is the init system used in Slackware. It uses sysvinit + BSD style rc scripts.
I'm talking about init system, not init file. OpenRC is an init-system that uses init file too. OpenRC isn't sysvinit even if it uses init file provided by sysvinit.
1of12 wrote:They're sysvinit scripts because they're used with sysvinit. The fact that they're 'BSD style' does not make them BSD init scripts or the init system they're running on some kind of *BSD init.
We seem to have major terminology differences. And BSD-init isn't something I came up with, it's how it is referred to all over the place
http://wiki.gentoo.org/wiki/Comparison_of_init_systems
http://www.linuxfromscratch.org/hints/d ... d-init.txt
I will say "BSD style init", if it suits you better. It still means the same thing.