Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

When glibc attacks! 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Try Debian (Score:2)

    by autarch (914) on 2003.10.28 11:17 (#25241) Homepage Journal
    I run Debian unstable, and have upgraded libc and it's associated files countless times, without any problems. Of course Red Hat screws it up, but their package management system is horrid.
    • That's so Linux user. There's a little script that all Linux people go through when they're doing support:
      • Doesn't work? Upgrade your kernel!
      • Still doesn't work? Try a different distribution!
      • What was your problem again?

      I'm sorry. I've been reading jwz [jwz.org] too long.

      FWIW, I've been using RedHat a while and never had any problems with glibc upgrades screwing up. Lots of problems with locales (solution: nuke), but never glibc. :-)

      -Dom

      • Well, there are certainly other choices, like not using Linux. I doubt that any other Unix-y thing will be much better than Debian in terms of ease of upgrade, though.

        Then there's Windows, which we all know and love or hate. As for Mac OS X, it seems nice, except for all the things I need to do my development work that only sort of work/compile properly there. I don't want to do a compiler dance every time I need some new Perl module with XS installed.

        Basically I've really only used two Linux distros,
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.