From owner-cvs-all  Wed Aug 12 13:58:12 1998
Return-Path: <owner-cvs-all>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA09903
          for cvs-all-outgoing; Wed, 12 Aug 1998 13:58:12 -0700 (PDT)
          (envelope-from owner-cvs-all)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09882;
          Wed, 12 Aug 1998 13:58:03 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id GAA19985;
	Thu, 13 Aug 1998 06:57:36 +1000
Date: Thu, 13 Aug 1998 06:57:36 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199808122057.GAA19985@godzilla.zeta.org.au>
To: bde@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG,
        eivind@yes.no
Subject: Re: cvs commit: src/sys/kern vfs_subr.c src/sys/nfs nfs_vfsops.c
Sender: owner-cvs-all@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>>   Don't configure compatibility code for pre-Lite2 mount() calls by
>>   default.  This code should go away soon.
>
>IMO, this code should be enabled until post 3.0-RELEASE, to allow a
>reasonable transition from the 2.2 branch to the 3.0 branch.
>
>Without this, you _have_ to have periods where your system won't boot if you
>get an accidental reboot.

It may not boot automatically, but that is always a possibility if the
system crashes during installation of a new (or even slightly changed)
version over the top of the running version.  Don't install over the
top of a running version unless you could recover.

Bruce