SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
There is a discussion going around if systemd is inevitable on slackware.
Slackware is better off without systemd.
If really the init system on slackware has to be changed (which I feel is unwanted, unwarranted) I request Patrick Volkerding and other core developers to consider S6 or Runit
Let slackware be unique. With slackware, is Gentoo / Funtoo using OpenRC. Let others go wherever they want
A former Archlinux user. Easy to get 'banned' on their forums. Just talk something negative about systemd, and you are out.
If it became necessary, I'd like to see how OpenRC could be implemented on Slackware. However, RUnit and S6 seem viable as well due to their concept of being UNIX oriented and friendly. Slackware aims to be UNIX-like, not Red Hat, Ubuntu, or Other-Linux-like.
Systemd just isn't too stable or well conceived to be a viable alternative to the BSD-derived SysVInit we use. It's Alpha-ware. Patrick already has a history of ONLY using stable and trusted software within Slackware so that's more than likely to remain the state of the system.
There are at least about a dozen or so Init systems that are far more developed and admin friendly than systemd is as it's still Alpha-Class software and realistically nowhere near stable or reliable enough for a production level OS for server or desktop systems..
BootScripts, DEMONS, eINIT, Initng, launchd, mudur, Solaris's System Management Facility, System Starter, Upstart, OpenRC, Classic BSD-Init, even BusyBox's Init. And there are probably more.
Small correction regarding Dragora GNU/Linux. Selk (Matias. A. Fonzo), Maintainer of Dragora, has confirmed (over the mailing list and on IRC at freenode) that in the Dragora GNU/Linux 3.0, SysvinitV + Perp would be the init system, perp provides the supervision