Hi Ross, What I am more after is trying to convince upstream systemd that this might be a potential problem within the embedded world.
Considering that date might get set by a malicious ntp server. In that case user space stops booting for us and I guess my understanding is same thing will happen for openembedded stack too. Isn’t this a concern to anyone? Umut > On Sep 8, 2015, at 2:04 PM, Burton, Ross <[email protected]> wrote: > > > On 8 September 2015 at 12:44, Umut Tezduyar Lindskog <[email protected]> > wrote: > Upstream systemd’s answer is pretty much using 64 bits time_t structure but > this is relatively expensive on 32 bits ISA. > > What problem are you trying to solve here - the general problem of "I want my > hardware to work after 2038" or "my RTC is stupid"? For the former you'll > potentially be writing a new ABI to introduce a 64-bit time_t (then updating > the kernel, libc, toolchain...), for the latter can't you have some kernel > code that clamps the random times on initialisation to be <2038? > > Ross -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
