Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!ulysses!allegra!princeton!udel!rochester!bbn!oberon!cit-vax!elroy!mahendo!jplgodo!wlbr!scgvaxd!trwrb!desint!geoff
From: geoff@desint.UUCP
Newsgroups: news.admin
Subject: Re: Map expiration dates
Message-ID: <1662@desint.UUCP>
Date: 17 Jan 88 07:07:16 GMT
References: <2323@cxsea.UUCP> <7815@rutgers.rutgers.edu> <12829@oliveb.olivetti.com> <296@fig.bbn.com>
Reply-To: geoff@desint.UUCP (Geoff Kuenning)
Organization: Interrupt Technology Corp., Manhattan Beach, CA
Lines: 26
Posted: Sun Jan 17 02:07:16 1988

In article <296@fig.bbn.com> rsalz@bbn.com (Rich Salz) writes:

> In news.admin jerry@oliveb.UUCP (Jerry Aguirre) suggests posting the maps
> as one file per site, using the d. files as an experiment.  Systems
> short on inodes could pack the files into an archive (map ranlib, anyone?)
> or a tarfile.
> 
> This is a great idea, and I hope the map folks give it some thought.

Unfortunately, those systems (like me) that are short on i-nodes are also
those which are short on disk space.  Packing files into a 'tar' archive
requires temp space equal to twice the size of the files and doesn't allow
individual file replacement.  'ar' is stupider about temp space, and requires
as much as three times the total map size in the temp space.  Grepping
out the '#' lines is possible, but unfortunately throws away useful
information like geographical locations and how to reach the administrator
at a particular site.

At the moment, my map files (compressed, but with '#' lines still in) take
1990 blocks;  the file system the live on has 2124 free at the moment, but
goes down as low as 1400 late each week.

If the net decides to go this way, I'm sure I'll manage to figure out a
way to live with it.  But I won't be real happy.
-- 
	Geoff Kuenning   geoff@ITcorp.com   {uunet,trwrb}!desint!geoff