Hi Petter,
Petter Reinholdtsen wrote:
But it is less risky to remove the calls to hwclock*.sh. If I
understood my recent discoveries correctly, the i386 kernel normally
sets its internal clock without help, so there is no need to run
hwclockfirst.sh and hwclock.sh. So instead of putting it in the
background, try to just add 'exit 0' after 'start)' in both scripts.
On my system, this dropped the boot from 44 to 20 seconds.
I also got a reduction but just of 4 seconds: from 53 to 49. I just
removed the scripts from rcS.d. Two seconds more than putting it on the
background.
I also tried to put the networking script in the background, but this
made ntpdate fail because the DNS server were unavailable.
This still makes no difference in my machine :(. Still 53 seconds.
So I'll follow your lead and change "put hwclock in the background" for
its removal for the deliverable 4.
cheers,
Carlos
--
Carlos Villegas
----------------------------------------
Hamilton Institute
NUIM, Maynooth, Co. Kildare
Ireland
Tel: +353 1 708 6458
Fax: +353 1 708 6269
www.hamilton.ie/carlos
_______________________________________________
initscripts-ng-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/initscripts-ng-devel
