lkml.org 
[lkml]   [2006]   [Jul]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [klibc] klibc and what's the next step?
Olaf Hering wrote:
> "It would be nice if ..." someone can build a list of things that
> changed over time. Say from 2.0.0 to 2.6.18. Just struct layouts and defines.
>
> I havent tried it, but one would hope that the /bin/ls from SuSE 5.3 still
> works today. Guess its time for me to actually try that the next days.

You know how much code there is in glibc to make your /bin/ls still work?

That being said, it in general isn't a problem to continue to use the
same exact sets of system calls, but that also means skipping any new
functionality. In recent memory that includes things like 64-bit file
offsets and high signals, even more recently it means things like
openat() and splice(). A full-blown libc also has to deal with
LinuxThreads version NPTL. Etc.

Again, I fully expect that klibc-0.1 still works on the current kernels,
but current klibc wouldn't work on 2.4 kernels.

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

\
 
 \ /
  Last update: 2006-07-11 20:25    [W:0.148 / U:0.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site