[SOLVED] Since going multilib, boot time really slow
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.
If you don't find any other explanation, check to see if you are getting disk I/O errors. Sometimes adding files to a disk puts the files in a previously unused (bad) area of the disk. Later attempts to read the files can then get I/O errors that cause retries, slowing down reading of the files.
For now I have created a separate script in /etc/rc.d and called it rc.update-icon-cache. I call it from rc.M. At least now I can switch it off when I don't need it, which is nearly always.
Won't mark it closed just yet on the off chance that maybe someone with the skills can suggest a way of automating the on/off function to detect when new icons are added and run it or not as the need requires.
But if I do that, what happens when I do install some new ones. Is there any way of undoing what you suggest?
All that command line does is get rid of icon cache files that (IMO) don't need to be there. If you didn't make those manually, then they were probably created by a package that came from outside of the official Slackware package tree. OK, I might have done it... there were a couple of times when a package was pulled into -current that did this, though they were quickly fixed. The need for icon caches is pretty debatable on a machine that's got a decent amount of RAM, as the icon files will end up cached through the normal filesystem caching anyway.
If you remove the icon caches, then if you install new icons they'll be used. Otherwise, the caches are preferred and the new icons won't be used until the caches are rebuilt to include them.
and what if anything is the alternative?
The alternative to removing the icon caches is keeping them up to date whenever new icons are installed. If you do that you won't need to call the update script in rc.M which is there to try to fix problems for people who ended up with cache files somehow and probably didn't even know it.