On Thu, Jan 05, 2012 at 07:59:00AM -0500, erik quanstrom wrote:
> > So the compiled result is not worth archiving.
>
> it has been more than once that in tracking down a problem, i've
> found that the "known working" executable worked but the source
> from that point in history didn't. and vice versa. having the executables
> and libraries archived was very valuable.
>
> otoh, just to use round numbers, if your build creates 100mb of new data
> and all of it hits venti before being replaced, then you've got 10000
> builds/TB. in practice, i think most people push to venti only once
> a day, so this is practically infinite. or, put another way, that's
> $100/10000 = 1¢/build. since the standard depricated comment is
> worth 2¢, it appears that these days 100mb is not worth commenting
> on. ?.
Perhaps, but it seems to me like digging ore, extracting the small
percentage of valuable; forging a ring; and throwing it in the ore, and
storing the whole...
Secondly, I still use optical definitive storage from time to time
(disks go in a vault)... with KerGIS and others, and kerTeX, this still
fit 3 times on a CDROM. So...
And finally, didn't the increase in size of the disks, with no decrease
of the reliability, increases the probability of disks failure?
Unfortunately, one finds not "small" (that were huge some years ago)
disks anymore...
PS: and for a Plan9 tester, he will begin by devoting a partition on a
disk to see. The iso is around 300Mb, so allocating 512 or 1024Mb will
seem enough. If he's hooked to Plan9---that happened to me ;)---sooner
or later a problem will occur.
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
