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.
To trace the init sripts, start at rc.S. Near the bootom it calls rc.modules, returns, finishes and then rc.M runs which calls rc.local at the end. If you use runlevel 4 then rc.M is not run.
By the way: any special reason Slack uses runlevel 4 instead of 5 like most other distros do? Is it just something Slack has had since the beginning of time (1992/1993) or is there a reason?
Read the last few lines of /etc/inittab
And be aware that many things that are usually done on startup don't happen in rc.4. rc.M is what is usually run when 'Going multi-user', but runlevel 4 will skip it.
My laptop does. It is my main dev machine and even if I didnt need to shut down to move it places I would need to shutdown when I need to test things in Windows.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.