From owner-freebsd-emulation Tue Jun 15 21:10:14 1999 Delivered-To: freebsd-emulation@freebsd.org Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (Postfix) with ESMTP id 94381154BB; Tue, 15 Jun 1999 21:09:57 -0700 (PDT) (envelope-from gnb@itga.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id OAA00804; Wed, 16 Jun 1999 14:09:53 +1000 (EST) Received: from lightning.itga.com.au(192.168.71.20) via SMTP by fw.bby.com.au, id smtpd000802; Wed Jun 16 04:09:49 1999 Received: from lightning (lightning [192.168.71.20]) by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id OAA12424; Wed, 16 Jun 1999 14:09:47 +1000 (EST) Message-Id: <199906160409.OAA12424@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Randall Hopper Cc: Ted Spradley , stable@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: vnconfig & FAT filesystem -- supported? In-reply-to: Your message of Tue, 15 Jun 1999 23:35:06 -0400. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Jun 1999 14:09:47 +1000 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Aside: the "vn" driver is not the same thing as the "vnode system" - the vn driver allows you to use a file (represented by a vnode in the kernel) as a block device. Vnodes are how the kernel represents files in a somewhat file-system-independent manner.] > Question is, can the vnode system handle MSDOS/FAT? Well, it certainly orta, as vn really knows only about blocks, not filesystems. And the "make release" process requires the use of the vn driver to build boot floppies. And it works for me: hellcat## vnconfig /dev/vn0a floppyimg hellcat## mount -t msdos /dev/vn0a /mnt hellcat## ls /mnt DATA.1* SETUP.EXE* _INST16.EX_* _SETUP.LIB* SETUP.BMP* SETUP.INS* _ISDEL.EXE* disk1.id* SETUP.DBG* SETUP.PKG* _SETUP.DLL* hellcat## umount /mnt hellcat## vnconfig -d /dev/vn0a hellcat## Check: do you have the vn device configured in your kernel? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message