![](\"https:\/\/i0.wp.com\/thedigitalmachine.com\/images\/fedora.png\")
<\/center><\/p>\nWith Red Hat dropping support for Red Hat Linux (duh!), it was only a matter of time before I made a move to a new distro – when it comes to running an internet-exposed server, a little guy like me has no choice – I HAVE to run an up-to-date auto-patched distro. With cyrus playing the role of the proverbial straw, I decided to upgrade (sidegrade?) to Fedora. Read on for all the gory details – just kidding, it’s not that bad. In fact, in retrospect, yum made it downright smooth.<\/p>\n
<\/p>\n
First, a note on mirrors.\u00c2\u00a0 The instructions I was following recommended giving Red Hat a break by using one of the many fedora mirrors available.\u00c2\u00a0 I dutifully selected an aleron mirror, which wasn’t too far away and had been blazing fast in the past.\u00c2\u00a0 However, during my adventures, I found that\u00c2\u00a0 the mirror wasn’t fully up to date, and that caused me a few dependency headaches I could have done without.\u00c2\u00a0 I recommend you use the default yum config which points right to redhat.com.\u00c2\u00a0 Sorry, Red Hat, but we’re talking about our babies, here!\u00c2\u00a0 \ud83d\ude1b<\/p>\n
The big plan was to jump straight from Red Hat 9 to Fedora Core 2, using rpm -Uvh yum-2.0.7-1.1.noarch.rpm<\/p>\n rpm -Uvh fedora-release-2-4.i386.rpm<\/p>\n yum upgrade<\/p>\n Oh if life were only so simple.\u00c2\u00a0 :>\u00c2\u00a0 Dependency problems followed, I tried to fix:<\/p>\n yum remove ‘redhat-config-*’<\/p>\n yum remove imap<\/p>\n yum remove pine<\/p>\n yum remove cadaver<\/p>\n But they kept coming on strong.\u00c2\u00a0 I took a deep breath and a step back.\u00c2\u00a0 Conclusion: better go Red Hat 9 -> Fedora Core 1, then Fedora Core 1 -> Fedora Core 2.<\/p>\n rpm -e yum<\/p>\n rpm -Uvh yum-2.0.4-2.noarch.rpm<\/p>\n rpm -Uvh fedora-release-1.3-i386.rpm –force –nodeps<\/p>\n yum upgrade<\/p>\n Cool, only one dependency problem came up:<\/p>\n yum remove jdkgcj<\/p>\n Fixed that, and FC1 dropped right into place.\u00c2\u00a0 Feeling emboldened, and not wanting to have to REALLY set up FC1 before jumping to FC2, I decided\u00c2\u00a0 that I would upgrade right then and there to FC2 before rebooting, while I still had a working network connection etc.:<\/p>\n rpm -e yum<\/p>\n rpm -Uvh yum-2.0.7-1.1.noarch.rpm<\/p>\n rpm -Uvh fedora-release-2-4.i386.rpm<\/p>\n yum upgrade<\/p>\n There were only a few more snags to work through before it decided to roll on:<\/p>\n rpm -e libmrproject-devel<\/p>\n rpm -e db4-java<\/p>\n rpm -e galeon<\/p>\n Then it was off to the RC2 races.\u00c2\u00a0 OK, so far so good.\u00c2\u00a0 Rebooted and… no network connection.\u00c2\u00a0 I don’t remember the details, but I had to tinker around with my ethernet driver before I got it working again – it’s frightening having to troubleshoot gear with NO INTERNET CONNECTION, it was like the good old days!<\/p>\n Once that was resolved, there were only a couple small snags left.\u00c2\u00a0 The first odd thing, and correct me if I’m wrong here, was that FC2 seemed to install two kernels, a 2.4 and a 2.6.\u00c2\u00a0 When I boot with the 2.4 I’m fine, but the 2.6 still has basic hardware problems (X doesn’t recognize the mouse, for starters).\u00c2\u00a0 Perhaps after a few more “yum update”‘s 2.6 will settle down.<\/p>\n The final problem was that my built-from-source apache wouldn’t fire up.\u00c2\u00a0 I dug up and polished off my handy-dandy Peace!<\/p>\n","protected":false},"excerpt":{"rendered":" First, a note on mirrors. The instructions I was following recommended giving Red Hat a break by using one of the many fedora mirrors available. I dutifully selected an aleron mirror, which wasn’t too far away and had been blazing fast in the past. However, during my adventures, I found that the mirror wasn’t fully up to date, and that caused me a few dependency headaches I could have done without. I recommend you use the default yum config which points right to redhat.com. Sorry, Red Hat, but we’re talking about our babies, here! \ud83d\ude1b<\/p>\n The big plan was to jump straight from Red Hat 9 to Fedora Core 2, using rpm -Uvh yum-2.0.7-1.1.noarch.rpm Oh if life were only so simple. :> Dependency problems followed, I tried to fix:<\/p>\n yum remove ‘redhat-config-*’ But they kept coming on strong. I took a deep breath and a step back. Conclusion: better go Red Hat 9 -> Fedora Core 1, then Fedora Core 1 -> Fedora Core 2.<\/p>\n rpm -e yum Cool, only one dependency problem came up:<\/p>\n yum remove jdkgcj<\/p>\n Fixed that, and FC1 dropped right into place. Feeling emboldened, and not wanting to have to REALLY set up FC1 before jumping to FC2, I decided that I would upgrade right then and there to FC2 before rebooting, while I still had a working network connection etc.:<\/p>\n rpm -e yum There were only a few more snags to work through before it decided to roll on:<\/p>\n rpm -e libmrproject-devel Then it was off to the RC2 races. OK, so far so good. Rebooted and… no network connection. I don’t remember the details, but I had to tinker around with my ethernet driver before I got it working again – it’s frightening having to troubleshoot gear with NO INTERNET CONNECTION, it was like the good old days!<\/p>\n Once that was resolved, there were only a couple small snags left. The first odd thing, and correct me if I’m wrong here, was that FC2 seemed to install two kernels, a 2.4 and a 2.6. When I boot with the 2.4 I’m fine, but the 2.6 still has basic hardware problems (X doesn’t recognize the mouse, for starters). Perhaps after a few more “yum update”‘s 2.6 will settle down.<\/p>\n The final problem was that my built-from-source apache wouldn’t fire up. I dug up and polished off my handy-dandy Peace!<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[5,4,9],"tags":[],"class_list":["post-73","post","type-post","status-publish","format-standard","hentry","category-linux-projects","category-projects","category-websites"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t
\n rpm -Uvh fedora-release-2-4.i386.rpm
\n yum upgrade<\/p>\n
\n yum remove imap
\n yum remove pine
\n yum remove cadaver<\/p>\n
\n rpm -Uvh yum-2.0.4-2.noarch.rpm
\n rpm -Uvh fedora-release-1.3-i386.rpm –force –nodeps
\n yum upgrade<\/p>\n
\n rpm -Uvh yum-2.0.7-1.1.noarch.rpm
\n rpm -Uvh fedora-release-2-4.i386.rpm
\n yum upgrade<\/p>\n
\n rpm -e db4-java
\n rpm -e galeon<\/p>\n