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.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
Why does slackware 10.2 take so long to startup? I would like some tips one how to get it to have a much shorter boot time. It seems to kind of hang at the hotplug part. So any tips are appreciated. Thanks!
hotplug and ldconfig are the two services that take up the most time. I suggest before considering to disable hotplug, find out what modules are used for your hardware by issuing an lsmod and then make sure they are listed and uncommented in rc.modules, then issue the chmod -x /etc/rc.d/rc.hotplug command. You will have to reconfigure alsa once hotplug is disabled, just rerun alsaconf. As for ldconfig, I can't remember what startup script it is under, rc.3 or rc.4 one of those, and simply comment it out, and you can enter the script to ldconfig to one of your shutdown scripts instead, like rc.6 , or just run ldconfig manually after installing new programs.
One more thing, since you will disable hotplug, be sure that you will not be planning to add any new devices.
Hotplug gets slower and slower as new 'agents'are added. Try installing the old hotplug package from Slack-10.0 -it's quite a lot faster than later versions.
Don't be fooled thinking that ldconfig takes a long time. It finishes and other things are happening, but there are no new prompts to replace the ldconfig line, so it LOOKS like ldconfig is still working, when, in fact, the scripts have moved along and done many more things...