From owner-freebsd-current  Mon Mar 11 12:47:14 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA14164
          for current-outgoing; Mon, 11 Mar 1996 12:47:14 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA14147
          for <freebsd-current@FreeBSD.ORG>; Mon, 11 Mar 1996 12:47:02 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA03862; Mon, 11 Mar 1996 13:42:31 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603112042.NAA03862@phaeton.artisoft.com>
Subject: Re: New kernel
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Mon, 11 Mar 1996 13:42:31 -0700 (MST)
Cc: coredump@nervosa.com, uhclem@nemesis.lonestar.org,
        freebsd-current@FreeBSD.ORG
In-Reply-To: <22539.826511303@time.cdrom.com> from "Jordan K. Hubbard" at Mar 10, 96 06:28:23 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > > How about PASSIVE instead of AGRESSIVE.
> > 
> > How about ASSERTIVE?
> > 
> > kernel: Would it be okay if I panic'ed now? (y/n)
> 
> How about PASSIVE_AGGRESSIVE?  The kernel doesn't actually panic, but
> corrupts your files occasionally when you're away on vacation. :-)

It would never work.  The machine would go through Lithium clock
batteries like there was no tomorrow...


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.