From owner-freebsd-current Sun Jan 31 15:14:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08554 for freebsd-current-outgoing; Sun, 31 Jan 1999 15:14:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08547 for ; Sun, 31 Jan 1999 15:14:01 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id SAA06802; Sun, 31 Jan 1999 18:13:52 -0500 (EST) Date: Sun, 31 Jan 1999 18:13:52 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Kris Kennaway cc: "Daniel C. Sobral" , current@FreeBSD.ORG Subject: Re: vn and 4.0 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 On Mon, 1 Feb 1999, Kris Kennaway wrote: > On Mon, 1 Feb 1999, Daniel C. Sobral wrote: > > > Is vn safe right now on -current? > > It's broken for me without Matt's patch posted the other day (not yet checked > in). I can send you a copy if you missed it. > > > And does current's msdos fs > > support fat-32? > > Don't know, but I think so. FAT32 has been supported for quite a while now, along with FAT12/FAT16 and the VFAT extension (long file names). In fact, we've just about got a read only NTFS now too. > > Kris > > ----- > (ASP) Microsoft Corporation (MSFT) announced today that the release of its > productivity suite, Office 2000, will be delayed until the first quarter > of 1901. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message