Tiny Core Base > TCB Bugs

enhance parsing dhcp supplied ntp-servers option

<< < (2/2)

Greg Erskine:
Hi Rich,

We have been working on various issues with setting the time properly for years on piCorePlayer.

There has been a lot of discussions over on the Slimdevices forum, very little here.

I think the multiple server issue raised here may have already been implemented in piCorePlayer by Paul. I know we discussed it over a year ago.

regards
Greg

Paul_123:
It sort of applies, but since piCore/Tinycore doesn't include a udhcpc script to process ntp from dhcp, more needs to be done.

https://github.com/tinycorelinux/Core-scripts/blob/master/usr/share/udhcpc/default.script

piCorePlayer has a completely different implementation for dhcp/ntp.

miesi:
Ok, I hope I get this rght now:
For some reason the tcl git contains getTime.sh ... but it is not used for piCore/Tinycore.

First I'll raise a pr to implement better handling if getTime.sh is actually used.

Then I'll see what my time budget allows.

Rich:
Hi miesi
Both piCore and Tinycore have getTime.sh present when
they boot up, which is why I felt your post was relevant.


--- Quote from: miesi on May 05, 2024, 07:03:44 AM --- ... but it is not used for piCore/Tinycore. ...
--- End quote ---
I think it was originally created by bmarkus to set the current
time on pi zero.

As near as I can tell, getTime.sh is an option for individuals who
want a convenient way to set their systems clock.

Paul_123:
It is a relevant, just not a complete fix.  The change posted won’t alone do anything, since getTime will never get anything from dhcp without changing that too.

Tinycore/piCore has always used a bootcode to specify the ntpserver.  So if we want to change how this works, it needs to be a complete solution.  I have seen routers advertise incorrect ntp servers via dhcp.  (Amazon eero routers for one). So the bootcode needs to be first priority.

Navigation

[0] Message Index

[*] Previous page