On Thu, 07 Nov 2019 15:38:04 +, Stuart Henderson wrote:
> Now I've gone through mkr, here's the diff.
>
> base66 goes from 8100->6870 inodes as it avoids the duplicated copy
> of the standard files, as well as the leap-seconds files.
Fine with me.
- todd
Fine with me.
Stuart Henderson wrote:
> On 2019/10/26 15:32, Mark Kettenis wrote:
> >
> > The fundamental problem with the "right" files is that the time_t
> > values end up being different from their POSIX values for the same UTC
> > time. So whenever these are stored and compared between sys
On 2019/10/26 15:32, Mark Kettenis wrote:
>
> The fundamental problem with the "right" files is that the time_t
> values end up being different from their POSIX values for the same UTC
> time. So whenever these are stored and compared between systems (or
> environments that set the TZ environment
On 2019-10-26 09:32, Mark Kettenis wrote:
>> From: "Todd C. Miller"
>> Date: Sat, 26 Oct 2019 06:55:02 -0600
>>
>> On Sat, 26 Oct 2019 12:15:33 +0100, Stuart Henderson wrote:
>>
>> > The way these files are supposed to work is that you set the system
>> > clock to the time with leap-seconds incl
> From: "Todd C. Miller"
> Date: Sat, 26 Oct 2019 06:55:02 -0600
>
> On Sat, 26 Oct 2019 12:15:33 +0100, Stuart Henderson wrote:
>
> > The way these files are supposed to work is that you set the system
> > clock to the time with leap-seconds included (UTC+leap, or TAI-10) and
> > copy the entir
On Sat, 26 Oct 2019 12:15:33 +0100, Stuart Henderson wrote:
> The way these files are supposed to work is that you set the system
> clock to the time with leap-seconds included (UTC+leap, or TAI-10) and
> copy the entire "right" set of files to the main zoneinfo directory
> (upstream provides them
Moving to tech:
On 2019/10/25 23:45, Christian Weisgerber wrote:
> Nick Holland:
>
> > I live in EST5EDT. (actually, I normally use
> >/usr/share/zoneinfo/right/US/Michigan )
> ^
> I suspect this to be the trigger for your problem. You have put
> yourself into
