Ulrich Drepper wrote:
>
> "H. Peter Anvin" <[EMAIL PROTECTED]> writes:
>
> > Sorry for being picky, but LFS, specifically, means using an heterogenous
> > API using seek64() instead of lseek() and so on and so forth.
>
> Wrong. LFS also includes -D_FILE_OFFSET_BITS=64 which transparently
> replaces the non-LFS types and functions.
>
Fair enough. However, the question still remains if we should make it
the default and make the old heterogenous API the explicit option.
-hpa
--
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
- Re: 64-bit inode numbers (was: glibc 2.1.96) H. Peter Anvin
- Re: 64-bit inode numbers (was: glibc 2.1.96) Ben LaHaise
- Re: 64-bit inode numbers (was: glibc 2.1.96) H. Peter Anvin
- Re: 64-bit inode numbers (was: glibc 2.1.96) Ulrich Drepper
- Re: 64-bit inode numbers (was: glibc 2.1.... H. Peter Anvin
- Re: 64-bit inode numbers (was: glibc... Ulrich Drepper
- Re: 64-bit inode numbers (was: g... Matti Aarnio
- Re: 64-bit inode numbers (wa... H. Peter Anvin
- Re: 64-bit inode numbers (wa... Paul Eggert
- Re: 64-bit inode numbers (wa... Alexander Viro
- Re: 64-bit inode numbers (wa... H. Peter Anvin
- Re: 64-bit inode numbers (wa... Alexander Viro
- Re: 64-bit inode numbers (wa... Ulrich Drepper
- Re: 64-bit inode numbers (wa... Andries Brouwer
- Re: 64-bit inode numbers (wa... Geoff Keating
