From owner-freebsd-hackers  Mon Jun 26 12:36:13 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id MAA00177
          for hackers-outgoing; Mon, 26 Jun 1995 12:36:13 -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 MAA00168
          for <freebsd-hackers@FreeBSD.ORG>; Mon, 26 Jun 1995 12:36:09 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id FAA11536 for freebsd-hackers@FreeBSD.ORG; Tue, 27 Jun 1995 05:34:33 +1000
Date: Tue, 27 Jun 1995 05:34:33 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199506261934.FAA11536@godzilla.zeta.org.au>
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: weird filesystem state (cannot remove files)
Sender: hackers-owner@FreeBSD.ORG
Precedence: bulk

>there's absolutely no need to save a kernel that just proved to be
>broken (and thereby destroying the valuable /kernel.old!), so i'm
>normally clobbering such kernels, even if it's the currently running
>one.

>Anyway i realize, the ``make install'' approach including the immutable
>flag is a Good Thing (tm) for the casual user.

I think destroying /kernel.old is wrong for the casual user too.  At
least 3 kernels are required for the `make install' approach to be
reasonable: /kernel, /kernel.old and /kernel.stable.

Bruce