"Hemmann, Volker Armin" <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Mon, 23 Oct 2006 21:10:58 +0200:
> DO NEVER downgrade glibc! I have been there, bitten by it very, very > hard. A nonbooting system, because not even udev runs, is a big problem > (I solved it, but it cost me time, sweat and tears). That's what a backup image, a snapshot of the system taken periodically when everything is known to be working, is useful for. =8^) As I said, I had to boot to the backup to allow me to do the downgrade to my main system using ROOT=, but it worked. > and rebuilt EVERYTHING that was built against the new glibc! Every > single app, every lib, everything. You miss something and you will > suffer. Actually, I was expecting issues, but haven't had any so far but one, easily fixed. As you mentioned, the latest kernel didn't want to boot, so there again I backed up a couple notches and got a working one, but everything else I had merged since then, notably including all of KDE 3.5.5, merged against glibc-2.5, seems to be working great against glibc-2.4-r4, which as it happens was merged only a couple weeks earlier -- actually that's probably my saving grace or I'd likely have had more issues. As it is, booting 2.6.18 with glibc-2.4-r4 works great, better than 2.6.19-rc2 with glibc-2.5 actually, due to the crashes that started the whole thing on the latter combo. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [email protected] mailing list
