From owner-freebsd-current  Mon Jul 20 20:35:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA29819
          for freebsd-current-outgoing; Mon, 20 Jul 1998 20:35:07 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29804
          for <freebsd-current@FreeBSD.ORG>; Mon, 20 Jul 1998 20:35:04 -0700 (PDT)
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
	by time.cdrom.com (8.8.8/8.8.8) with ESMTP id UAA27160;
	Mon, 20 Jul 1998 20:33:40 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: Alfred Perlstein <bright@hotjobs.com>
cc: Joel Ray Holveck <joelh@gnu.org>, freebsd-current@FreeBSD.ORG
Subject: Re: vn subsystem 
In-reply-to: Your message of "Mon, 20 Jul 1998 21:29:08 CDT."
             <Pine.BSF.3.96.980720212829.337E-100000@bright.ny.otec.com> 
Date: Mon, 20 Jul 1998 20:33:39 -0700
Message-ID: <27156.900992019@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> hrm, not really there was some traffic on the lists a few weeks/months
> back about it being broken, but that's all i know.

Erm, wonderful.  Can we have some commentary from someone who's
actually proven this either way now?  Like I said, my own usage of the
vn driver has not shown any such instability.  If someone who's
_actually used it_ can now comment on its instability, we'll get a lot
further.

- Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message