From owner-freebsd-hackers  Sun Apr  2 11:35:27 1995
Return-Path: hackers-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA06856 for hackers-outgoing; Sun, 2 Apr 1995 11:35:27 -0700
Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA06844 for <freebsd-hackers@FreeBSD.org>; Sun, 2 Apr 1995 11:35:22 -0700
Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id LAA07473; Sun, 2 Apr 1995 11:39:03 -0700
Date: Sun, 2 Apr 1995 11:39:03 -0700
Message-Id: <199504021839.LAA07473@trout.sri.MT.net>
To: Brian Tao <taob@gate.sinica.edu.tw>
Cc: FREEBSD-HACKERS-L <freebsd-hackers@FreeBSD.org>
Subject: Re: any interest? 
In-Reply-To: <Pine.BSI.3.91.950403022657.20912a-100000@aries.ibms.sinica.edu.tw>
References: <199504021802.LAA00189@corbin.Root.COM>
	<Pine.BSI.3.91.950403022657.20912a-100000@aries.ibms.sinica.edu.tw>
Reply-To: nate@sneezy.sri.com (Nate Williams)
From: nate@sneezy.sri.com (Nate Williams)
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

Brian Tao writes:
> > >    If we had a filesystem that dealt with sparse files correctly,
> > 
> >    Uhh, we do - FFS deals with them just fine.
> 
>     Hmmmm... what was that discussion a few weeks back about sparse
> files then?

Tar didn't realize that FFS handled them correctly so it didn't work
correctly.  It has since been corrected.


Nate