Messages in this thread | | | Date | Sun, 5 Dec 1999 22:44:57 +0000 | From | Steve Dodd <> | Subject | Re: Getting system info from the kernel |
| |
On Tue, Nov 16, 1999 at 12:38:18AM -0500, Alexander Viro wrote:
> It would be reall nice if we had a generally accepted library with sane > interface that could be used by everything. Then the changes would be much > easier. Right now we have all sorts of spiffy little utilities (seriously > resembling DOS BBS collections - bad symptom in itself), each of them > doing its own thing in its own way. Yes, if they would directly use the > kernel memory it would be even worse. But even in the current form it's a > mess.
Am I mad or is part of the problem that *everything* is in glibc? I'd love to see things which were system interfaces but in user-space moved to a libsys.so or libkernel.so or liblinux.so or something. A library that was maintained with the kernel[0], which glibc could talk to. Basically make libc what it (theoretically) once was, a library of utility functions for C programmers. BCPL programs shouldn't need to be linked to libc <g>
[0] God knows how you deal with linking the right library for different multiple major kernel versions installed on the same machine though; ld.so hackery?
-- Advocate: n. Pack animal, tends to produce a lot of noise, especially when two groups greet each other with projectile vomit and long loud screams. Can imitate speech better than parrots, but can't be used as pets due to guano problems.
- 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/
| |