lkml.org 
[lkml]   [1999]   [Oct]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: How to extend struct stat?
On Fri, Oct 15, 1999 at 08:05:10AM -0700, Ulrich Drepper wrote:
> Jamie Lokier <lkd@tantalophile.demon.co.uk> writes:
> > Perhaps this is a bug in Glibc, I don't know. If so, they should change
> > __ino64_t and do the appropriate hacks for binary compatibility with old
> > stuff.
>
> I have asked around in the kernel hacking circles when I had to choose
> the values and got told that 32 bits are enough for ino64_t. So live
> with it.

That is your collected opinnion/wisdom for the user-space.

Let kernel, and kernel/user interface (for LFS/64 syscalls)
handle it as 64-bit entity, and you need to write new wrapper-
interfaces for them too..
Thwn when there really comes some case where 64-bit entity is
needed for USERSPACE, we cross that bridge and change glibc's
external 'struct stat64' and other places where __ino64_t needs
to be 64-bit.

However because for kernel/user interface doing changes is
painfull, all such changes must be done once, and all the way.

> --
> ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
> Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
> Cygnus Solutions `--' drepper at cygnus.com `------------------------

/Matti Aarnio <matti.aarnio@sonera.fi>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:54    [W:0.054 / U:0.984 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site