How about:

You edit /etc/rc.d/rc.local, append line
/usr/bin/echo "ldconfig" | /usr/bin/at now +5minutes

:)

That will run ldconfig 5 minutes after the boot-scripts
have finished, X and your "most important apps"
should be up & running, and the process in the
background shouldn't bother you too much ;)


Cheers,
Tink

oh, great idea. Why didn't i think of that? (Because i am a newbie )

Thanks for the tip.

Why reboot at all unless you've just upgraded the kernel?

Power-saving, environmental conscience, care for
future generations?

If it's not actually a server of sorts I can't see a
good reason not to shut it down, unless of course
one feels the urge to part-take in a contest about
longest uptime, fastest CPU, most RAM, fastest GPU,
... to compensate for lack of real of ... (insert appropriate
choice here) ;)

You can extend that to the world of motorcars if you
wish (faster, better acceleration, most expensive
wheels, ... )!


Cheers,
Tink

I'm a little confused, the "updating /sbin/ldconfig" thing only takes about 15 seconds to do it's thing on my PC (which is over 2 years old).

nope the running ldconfig at background command didn't work. First of all slackware does not have a command now for me

The command is at, now is a parameter.

In Slackware 10 it's in
/<cdrom1>/slackware/ap/at-3.1.8-i486-2.tgz


Cheers,
Tink

Nope not I, but the intent in this thread appeared to be to find ways of reducing the boot time, hince not rebooting the machine at all is the most effective way to accomplish said end result. As I'm sure most everyone is aware, unlike Windows, Linux is very stable in this regard and seldom needs rebooting. That was always my biggest gripe with Windows, everytime I turned around it said, "Reboot Me Please", or was locking up. Anyway, my workstation stays up 24/7 365 out of shear convience, kinda like flourscent light in my bathroom.

/me looks at DaHammer's signature and says:"Yeah, right" :D

Well, if you put it like that you're one of the worst
energy wasters I've come across in my entire life ;)

My notebook (no where near as grunty as your thing)
takes under a minute from power button to first activities
in my WM ...


Cheers,
Tink

Tinkster, that's the perfect solution. I just tried it out. Sure enough, a check of my running processes showed that at five minutes after booting ldconfig appeared, doing its thing quietly in the background. Thanks for the tip.

BTW, I posted your solution in alt.os.linux.slackware, where they were also discussing the pros and cons of having ldconfig run as part of the boot sequence.

Heh :)

Now the REAL pros are going to stomp me
into the mud ;}


Cheers,
Tink

Hmm. Maybe I should have asked you first. Oh, well. The post is buried way down in a long thread that is already pretty much dead, I think. But I do hope you don't get any hate mail on my account.

Those guys at alt.os.linux.slackware might be real pros, but some of them seem to have a grudge against humanity. It's not for the faint of heart. That said, I've gotten some good advice out of some of the more helpful ones. There seem to be some long-running feuds, though, and a lot of the boyz have entirely forgotten their manners. There's one poor guy who can't post anything without trashing everybody else. I think he needs a shrink, fast.

Plus there are an awful lot of posts pertaining to Britney Spears. I didn't know she liked computers so much. Great to have her on the Slackware Linux team, though.