Quote:>Btw, you might want to try Debian instead of Red Hat, as in my case
>the switch from libc5 to libc6 has been practically transparent. As
>for glibc2 -> glibc2.1, one would hope that as soon as glibc attains
>full posix compliance the madness will stop.
Until glibc 2.2 rolls around and breaks some more interfaces, for
the sake of compatability with some other standard of the week.
Being ``standards compliant''(tm) doesn't mean that you have to take
a pitchfork to backwards compatability.
Quote:>Also, the LSB specifies
>glibc2.1 as the Linux libc.
And that settles the LSB as yet another nonsensical linux ``standard''
that will be hyped like the second coming of christ, then quickly
shoved aside when the next best thing is invented.
If the LSB was serious, they'd publish an interface and say that a
system conforms to their standard if it matches the interface. But
that wouldn't be the Linux way, because that would be compelling
people to stick to a published behavior and that is apparently just
the first step towards Microsoft control.
Sheeesh, I'll bet that according to the LSB my distribution Mastodon
(which has about 4 times as many BSD programs as FSF programs, and
the only reason for that is I'm stuck with the GNU compiler
toolchain) doesn't even count as Linux.
____
david parsons \bi/ Where can I get a gif of the LSB logo with a red slash
\/ through it?