[tz] Looking for a way to cut down binary zoneinfo size. Does anyone have the way to?

Arthur David Olson arthurdavidolson at gmail.com
Thu May 18 18:24:52 UTC 2017


One quick-and-dirty possibility: in zic.c, set "early_time" to one billion
(and downgrade the error about leap seconds before the big bang to a
warning).

(While quick and dirty, this is considerably more refined than setting
timecnt to zero.)

    @dashdashado

On Thu, May 18, 2017 at 1:59 PM, Viktor Sergiienko <singalen at gmail.com>
wrote:

> On Thu, May 18, 2017 at 10:39 AM,  <Paul.Koning at dell.com> wrote:
> >
> >> Limited savings is due to disk sector size; as an example, the
> "America/New_York" produced by an unmodified zic weighs in at 3545 bytes;
> on a 4096-byte-sector system, the one sector it takes can't be reduced.
> >>
> >
> > That's a point.  Note though that removing old information will also
> make for a bunch of duplicates, which reduces the total storage needed.
> Also, if you can use a storage system that packs the data, the sector issue
> may not be there.  I could imagine, for example, storing the zone data in a
> zip file and extracting the desired file when the user says "I want to use
> zone America/Thule".  In our own case, I used a dense file system similar
> to Linux's "romfs".
> >
>
> Yep, or we can mount an archive as is, with archivemount or something.
> The file slack can be dealt with, as long as the data is slimmed.
>
> Thanks!
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/tz/attachments/20170518/7eec0cf2/attachment.html>


More information about the tz mailing list