tried searching in slack docs...couldnt find anything with the keywords...

does slackware 14.2 use init or upstart?

also is there a new version of slackware coming out?

It's a top secret and very very confidential!

14.1 is the latest release version and uses sysvinit-2.88dsf

No sign of a new version yet. It comes out "when it's ready" which is usually around once a year +/- a couple of months or so. So, anything from 3 to 6 months from now, but that's a complete guess.

so does slackware use its own system for starting up daemons etc...
as when i look in /etc/rc.d/rc5.d there are no files...

if its so top secret...can only james bond know its story???

Take a look in /etc/rc.d/rc.S or rc.M and you'll see how it's all done.
The sysvinit runlevel directories are supported, but rarely used.

There is one much more powerful than James Bond, who uses only self-constructed high-tech devices and weapons powered with his genius Slackware. His name is Patrick Volkerding and he is doing everything alone, not like James Bond who is dependent by Quartermaster/s.

Only Patrick Volkerding knows the true story!

Is this the new "Are we there yet?" thread?

Probably. It wouldn't be a proper development cycle without one.
No doubt, Brian will be along shortly with his cat entrails.

Slackware uses BSD Init.

http://www.slackware.com/config/init.php

Cheers,

Niki

2 members found this post helpful.

"Brian will be along shortly with his cat entrails" Brian is sooo 16th century...

Slackware uses sysvinit with BSD style scripting. It uses two staging scripts, rc.S and rc.M, to load all necessary services as well as rc.local to load any extra daemons and services that may or may not use init scripts. rc.S loads the single user mode one-shot services and core system daemons, then it loads rc.M to start multi-user mode and load all other system services and post-boot scripts to configure the rest of the system. It's a very humanesque and easy to read design.

1 members found this post helpful.

Actually, its more of a hybrid. BSD traditionally used a single 'rc' script with a rc.conf/rc.conf.local to configure what needed starting. The rc.d/rc.something stuff in slackware is inspired by sysvinit's init.d/ scripts, but slackware decided not to use the per-runlevel rcn.d/ directories and the symlinks they contain, instead invoking the rc.something files directly from rc.S/M.

Interestingly, OpenBSD started using rc.d/rc.something type scripts for its daemons a couple of releases ago. I wonder if it was inspired by Slackware.

Dafuq? Slackware with Upstart?..... Nurse! nnn nnn NNNNNN < !!! S N A P !!! >

enorbet i am obviously a newb...i am reading a book and trying to see where this all fits together...i read that older systems use init which is being replaced by upstart...there really is no need for your sarcastic negativity...

upstart is a ubuntu-specific thing. Most systems nowadays are switching from sysvinit to systemd, which has spawned many threads here in the Slackware forum, since Slack is not following the trend so far. That may explain why some members get touchy when you ask questions about 'init' in Slackware. Most systems traditionally used the binary sysvinit coupled with the dir/link structure you seem to know about. Slackware has always used the sysvinit binary, but with a different script/dir/link structure which resembles the system used in BSD's. archlinux used to do the same -actually, their system resembled BSD's even more than Slackware. But, arch has since switched to systemd. The only notable distros which have not switched to systemd are Slackware, LFS, gentoo and crux.

2 members found this post helpful.