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

Just to be sure: when you changed to the compact mode in lilo.conf. Did you remember to update lilo using something like: "lilo -v"?

@moesasji , No , i did'nt see it mentioned anywhere , is that the full command to execute? i mean just "lilo -v" ?

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 :-)

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.

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.

It worked !!!!!! after running lilo command.... it was so fast that it did'nt even show the pacman thing.....!!! thank you all.