I'm considering having d-i run ntpdate as part of the install process. I can see two ways to do this; d-i could just install ntpdate onto the target system, which would make it sync the clock at install time (and again at bootup I think). Or we could have a small ntpdate binary in a udeb that d-i runs once during the install. I'm unsure which is the better appoach. Installing ntpdate kind of assumes it's right for everyone; I know some people, especially some people with NTP servers, don't like running ntpdate for various reasons. I think that it's possible for ntpdate to hang the boot process for at least one dns timeout if networking is broken. One open bug on ntpdate suggests it might fail if the NIC is a pcmcia card (although I think it would not hang in that case). On the other hand a udeb is more work, bloats d-i a bit more, and doesn't put a perminent clock setting mechanism in place. I welcome thoughts of suggestions on this matter.. -- see shy jo
Attachment:
signature.asc
Description: Digital signature