Are you gonna to upgrade to glibc-2.4? Are you going to do it from source or wait for Slackware packages?

Peace....

IMHO, I shall wait for them official packages, I don't want to pointlessly screw up the system

i agree with raska, since with official packages, usually there will be no big deal. Just update, run ldconfig, and everything seems to happen naturally

Come on, guys! Where's your sense of adventure?

Peace...

Sense of adventure? I prefer to spend my spare time bungee jumping onto my wife than trying to be a guinea pig for updating a critical package like glibc. This is the way it usually works is this forum:

Help! I just installed the new glibc from foobar, and now I have a kernel panic!

Did you remember to recompile the foofoo package?

OK. I recompiled foofoo, now alsa has gone south.

(etc,etc)

I think I'll wait for the newest Slackware, not just some package that someone posts that was probably compiled with -current and gnome. (Both of which I avoid). Why? I want stable, not cutting edge. I prefer a functional system.

here's Pat comments on glibc-2.4 on the latest changelog

I LOVE Pat's way of making sure things are rock-solid before doing a version release. Beta-testing is not my idea of fun....lol

I'll wait for the next release of Slackware before 'upgrading....I do make sure I'm up to date for 10.2 security, etc.), but even 'current' is off my scope (I see way too many 'I just upgraded foo in current, and now...').

Well, I can't really argue with that.

Yeah, I hear ya. I guess I've been fortunate I haven't had those kinds of problems. I'm using a Slackware 8-based system and I've kept it up to date manually with great success.

Yep, I hear you on this too. I'm thinking I'll handle this transition when I get a new PC. My current Pentium II 350MHz is still going strong, but I want something faster. Something more "21 century".

I was mainly curious to see how many were planning to take the dive.

Peace...

Want a quick 'guage'? every week, do a search on LQ for 'glibc-2.4' and see the horror....lol

As far as 'transition' w/PII 350 , I'm running a website/forum/mail servers on a PII300. 10.2, 512MBram. Don't have one problem with it. That is the cool thing about Linux. Old school just plain works. 'Legacy Support' means something, not like XP where you need the biggest/fastest to make it do anything.

I did a search on glibc-2.4 and found a bunch of threads matching "glibc" but for 2.4. So I didn't bother wading through all the hits.

As I said, my system is rock solid but is definitely not as "crisp" as I would like. I've also got 512MB of RAM and that helps a lot but doesn't change the fact it takes 4-5 hours to compile X or wine, etc. (Of course, compile times change with any given build).

As a comparison, I built OpenSSH 4.3p2 on my desktop system and on a Pentium III 700MHz box, also with 512MB of RAM, that I admin at the same time. I logged into the PIII-700 via ssh and that box hosts 15-20 websites, has Qmail/Vpopmail running handling e-mail for about 10-12 of those sites (not sure how many accounts total), SpamAssassin, ClamAV, and Courier-IMAP. On average between 50-100MB of swap is used on that box where mine (PII-350) hardly uses any (sometimes it will). It's simply amazing (to me) watching how much more quickly the configure script runs on the PIII-700 than on my desktop machine. I have the terminal windows side-by-side so I can watch them run. I always use "time" to get actual timings of builds but to watch one window "scream" while the other window just scroll is heartbreaking. In fact, I sometimes give my machine a "head start" so it will at least appear to be "fast".

The PII-350 has been stable enough AND a good enough performer that I've been putting off a hardware upgrade for about 3 years now. One of these days I'll get around to it.

I've also been casually looking at other distros to see how I would feel operating outside of a Slackware environment. We'll see what happens in the end.

Peace...