On Mon, Mar 23, 2015 at 4:56 PM, Kay Sievers <[email protected]> wrote:
> On Mon, Mar 23, 2015 at 3:49 PM, Stef Walter <[email protected]> wrote:

>> It seems that timedatectl itself needs information about remote local
>> time, since when connecting remotely over DBus it gets the local time
>> wrong. [1]
>
> Yeah, it's currently a mix of local vs. remote data. If timedatctl
> should work correctly on a remote host, it needs to fixed.

Btw, we had plans to support the kernel' side of localtime (really
broken by design) for FAT and SCSI and network stuff, but it turned
out to be an unsupportable mess, and we just declared FAT timestamps
as UTC (like Android does).

Unless someone has an idea how to fix and use all that reliably, I'll
just go and remove the DST timezone data parser src/shared/time-dst.c
and its user in timedatctl.

Thanks,
Kay
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to