On 3/6/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote: > 2007/3/6, Michael Homer <[EMAIL PROTECTED]>: > > On 3/6/07, Carlo Calica <[EMAIL PROTECTED]> wrote: > > > On 3/5/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > > > > > > > > It shouldn't make difference. Detsch tested the upgrade on a 2.3 > > > > system moving to a 2.4. I have never tried myself to upgrade Glibc. > > > > Can anyone take a look into this? Maybe by running gobo inside qemu or > > > > other emulator.. I don't have the time to test that right now, > > > > unfortunately. > > > > > > > > > > I tested a Glibc upgrade in qemu. Fresh 013 install. InstallPackage > > > Scripts and Compile. Compile DHCPCD (we need a new bin package). > > > InstallPackage Glibc. D/L and sig check fine. During SyminkProgram, > > > fine until ldconfig, then get "FATAL: kernel too old" error messages. > > > Now nothing works. On reboot, init dies with "FATAL: kernel too old". > > > I'll upgrade kernels and check again. > > That's exactly what happened for me. For the record, for anybody else > > who runs into this problem, here's how I fixed it: > > 1) Boot into another distro - I used Gentoo, but it shouldn't matter > > what. Mount the Gobo partition on /mnt/gobo. > > 2) cd /mnt/gobo/Programs/Glibc > > 3) rm -r 2.5 > > 4) rm Current > > 5) ln -s 2.4 Current > > 6) cd /mnt/gobo/System/Links/Libraries > > 7) ln -sf ../../Programs/Glibc/2.4/lib/* . > > 8) cd ../Executables > > 9) ln -sf ../../Programs/Glibc/2.4/bin/* . > > 10) rm -f /mnt/gobo/System/Settings/ld.so.conf (it's a symlink) > > 11) echo /System/Links/Libraries > /mnt/gobo/System/Settings/ld.so.conf > > 12) ldconfig -r /mnt/gobo -f /System/Settings/ld.so.conf -C > > /System/Settings/ld.so.cache > > 13) cp /mnt/gobo/System/Settings/ld.so.cache > > /mnt/gobo/Programs/Glibc/Settings > > 14) chroot /mnt/gobo (this should work _at this point, and no sooner_) > > 15) SymlinkProgram Glibc 2.4 > > 16) Reboot into Gobo > > All those commands need to be run as root - under sudo is fine. It's > > also possible that some of those commands aren't actually necessary, I > > didn't perform rigorous elimination testing on them. It might be > > worthwhile making up a statically-linked binary to perform those steps > > in an emergency and including it in Scripts, if there's no way to > > avoid it. > > -Michael > Steps 2-9 can be skipped by using RescueSymlinkprogram, which is a > static binary included in Scripts, instead. That should probably also > take care of reseting your ld.* files as well. I tried it; it didn't actually seem to do anything. At least, running it didn't make things work, and the Current symlink still pointed to 2.5 when I examined it from Gentoo.
I also don't think it would have been able to run ldconfig - it was one of the binaries that didn't work. That's why I had to use the Gentoo one with the -r /mnt/gobo (change to and use new root directory) option. Actually, I guess that same problem with ldconfig would scupper making a "RescueGlibc" binary. I don't know what's involved in generating ld.so.cache, but I doubt it's simple. > And you can use the GoboLinux install CD (one does most probably have > one lying around). Yeah, a live CD should be fine. I couldn't use the Gobo one because of the dodgy CD drive I mentioned before, possibly combined with some bug on the CD (Ubuntu CDs work fine, but the Gobo one will die at random at one of several points before the prompt appears). For anybody else, though, a Gobo CD could even be better - you might be able to use the SymlinkProgram on the CD by changing the $goboRoot variable, which would avoid the manual linking in the middle. -Michael _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
