Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 14 Mar 2003 00:36:40 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Cc: "Pierre A. Humblet" Subject: Re: cygwin-1.3.21-1, problem with sparse file creation as default Message-ID: <20030314053640.GB12940@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com, "Pierre A. Humblet" References: <3E70AD52 DOT 744 DOT D4BC055 AT localhost> <000801c2e974$0a0541b0$78d96f83 AT pomello> <20030314024154 DOT GA33739617 AT hpn5170x> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030314024154.GA33739617@hpn5170x> User-Agent: Mutt/1.5.1i On Thu, Mar 13, 2003 at 09:41:55PM -0500, Pierre A. Humblet 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). > >Running a speed test would be interesting of course, but I point to an >advantage for most of us: with 32 bit uids the /var/log/lastlog file >can become enormous. Fortunately (for systems that support sparse >files), it is sparse. I think we'll have to come up with some other way of dealing with /var/log/lastlog for Win 9x though, won't we? cgf -- 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/