Linked by Eugenia Loli-Queru on Tue 26th Jun 2007 09:03 UTC, submitted by lost
Today Patrick J. Volkerding
announced Slackware Linux 12.0 RC2. There are no big new features, this is almost a collection of bug fixes. A review of the RC1 can be found here (translation). A review of the Slackware-based Vector Linux 5.8 SOHO can also be found here.
Thread beginning with comment 250776
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2007-06-26
Member since:
2007-02-05
So, Slackware's init is a SysV-style init, without the SVR4-style per-runlevel symlinks.
Actually, as krasnolin pointed out, Slackware's init scripts are BSD style with SysV compatability included.
this is from the rc.sysvinit located in /etc/rc.d.
This file provides basic compatibility with SystemV style
# startup scripts. The SystemV style init system places
# start/stop scripts for each runlevel into directories such as
# /etc/rc.d/rc3.d/ (for runlevel 3) instead of starting them
# from /etc/rc.d/rc.M. This makes for a lot more init scripts,
# and a more complicated execution path to follow through if
# something goes wrong. For this reason, Slackware has always
# used the traditional BSD style init script layout.
#
# However, many binary packages exist that install SystemV
# init scripts. With rc.sysvinit in place, most well-written
# startup scripts will work. This is primarily intended to
# support commercial software, though, and probably shouldn't
# be considered bug free.
#
# Written by Patrick Volkerding <volkerdi@slackware.com>, 1999
# from an example by Miquel van Smoorenburg <miquels@cistron.nl>.