X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=1.1 required=5.0 tests=AWL,BAYES_20,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RFC_ABUSE_POST,TW_KC,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: From: Jay K To: , , Subject: RE: upper limit to df reported available size? Date: Sat, 11 Dec 2010 01:51:00 +0000 In-Reply-To: <1292030585.3028.ezmlm@cygwin.com> References: <1292030585 DOT 3028 DOT ezmlm AT cygwin DOT com> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 > I guess what we really need > is to redefine fsblkcnt_t to become a 64 bit type. Oh well, this > requires another backward compatibility hack, just like back when we > switched to 64 bit off_t (Cygwin 1.5). Let's do it at the same time as > we change sigset_t and time_t to 64-bits(with knock-on effects to > struct stat, among others). In other words,all good changes, but certain= ly > something that will take a lot ofplanning to pull off in one go. =20 =20 Can you fix the jmp_buf size then too maybe? It is blown up by a factor of 4. http://sourceware.org/ml/cygwin/2009-01/msg00863.html =20 I realize it has less/no value to fixing. But I'm not sure how changing the others won't require *everything* (just about) to be recompiled anyway. Maybe you rename functions somehow? =20 =20 Thanks, - Jay =20=20=09=09=20=09=20=20=20=09=09=20=20 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple