[SOLVED] pacman trap in booting takes too much time , compact command on lilo.conf not effective
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.
pacman trap in booting takes too much time , compact command on lilo.conf not effective
My machine runs on AMD Quad Core 64 bit processor with 4 GB ram , slackware 14.2 linux loading pacman trap (..........) takes more than 20 seconds , i have tried the compact option in lilo.conf and it was not effective , is there any other method to avoid this ? I also tried hdparm -d1 /dev/sda5 (sda5 is my root partition) but its was showing error such as incorrect ioctl etc. It could be helpful if anyone could suggest me away , post the linux loading i have compacted every services so it loads faster.
I saw another thread here similar to mine , but their problem was solved by adding compact in lilo.conf , not mine
Yes, just typing in "lilo -v" as root is all that is needed. A bit more background explanation can be found in the slackbook under lilo, see: http://docs.slackware.com/slackbook:booting
Thank you @moesasji , currently i am not in my machine , once i get back to my machine i will test and will let you know , if it works then i will mark this thread as solved , but my only doubt is that in the lilo conf file on the compact line it is commented that it does not work on all machine , so let me try my luck :-)
Thank you @moesasji , currently i am not in my machine , once i get back to my machine i will test and will let you know , if it works then i will mark this thread as solved , but my only doubt is that in the lilo conf file on the compact line it is commented that it does not work on all machine , so let me try my luck :-)
When you edit your /etc/lilo.conf then you must run the command "lilo" to write the changed configuration to the boot block of your harddisk. The "lilo -v" command suggested above is just a more verbose version of the command "lilo".
In this regard, LILO is different from GRUB. If you modify the grub configuration file then GRUB will read that file when your computer boots because GRUB has built-in support for several fileystems (and therefore knows where to find the configuration file). LILO on the other hand, does not know about filesystems at all and only keeps a list of pointers into your storage device where it finds the configuration information, the kernel, the initrd etc. That is why you have to run "lilo" after modifying its configuration, so that lilo can store this information in the boot block.
but my only doubt is that in the lilo conf file on the compact line it is commented that it does not work on all machine
I think this is just Pat playing it safe. All computers should work with having compact commented out, but if some computers can't boot with compact enabled, then it is pretty serious.
But in my 10+ years using Slackware, I haven't had a computer that doesn't work with compact. I'd imagine it is only seriously old computers that would run into problems with it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.