Date: Tue, 6 Jan 2004 21:42:26 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Scott W <wegster@mindcore.net> Cc: freebsd-questions@freebsd.org Subject: Re: how to use lseek() system call with over 2G files? Message-ID: <20040107034226.GN38169@dan.emsphone.com> In-Reply-To: <3FFB76C2.2040604@mindcore.net> References: <3FFAF127.3080309@dynaweb.ru> <20040106174828.GD38169@dan.emsphone.com> <44smissuq2.fsf@be-well.ilk.org> <3FFB76C2.2040604@mindcore.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jan 06), Scott W said: > Lowell Gilbert wrote: > > off_t has *never* been anything but 64-bit in FreeBSD. > > This is interesting, having had to deal with the LARGEFILE_64_SOURCE > and _LP64 'hacks' (llseek(), creat64(), etc etc...back in Solaris > from 2.6 on, which seem to still be in place in Solaris 9. Are all > file operations and mmap() 64 bit capable then in FreeBSD (or > presumably Open/Net/FreeBSD?) I don't see any LARGEFILE constants in > FreeBSD.... Correct. The whole reason for the largefile stuff was to ease the transition from 32-bit off_t to 64-bit off_t. Even now, I don't think Linux, Solaris, or AIX enable 64-bit off_t by default. Heck, Solaris and AIX still default to building 32-bit /binaries/, even though they've been on 64-bit CPUs for ages. My guess is the "transition period" will last at long as x86 CPUs exist :) Tru64 always ran on the 64-bit Alpha, so it's another OS that never had to deal with it. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040107034226.GN38169>