On Tue, 31 Oct 2000, Matti Aarnio wrote: > Something along the lines of: As we no longer have access control > in form of having magic UIDs, e.g. zero vs. non-zero, we could as well > begin to use UTF-16 UNICODE 3.0 encoded strings for UID referral in > fixed size arrays giving us instant Java string compability. > (Ok, far fetched, but just you wait...) To fsck with Java, there are reasons to represent text as text completely unrelated to that crap. Actually, flag-day might be a good idea - we definitely could live without _many_ system calls. And not just ones that have analogs with wider fields. Look through the syscall tables and see how much of it consists of useless junk that belongs to userland. Sigh... - 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
- Re: 64-bit inode numbers (was: glibc 2.1.96) Mark Kettenis
- Re: 64-bit inode numbers (was: glibc 2.1.... H. Peter Anvin
