From owner-freebsd-current@FreeBSD.ORG Mon May 12 07:55:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC89A37B401 for ; Mon, 12 May 2003 07:55:07 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E6BE43FDF for ; Mon, 12 May 2003 07:55:06 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0346.cvx40-bradley.dialup.earthlink.net ([216.244.43.91] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19FEhg-0006zl-00; Mon, 12 May 2003 07:55:01 -0700 Message-ID: <3EBFB57D.7376D4A8@mindspring.com> Date: Mon, 12 May 2003 07:53:49 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kirk McKusick References: <200305112244.h4BMiFTh036221@beastie.mckusick.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a46ffd3ec42faf24ad5dfbf780a373ca453ca473d225a0f487350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org cc: Julian Elischer Subject: Re: large ufs2 partitions and 'df' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2003 14:55:08 -0000 Kirk McKusick wrote: > Julian Elisher wrote: > > I think that swithing to a new syscall with a fixed structure > > and using the rules you mention above to populate the structure in an > > ostatfs call might be the best answer. > > Old binaries probably only need to know that there is > X blocks free > > and not necessarily the correct number. > > New binaries can use the new syscall. > > So right you are. It would be possible to get the space by nibbling > a bit more space from MNAMELEN, but at some point we need to just bite > the bullet and define a new structure. I am leaning towards believing > that time is now. If we do define a new structure, I would like to > clean up the existing one a bit. I would propose this: If you're going to change the structure, please put a version number as the first field, so that it's never a problem again. Also, put a spare field on the end (64 bits) to allow for future expansion that maintains binary compatability (by way of choice about what to copy in). -- Terry