Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <01e201c2e9bc$aa4642d0$78d96f83@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: <cygwin AT cygwin DOT com>
References: <3E70AD52 DOT 744 DOT D4BC055 AT localhost> <000801c2e974$0a0541b0$78d96f83 AT pomello> <20030313214424 DOT GT27047 AT cygbert DOT vinschen DOT de>
Subject: Re: cygwin-1.3.21-1, problem with sparse file creation as default
Date: Fri, 14 Mar 2003 00:00:03 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Corinna Vinschen wrote:
> On Thu, Mar 13, 2003 at 03:20:10PM -0000, Max Bowsher wrote:
>> We've had no proof of advantages (except in one very restricted
>> corner case), and no disproof of disadvantages (i.e. speed
>> penalties).
>
> Max, do you perhaps remember the discussion on cygwin-patches?   You
> were the only one actually against it (well, besides Gary who was
> against it
> due to misinformation) without having *any* proof that it has
> disadvantages.

No proof that it *doesn't* have disadvantages, either.

Since there is no way to un-sparsify a file (short of re-creating it), I've
decided that it is easier for me to run with a self-compiled Cygwin DLL,
until I have the time to concoct suitable benchmarking programs to obtain
actual evidence (positive or negative) on the influence of making files
sparse unnecessarily.

> Do you also remember that we asked for a testcase to show the
> disadvantage (disfunctionality, bad timing, etc) and nobody showed up
> since Feb 20, when I checked this in?

Yes. I haven't got around to writing a testcase - partly because following
cygwin cvs is interesting, so I don't view it as an inconvenience that I'm
compiling my own dll.

>> Plus now an actual bug has surfaced.
>
> Nonsense.  It's a bug in winfile, not in Cygwin.  Are you using
> winfile?

No. I just have a feeling of abstract wrongess about the situation.

So I'll shut up now, until I write that testcase.

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/