Hi Oliver, Oliver Tappe <zooey@xxxxxxxxxxxxxxx> wrote: [...] > Alternatively, we could use a similar approach to how the name of the > timezone file was transported to all processes before my changes: via > the > kernel, using two specific syscalls that set/get them. > In that case, clockconfig could put the timezone attributes into the > kernel > and tzset() would fetch them from there. Since clockconfig is already > able > to parse the 'Time settings' file, there would be not need for a > specific > libroot_timezone_info file. > > But to me it felt a bit weird to use the kernel as some kind of "data > storage". Or would that be just fine? There is already a real_time_data structure shared between userland and the kernel (see src/system/kernel/real_time_clock.cpp), and I would say this would fit perfectly fine for that usage as well. In that case, only a call to set the data would be needed (unless locking dictates both). Bye, Axel.