the documentation should explain more or less verbosely, why two scripts doing virtually the same in short distance are needed.
Yes please! I'm currently trying to improve the boot time on my ASUS Eee; you may have heard of Arjan van de Ven's demo where he gets this machine to boot in only 5 seconds - Debian is currently about 5 times worse than that. And it spends two whole seconds (gasp!) setting the clock. If it would set it only once, that would save a whole valuable second! So I'm tempted to hack out one or other of these scripts - but I fear doing so, since I don't know why we have two in the first place. Could we please have a few words of explanation, dear experts?
I'm also curious to know why reading the clock takes a second anyway. Note that we have to use --directisa on this hardware to avoid a random lock-up. It looks as if the CPU is busy for the second that it's running - in a busy-loop maybe? Is there anything that can be done to accelerate this?
Cheers, Phil. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
