[ntp:hackers] /dev/ntpsymlink1 -> COM1: for ntpd on Windows

Dave Hart davehart at gmail.com
Sun May 31 16:50:26 UTC 2009


On Sun, May 31, 2009 at 4:26 PM, Terje Mathisen <terje at tmsw.no> wrote:
> Dave's approach is obviously "The Right Thing" to do, with one tiny caveat:
>
> ntpd device numbers start at 0, while Windows start at 1, and in the
> current code this is correctly mapped.
>
> I.e. 127.127.20.4 maps an NMEA gps receiver connected to COM5, while my
> 18LVC on COM1 would use 127.127.20.0

I do not see the benefit of changing the unit number to COMx: mapping
on Windows at this point.  127.127.x.0 has always mapped to the (never
present) COM0:, changing that now would break existing configurations
(and documentation) for no apparent gain, as we can now use unit
numbers larger than 3.

Cheers,
Dave Hart


More information about the hackers mailing list