On Mon, 17 Feb 2025 at 18:24, ruggero rossi <[email protected]> wrote: > > On Tue, 18 Feb 2025 00:22:16 +1000 (AEST) > David Leonard <[email protected]> wrote: > > Hello David, > > This is the first time I've thought about NTP eras, so I'm not sure my > reasoning is correct, but here are my considerations:
[...] > About the starting point, the only comment I can make, is that we must be > sure that a system starting with unix time_t = 0 - no battery in the real > time clock - starts in the right era. Having a battery on-board is a luxury that not all the embedded systems have. Which usually, they are working on a 32 bit architecture, in the best case. While for some other systems the RTC battery can go out of order in a sudden way and despite this they should crash but resuming the smoothest way (e.g. collecting the right time/date from the network). Said that, I understand that a small-footprint oriented project like busybox should not implement a reliable solution for every exotic case of the fortune, on the other hand, the small-footprint oriented is mainly because of embedded systems, at least in origin. Which is still true today because the other market niche - like Android systems - has been fulfilled by toybox because of the different license terms. The toybox, which was and still be developed by the previous busybox maintainer/leader. So, busybox did not switch on a broader market and it should still be considered an embedded-like tool. Whatever the word "market" my upset someone, that's a matter of fact, whether toybox or busybox earning or not, by those markets. However, applying a s/market/field of application/g does not change a bit the whole meaning. Moreover, if a fix - whatever it would be - does not bloat the code excessively (and a if/else, is not going to do that) nor increases the size (or just a little bit), then everything considered above, it should be applied. Not necessarily as originally proposed but in one way or another. IMHO, naturally. Best regards, R- _______________________________________________ busybox mailing list [email protected] https://lists.busybox.net/mailman/listinfo/busybox
