SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Which one is the execute bit? Here's what I'm getting:
-rw-r--r-- 1 root root 3678 Jun 15 2016 /etc/rc.d/rc.cups[/CODE]
There is no execute bit (x) in the above output, so the file is not executable and for this reason cups is not starting on boot.
To change that you should run:
Code:
chmod +x /etc/rc.d/rc.cups
Since as you say, you're a noob, better take a look here about file permissions and how to manage them
Slackware is one of the few distros that do not use systemd to start up. Consequently it does not have systemctl, which is part of systemd. It is also angled at people who are at home with the command line and understand the basics of how a Linux system is put together. That doesn't mean that a novice can't use it, but you must expect a steep learning curve. You might feel more at ease with a different distro.
But it has a confusingly named sysctl that is a part of procps-ng.
Sysctl is very old. It already existed when I started using Linux around the turn of the century. If there is any confusion now, it is entirely the fault of Poettering and the systemd team.
What sysctl does is to allow system administrators to actually write into, and so modify, the running kernel, using the /proc interface (which procps deals with). systemctl is the user/administrator interface of systemd.
Slackware is one of the few distros that do not use systemd to start up.
Praise Bob! One of many reasons why I love Slackware. As suggested previously I think it is a good idea to read the ample, available documentation on how to configure Slackware.
But it has a confusingly named sysctl that is a part of procps-ng.
average_user --
IMO, the distros that run systemd have a confusingly named program called systemctl which is too similar to an existing, very important Admin Tool on Linux / BSD.
Based on your recent Qs here on LQ, you probably want to familiarize yourself with the basics of the best Linux Distro out there ( but I am a little biased )
HTH
-- kjh
Last edited by kjhambrick; 03-14-2019 at 12:00 PM.
Reason: P.S.
*cough*
OP did not state systemctl but chkconfig; which is the RHEL6 way; I think he's more familiar with RHEL family, which is fine.
In very short:
When Slackware boots, it starts a procss called 'init'
Init reads a file: /etc/inittab
In that file is listed which processes should be run at which runlevels. (type runlevel at your prompt and notice it is (probably) 4 when you're reading this )
One of the scripts launched by init is /etc/rc.d/rc.S as initialisation
That script runs a few other scripts in /etc/rc.d (as long as they have their x-bit (executable) set)
Also there's a file rc.local: which you're free to fill with services you want to be started; Similary there's a script rc.local_shutdown for services you want to be shutdown clean on system shutdown.
Then in particular cups: it is launched by rc.cups, which is called by rc.M
rc.M has this comment at the top:
Code:
# rc.M This file is executed by init(8) when the system is being
# initialized for one of the "multi user" run levels (i.e.
# levels 1 through 6). It usually does mounting of file
# systems et al.
(triggered: runlevel 6 is reboot, right?)
Anyway, if you look close, you'll see that rc.cups is ran when /etc/rc.d/rc.cups has x-bit set;
I would recommend reading the Slackware book; not only to learn Slackware, but to learn Linux; You'll also learn what other systems do, how they do that and maybe find a rationale. (Although I have yet to discover the rationale behind systemd) Read: http://www.slackbook.org/
IMO, the distros that run systemd have a confusingly named program called systemctl which is too similar to an existing, very important Admin Tool on Linux / BSD.
Come on, I didn't say it's Slackware's fault. I just wanted to let OP know that there is also sysctl that is not, say, a variant or an abbreviation of systemctl.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.