This is a discussion on /sbin/ldconfig within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Why does /sbin/ldconfig run every time I boot, and why does it take so long to notice that I ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| |||
| Rich Grise wrote: > Why does /sbin/ldconfig run every time I boot, and why does it take so > long to notice that I haven't installed any new libraries? A lot of people don't remember/know to run ldconfig manually. Some people don't reboot often. A few of us comment out a few lines around /etc/rc.M:90. Its a small price to pay to keep Slackware more accessible; Windows folks are used to rebooting whenever something doesn't work. |
| ||||
| Le Thu, 28 Sep 2006 19:43:57 -0500, D Herring a écrit*: > Rich Grise wrote: >> Why does /sbin/ldconfig run every time I boot, and why does it take so >> long to notice that I haven't installed any new libraries? > > A lot of people don't remember/know to run ldconfig manually. Some > people don't reboot often. A few of us comment out a few lines around > /etc/rc.M:90. Its a small price to pay to keep Slackware more > accessible; Windows folks are used to rebooting whenever something > doesn't work. that was an exageration off your evil dreams, the real world "phrasé" is : " Windows victims are trained to rebooting whenever anything seems to work and doesn't boot or freeze before you could do something useful " Oh, well, that's right, there's no real difference between the two sentences ;-) |