On 13 October 2010 07:21, Corey Kovacs <corey.kov...@gmail.com> wrote:
> > The problem I see with the suggestion before this is glibc and the > kernel. The kenrel uses glibc so if you I _believe_ you need to have > them both installed and ready to go before you reboot and remove the > old glibc. > > I haven't even begun to consider testing this, but I believe it's possible. It would be interesting to try it. The key thing to remember is that while the 64 bit kernel can run 32 bit programs, the 32 bit kernel cannot run 64 bit programs. The first challenge, though, is installing that 64 bit kernel on the 32 bit machine. I quick glance through /sbin/new-kernel-pkg suggests that this might be possible. If it isn't then you'll have to take the vmlinuz, initrd and /lib/module/<ver> from a different 64 bit machine (with a compatible initrd, of course). Then you can reboot. Now you have a 64 bit system with no 64 bit binaries. "uname -a" should tell you you have an x86_64 as well. The next stage would be to convince yum to upgrade to 64 bit binaries. It might be enough to do something like "yum reinstall" but you'd probably want to start by doing "yum install glibc.x86_64". Yum should take care of all the dependencies for you, but even so I'd assume that it's all going to go horribly wrong. When it does, of course, you'll be left with a system that doesn't work in a 64 bit environment and won't come up as 32 bit any more. You're going to need that backup. You did take a complete backup didn't you? Unless the re-configuration is a nightmare and you're prepared to try several times then re-install. Unless you want to just do it to prove it can be done ... jch
_______________________________________________ rhelv5-list mailing list rhelv5-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv5-list
