XXX Chats

arguments against carbon dating

Updating glibc gentoo

Now, you may be wondering, how do we fix this problem?

:-) To be clear: IF YOUR INSTALL IS THIS OLD, IT’S PROBABLY JUST AS EASY TO BACK UP YOUR IMPORTANT FILES AND START AFRESH. Password: gentoo gentoo-vm ~ # passwd New UNIX password: ************* Retype new UNIX password: ************* passwd: password updated successfully gentoo-vm ~ # rc-update add sshd default gentoo-vm ~ # /etc/init.d/sshd start Between the first tar command and the success of ’emerge -u DN system’, the true state of the system, and the state according to portage are different.

If you’re running on 2006.0 like this VM, then it will remove that profile, leaving you with a broken /etc/make.profile symlink, and a lot of the packages that you’ll need to update the system (update in a “normal” way) have been removed from the Gentoo mirrors, causing quite the headache.

With that out of the way, if you’re still interested, let’s begin! Luckily for us, Gentoo provides incredibly old packages.

The information on Jeremy Olexa’s blog really helped me start this out, but it seems that there’s a couple of things that vary between installations, and I’m trying to list all that can “go wrong” with such an upgrade here (if you run into other problems, then post a comment, and I’ll see if I can figure something out! This particular blog post is based on this VMware image.

Yes, I realize that it would probably have been a shit-ton easier to install a fresh version of Gentoo, but I absolutely loathe the Gentoo installation process because I normally mess up one tiny thing than ends up causing me to have to re-install it again, or at the very least, boot up a repair CD. I don’t know what kind of setups you people on there on the bloggerchats are running! If you’re following along with me, and are using the VM, then you’ll want to set a new password and start up SSHD.

Comments Updating glibc gentoo