From owner-freebsd-current  Mon Mar 17 00:07:06 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA28575
          for current-outgoing; Mon, 17 Mar 1997 00:07:06 -0800 (PST)
Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA28569
          for <current@freebsd.org>; Mon, 17 Mar 1997 00:06:59 -0800 (PST)
Received: (from bsdcur@localhost)
          by shadows.aeon.net (8.8.5/8.8.3) id KAA00928
          for current@freebsd.org; Mon, 17 Mar 1997 10:05:15 +0200 (EET)
From: mika ruohotie <bsdcur@shadows.aeon.net>
Message-Id: <199703170805.KAA00928@shadows.aeon.net>
Subject: panics?
To: current@freebsd.org
Date: Mon, 17 Mar 1997 10:05:15 +0200 (EET)
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
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

is it only me or does the -current (well, now few days old) cause some
panics? anyone?

yes, i know it's expected and stuff, and i did expect it to be flaky.

i havent yet been able to track down what exactly causes it to fall down,
but were wondering if someone would have ideas...

and as soon as i catch the reason i'll let you know... (i think i turn on the
panic dumps)

while i post, to me it sounds a nice idea to twiddle the naming like it
was suggested...

2.1.x	stable
2.2.x	current
3.0.x	future	(experimental?)

it would make it somewhat more clear.


mickey