From owner-freebsd-current@FreeBSD.ORG Fri Dec 19 22:23:51 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 4DC1216A4CF; Fri, 19 Dec 2003 22:23:51 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D4F843D39; Fri, 19 Dec 2003 22:23:50 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfldp.dialup.mindspring.com ([165.247.213.185] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 1AXaWj-0007S2-00; Fri, 19 Dec 2003 22:23:49 -0800 Message-ID: <3FE3EAF5.94E23A4@mindspring.com> Date: Fri, 19 Dec 2003 22:23:49 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Tim Robbins References: <3FE29BA4.9060205@unisa.edu.au> <3FE2CD51.FCF0BD4D@mindspring.com> <20031219114853.GA234@wombat.robbins.dropbear.id.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4bf4971518ae16ad6b83e1d74d791a7f93ca473d225a0f487350badd9bab72f9c350badd9bab72f9c cc: Benjamin Close cc: freebsd-current@freebsd.org Subject: Re: smbfs 4G max file size 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: Sat, 20 Dec 2003 06:23:51 -0000 Tim Robbins wrote: > On Fri, Dec 19, 2003 at 02:05:05AM -0800, Terry Lambert wrote: > > Benjamin Close wrote: > > > Whilst tinkering with some backups the other day I noticed that > > > smbfs capped out at 4G. > > > Does the protocol restrict it to this limit or is there something else? > > > > It is a limitation imposed by the 32 bit file size in bytes field > > for the over the wire protocol. It occurs becaus the FreeBSD SMBFS > > client code uses a slightly older, cruftier version of the SMB > > protocol (at least this is my understanding). > > > > I've acutally suggested a couple of times in the past that someone > > take the Darwin SMBFS code from MacOS X (10.3, Panther), which is > > now up on the Apple developer site, and back-port it to FreeBSD. > > This is a pain to do without proper change logs or version control > and there are problems with their choice of licence. In addition, > porting Apple's code would re-introduce many bugs that have been > fixed in FreeBSD. I think you haven't looked at the code in question. Apple only applies the APSL to code that it writes. There are a number of projects that were originally external code, and for those, the license is whatever it started as. Since the SMBFS code is a port of the FreeBSD SMBFS code, the license has been left alone. As to the reintroduction of bugs, I seriously doubt it, since the SMBFS follows the FreeBSD changes pretty religiously on its own. -- Terry