Linked by Eugenia Loli on Mon 9th May 2005 18:38 UTC, submitted by Robert Burns
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



a few &s in /etc/rc.d/rc.M can do wonders (carefull with hotplug though, you should probably just let that one sit) had to do this for my laptop (slow, used a transmeta chip, which is, i suspect, the main reason)
background for those confused: rc.M is a startup script, which runs each startup command one at a time, showing you its output, so if anything goes wrong, youll see it. no one cares any more (at least till something goes wrong) so background those starting tasks and it will move on to the next one, effectively doing them in parallel.
anyway, the above applys to slackware, apperantly uniquely to slackware, as all the other distros have complex start up procedures that take even longer.