Linked by Thom Holwerda on Sat 15th May 2010 19:23 UTC
Thread beginning with comment 425113
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2010-03-08
Then, think about UNIX's traditional startup process : it runs a script shell, which then sequentially runs several tasks.
Yes. I can't imagine why you want to multi-task during startup, though. If you have a hardware issue,can you image debugging it in a multi-tasking scenario??? *shudders* "
The reason for multitasking the startup process is simple, actually : during startup, there is a lot of IO-bound tasks. Waiting for IO is wasting precious time. Let's suppose that you want to connect to the internet at boot time. Wireless connection + DHCP request and acknowledgement takes, say, 5 seconds. During those 5 seconds, you could have loaded several modules from the HDD.