Skip to main content

CentOS 4.8 in Virtualbox 5.1.x



Years ago I was part of a project that was developed on and ran on CentOS 4.8. The software we developed was only used in-house so we were able to work around any bugs we found. The development cycle was extremely short, 4 months, considering the end result.

While we've backed up the source frequently over the years the software really never got a major facelift. I spent a bit of time over the years making some minor changes (I gave the menu a facelift changing it from rotating gifs to CSS, and made some code changes to deal with a tax shift that happened years ago), but what the project really needs is a major overhaul.

One of my goals right from the outset was to open source the project, but this didn't happen because I was simply too swamped with other things to completely audit the code. Also I wanted to simplify the project before exposing it to the world. Initially we based the project on an eCommerce suite (OSCommerce). At the time we were using that suite for another project and we thought we'd just export the database to another live site based on the same eCommerce suite. That never happened and the eCommerce suite added many more tables and fields we never ended up using (though we added a few of our own).

This all brings me back to the fact that the project was running on CentOS 4.8, an old version of CentOS (which has been on version 7 for awhile). I struggled getting CentOS 4.8 to install in Virtualbox 5.1.x, mostly because I was trying too hard. CentOS would start to boot then hang with an NMI error. The problem was that I was trying to install using the Linux kernel 2.6/3 as a base when what I really needed to do was just select Red Hat 64 (the default). I was overthinking the installation. When I finally tried the default selection for Virtualbox CentOS 4.8 installed just fine.

Comments

Post a Comment

Popular posts from this blog

Our media encoding process

It occurred to me that I started posting to debugfs as if I just left off from my old domain (a story for another time). I had something in the order of 300 articles on the site so naturally posts on this site don't have the context they had on the old site. When I first started debugfs I talked about the Handbrake command-line script I run on our KODI server to shrink the size of Blu-rays (since they can be huge). I didn't really get into the details of the whole process and I've since changed how I rip and encode media. When I buy a DVD/Blu-ray the first step I take is to back-up the media using MakeMKV. MakeMKV is great for dumping both Blu-ray and DVD content to a .mkv file. I prefer .mkv over .mp4 because I love subtitles and the .mp4 container only lets you "burn" one subtitle into the file. Files in an .mkv container can contain as many subtitles as the DVD/Blu-ray has. I normally rip these on my desktop workstation which has a late 2013 AMD A8-5...
2 comments
Read more

That itch to upgrade again - Ryzen 5 2600G?

Lately I've been collecting a lot of movies. Each week Maria and I set a small budget for personal "wants," much of mine has gone to DVDs and the occasional Blu-ray disc. I've been lucky to find some really great deals, but it's got to the point where I'm backed up because ripping all the media is taking more time than I have on evenings and weekends. From what I've read ripping Blu-rays (unless you're also re-encoding them) is entirely dependent on the Blu-ray drive - there's little to be gained by upgrading to a new CPU/motherboard. I use a licensed copy of MakeMKV to rip my Blu-rays. Then I transfer the ripped mkv to our KODI machine and using HandbrakeCLI (the command-line version of Handbrake) to compress the large Blu-ray file to a smaller file. I could compress the file on my desktop, but my AMD A8-5600K APU doesn't have the same power as our KODI machine (which has an i7-2600 and is cooled with a Corsair H60 water cooler). The...
Post a Comment
Read more