Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • 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 [] 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. :-)


      • 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,
  • [insert obligatory anacdote about Debian and its ability to update libc three times before breakfast here]

    That out of the way, some advice. Back in the mists of time when Apple Powerbooks were black and named after streets in New York, some Linux nutters decided it would be cool if they could run something other than a crappy co-operative multitasking system (translation: we crash by mutual consent) on Apple hardware. Enter Debian Linux/PowerPC. I had interesting times in 1998 when they were just getting off the ground. There was no stable tree, just unstable and yes it was unstable. A libc upgrade causing catostrophic system failures was a regular occurance.

    So what I learned to do, and my advice to you, is to do a static compile of your basic utilities to have in an emergency. fileutils, bash, textutils, rpm, etc... Or keep a copy of sash (Stand Alone SHell) around and set root to use that. It'll at least let you do *something* when libc fails.

    Or you could just use Debian. *p0inT and l4f*

  • Moving from RedHat may be an option for home use, but my two jobs won't be migrating from RH any time soon. And here's a confession: I like Red Hat. Yup. I like RPMs and SRPMs. I've even figured out how to use chkconfig to register my sysV init scripts. Would it be cool is rpm was more like CPAN, in that it sought out missing dependencies over the net for you? Sure. I know that's what RHN is all about.

    That said, only a fool wouldn't try to avoid making the same mistake again. I will certainly look