From owner-freebsd-hackers  Sat May 20 13:27:40 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id NAA07811
          for hackers-outgoing; Sat, 20 May 1995 13:27:40 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA07805
          for <hackers@FreeBSD.org>; Sat, 20 May 1995 13:27:34 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA13062; Sun, 21 May 1995 06:23:56 +1000
Date: Sun, 21 May 1995 06:23:56 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199505202023.GAA13062@godzilla.zeta.org.au>
To: hackers@FreeBSD.org, pritc003@maroon.tc.umn.edu
Subject: Re: kernel database files
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

>Due to the way I name my kernels (kernel.MMDD, linked to /kernel),
>whenever I boot a new kernel for testing before linking it to
>/kernel, I wind up with a new kernel database file in /var/db.  
>Booting a lot of different kernels can cause your root file system to 
>start filling up, since these files are 300K+ in size.  How about if 

I think the kernel database should be regenerated at every boot like
it was in 1.1.  kvm_mkdb was very slow in 2.0 due to braindamaged
buffering in kvm_mkdb and/or db and braindamaged non-delayed writing
of full blocks in ufs, but Poul fixed kvm_mkdb on 1995/01/10 so it
now takes only about 1 second on a DX2/66.

Bruce