>Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> I think you'll find Red Hat went glibc before Debian.
>
>What does this mean "went glibc"? Debian hasn't released a glibc
>distribution yet (you can download it, but it's technically not yet
>released -- no official cdroms yet).
I suppose that they are working on installations software.
You reminded me more, Debian continue to backport all security and needed
patches from hamm (libc6) to bo (libc5) for `stable' people that is still
happily using libc5 without one security problem (but with a bit outdated
software of course).
Also Debian provide you i486-linuxlibc1-gcc that compile against libc5 and
you have for every package the shared objects and the includes for libc5
and libc6 and you can continue compiling against the two libc libraryes on
the same system only changing the name of the compiler without one
problem. I compiled postgres 6.2.1 on my libc6 system some time ago only
changing the name of the compiler using the `configure` script, then I
copied the binaries in a libc5 system and worked without a warning.
>That said, it's not been glibc, as such, that's been holding back debian
>-- getting everything else working reasonably. [Debian is probably going
>to move to an "incremental release" sort of a system, which (if it had
>been in place in the past) would have resulted in a number of releases
>which were a mix of libc5 and libc6. Debian is pretty good, but it
There are no mixed release. 1.3 is libc5. 2.0 is fully libc6. 2.1 ? (I am
not sure of the number) it' s just started as unstable. 1.3 is dieing. The
only software I am using libc5 are acroread and netscape.
>doesn't matter if most people prefer to use something else only because
>they need the newer software.]
Eheh, you are really not using Debian... I only can agree that there are
less official release than RH (and this only metter people that upgrade
using CD), but note that this mean also that there are less frequent
needed set of bugfix. If you install software from unstable you are always
uptodate (as me ;-). Maybe you are more happy to use a distribution that
call unstable -> stable. Debian call unstable the latest software.
Here some examples:
1. Netbase provided ipchains after some days 2.1.x used it as default
firewall code.
2. modutils started to autoprobe if kmod is present after some days of the
inclusion of kmod in the kernel.
3. pppd got fixed after some days we discovered the y100 problem.
etc...etc...
The only software I had to compile by hand because is outdated (but works
fine with 2.0.x) is procinfo since the maintainer seems lazy ;-).
Instead I had some problems with RedHat. For example RH identd don' t
resolve username if the user is a nis user (don' t ask me why since I have
not time to waste on RH bugs). This bug breaks postgresql remote
autentication (note that the postgres I was using was been compiled and
distributed from RH). I fixed the RH identd problem overwriting the RH5.0
identd binary executable with the identd Debian 2.0 executable.
Andrea[s] Arcangeli
PS. Excuse me people for the offtopic but I didn' resisted to answer ;-).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu