From owner-freebsd-current Mon Jul 20 23:33:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24880 for freebsd-current-outgoing; Mon, 20 Jul 1998 23:33:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA24873 for ; Mon, 20 Jul 1998 23:33:12 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.8) with SMTP id XAA21188; Mon, 20 Jul 1998 23:32:52 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Mon, 20 Jul 1998 23:32:51 -0700 (PDT) From: Chris Timmons To: Joel Ray Holveck cc: freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-Reply-To: <199807210525.AAA00857@detlev.UUCP> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One vn subsystem bogon that I haven't attempted to reproduce since last summer involved a 2.2-stable system with a BigDisk NFS mounted from a 3.0-current system. 'make release' on the 2.2-stable system into the BigDisk would totally hose the 2.2-stable system to complete catatonia at the instant when the vn stuff executed. Since then, dyson et al fixed a bunch of nfs problems in -current, but it was never clear to me if this was really an NFS problem, or actually related to the vn driver in -stable. Prior to these problems I used to build 2.1.x releases with a BigDisk NFS mounted on then 2.2-current. Anybody doing this recently? -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message