From owner-freebsd-current Mon Jul 20 16:33:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15673 for freebsd-current-outgoing; Mon, 20 Jul 1998 16:33:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.baldcom.net (green@zone.BALDCOM.NET [205.232.46.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15662 for ; Mon, 20 Jul 1998 16:33:07 -0700 (PDT) (envelope-from green@zone.baldcom.net) Received: from localhost (green@localhost) by zone.baldcom.net (8.8.8/8.8.7) with SMTP id TAA20835; Mon, 20 Jul 1998 19:33:00 -0400 (EDT) Date: Mon, 20 Jul 1998 19:32:59 -0400 (EDT) From: Brian Feldman To: Alfred Perlstein cc: Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-Reply-To: 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 Seems to work "somewhat" okay for me, problems being, that doscmd and newfs_msdos can't seem to agree on the format of my msdos.drv (/dev/vn0); so when I newfs_msdos it I can then mount and use it, but I have to reformat it in doscmd so I can use it in DOS. I get strange errors when I try to do either with the wrong formatted drive. Brian Feldman On Mon, 20 Jul 1998, Alfred Perlstein wrote: > no, it's been broken for some time now. > > -Alfred > > On Mon, 20 Jul 1998, Joel Ray Holveck wrote: > > > Is vnode support operational? It's hung my system when I've tried to > > use it lately. > > > > Thanks, > > joelh > > > > -- > > Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan > > Fourth law of programming: > > Anything that can go wrong wi > > sendmail: segmentation violation - core dumped > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message