Subject: Re: nuking the vgrindefs Berkeley DB file from orbit.
To: Erik E. Fair <email@example.com>
From: Simon Burge <firstname.lastname@example.org>
Date: 06/27/1999 17:25:29
"Erik E. Fair" wrote:
> If the current Berkeley DB is anything like the original dbm(3), then that
> file has holes, and is not actually taking up 500K on your disk.
Just built a fresh one, and then copied the db file so it wouldn't have
simonpc:src/usr.bin/vgrind 6> ls -ls vgrindefs.src*
7 -rw-rw-r-- 1 simonb admin 6699 Jan 20 1998 vgrindefs.src
296 -rw-rw-r-- 1 simonb admin 532480 Jun 27 17:20 vgrindefs.src.db
528 -rw-rw-r-- 1 simonb admin 532480 Jun 27 17:20 vgrindefs.src.db.cp
So yes it does have holes, but there's still a proverbial boat-load that
isn't holes. Also, tar/pax doesn't know about holes (except for some
esoteric gtar options), so when extracted from release media it's gonna
take up that extra space...
(A still not convinced) Simon.