I Promise This Isn't A Mac Blog

New MacBooks today.

Okay, not that color isn't important, but slapping on an extra hundred and fifty bucks just to get the case in black? The price difference is $200 and you can upgrade the hard drive on the white model for $50. They are otherwise identical.

I suppose it'll make it easier to spot the suckers cool people.

Oh, wait. These people bought Macs. Silly me. (Interpret that how you want.)

In all seriousness, the mid-range white model isn't a terrible deal. If you don't mind integrated graphics and low resolution, and you don't mind (or prefer) a small laptop screen, this might just be for you.

At the moment, I'm convinced that if I bought one of these, I would end up loading Vista (beta in June) and/or Gentoo on it. Is there a right/middle-click driver for the touchpad available for Linux? I might have to write one. Not that I would ever get it done. I still haven't found time in my busy life to get MythTV up and running on athena.

<creative title>

Been up and running for a while now. I had a minor hiccup when the root partition failed fsck, but I was able to copy the files off to a backup parition, reformat, and copy them back. The failure happened at the same time as I had to manually turm off the computer (because it froze). I'm not sure if the filesystem error was the cause of the crash, or vice-versa. That's the second time it's happened. I'm thinking it might be ReiserFS, but I'm not overly worried. I pulled a backup script off the web and configured it to keep 4 weekly backups and 6 monthly backups at all times (once it builds up to that number, that is). There's a short list of locations you need to back up on a Gentoo system in order to be able to regenerate the exact same system in a straightforward and quick (ignoring compile time) manner.

I started using RAM/swap filesystems for /tmp and /var/tmp, and also for a writable /mnt/inbox folder shared via Samba. The inbox folder is capped at 100MB, while /tmp and /var/tmp are capped at 1GB and 3GB respectively. I have 1GB of RAM and 4GB of swap space. One nice benefit of this is that my compiles happen in /var/tmp, and the downloaded files are stored in RAM, so there's no time lost to reading and writing the hard drive.

The next step in my quest for the ultimate MythTV box is to become an expert (okay, well, maybe a knowledgeable novice) at configuring MySQL. I think that's the last step before I actually dive in to MythTV. We'll see.

In preparation for MythTV, I cleared out my 250GB Hard Drive (I moved the backup data from a partition on this drive to the one I had previousely been using on the 320GB drive for a 32-bit chroot--for which it turns out I don't have much use) and repartitioned it into one huge drive. I might break it up more later. That depends on the demands of Myth's storage scheme(s).

Athena has (has had now for a while) two internet hostnames: athena.homelinux.net, and athena.gentoofreaks.org

The first is updated through DynDns.org, which has limited selection of domains, the second is through afraid.org, which has literally thousands to chose from. RFH's router (a Linksys) can do DynDNS, so I moved that to there, and set up a cron script to update the afraid.org name.

I have Apache set up to route the two paths to different virtual hosts, but right now both of them are pointed at the same place, since I don't have much to put up. I also set it up so that each user can crate a public_html directory in his home folder accessable to the web, which is slightly more convenient than having to go to /var/www/localhost/htdocs/ and doesn't require that I give RFH write access if I want offer him hosting space.

w00t!

Hey! I can see!

After hours of reconfiguring the kernel, recompiling and rebooting, I finally solved the problem that was causing athena to boot without framebuffer support.

It turns out that I was compiling in framebuffer modules that conflict with vesafb, which is *the* module that works on x86_64, apparently. Mostly this was due to my confusion because I have an nvidia graphics card and there were two modules that said "nvidia."

So, now when I boot up with my custom kernel, I see all the wonderful status information fly by and then finally when it's all booted a login screen.

Yay.

Next up: installing X, Gnome, and KDE, and then...

On to MythTV! (I compiled in the pchdtv3000 driver, so this should be a cakewalk. Unless it isn't.)

Well, Here I Go

I tried switching to KDE, but X still wouldn't start up, so I'm switching to an athlon-xp configuration, and hoping for the best. One huge benefit of doing this is that I don't have to deal with having separate 32-bit libraries to link with all the programs that won't build under x86-64 (like Firefox).

Also in general everything should run more smoothely because of the large user base (and therefore greater testing visibility). Basically, under normal circumstances you wouldn't think of releasing something that doesn't work on an x86, but you might not consider whether your program runs (or even builds right) on some newfangled architecture that no one uses yet. Ironically, I may have to wait until 64-bit Windows makes 64-bit desktop computing common before real support arrives for my processor. Yeah, yeah, I know, the old "do it yourself" Linux mantra, bla, bla, bla. I don't think I'm at the point where I can reverse engineer my graphics card and write my own driver. Getting there though.

I just chrooted and issued the "emerge --sync" command, which means she's going to be compiling for a while.

I threw my old TV tuner into Athena. Apparently MythTV works with just about any tuner out there. Still, I want to get an HDTV tuner card, but I think I'll wait on that until I have a working graphical system with MythTV installed (and hopefully standard TV up and running). Boo broadcast flag.

I See Penguins

Please note: This post is a duplicate. The original can be found here. I am posting it on this blog for continuity.

---

Okay, okay, you've all been clamoring for a post. I give. So here goes. I am going to build a computer. I've wanted to do this for quite some time, but lately, it's all been coming together, and I've gathered enough momentum to see it through. The first event on the chain was my acquisition of a monitor. Slickdeals had a 17" flat screen CRT for $30 after rebates and I bit. I wasn't exactly sure what I wanted to do with the monitor at the time, but I figured I could always find a good use for it. It's a pretty good monitor⁰, and I've thought of a use for it. This all fits into my larger scheme of building a Linux¹ box that provides all the good functionality of a TiVo, but without the annoying parts (like the ads, the fact that they disabled the 30-second skip and don't delete commercials, and the fact that your recorded shows are stuck on your TiVo, and you can't really do anything useful with them). I don't just want a TiVo replacement or a Media Center PC. I want a server. I want to play with utilize Linux (because it will help me in my career/hobby), which brings me to the next event on the chain. I spoke with my sister Sazzly on the phone the other day and I mentioned that I was considering building a Linux box. I remembered that her roommate had one, and I asked what distro she was running. I use Red Hat at work, but really I didn't know that much about what the different distrobutions had to offer, or for that matter how to go about setting up a system. I know and use a lot of the every-day commands, but I don't know the ins and outs of administrating a Linux system. She said her roommate ran Gentoo², and then mentioned that it was really easy to install programs "because there's this one command that you type followed by the name of the program, and it installs automagically [paraphrase]." So naturally I had to do some research. Among other distro sites, I went to gentoo.org and looked around a bit. Apparently, Gentoo is the ultimate roll-your-own distro. And get this: when you install a program, you do it by downloading the source code and compiling it yourself! Oh, sure, this is possible on every Linux distro, and sure, you don't have to do it this way: you can also install from binaries, but the minute I read this, my jaw hit the floor and I began to salavate. Okay, not literally, but I was instantly hooked. This, you see, my young grashopper, is the path to ultimate optimization and customization. Processors can only be as efficient as the compiler that built the programs they're running tell them to be (this isn't 100% true, but bear with me), so if I bought a 64-bit processor and ran programs compiled for a 32-bit perocessor, it would still work, (because the 64-bit processor is backwards compatible) but aside from a few optimizations built into the processor, there wouldn't be nearly as much of a jump in performance as if the program were compiled for a 64-bit system. It gets even better than that. Suppose you had a Pentium 4, in fact, you probably do have a Pentium 4 if you bought your computer in the last couple of years. Most of the software that you run on your computer does not take advantage of all the bells and whistles that come with the P4 processor. This is because not everyone has one, and when you distribute your program in binary form, you don't want to tell everyone without a particular processor that they can't use your software unless they upgrade your system, so you go with the lowest common denominator, which is x86 (Remember those 386 machines? Running DOS? Yeah, I didn't think so. That's how old this technology is.), or you stipulate a set of system requirements for a more recent processor (The Pentium II is common nowadays), but you can't use the latest hardware enhancements, because you want your product to be useable for "most people" on their current system. You see, this is even better than having my operating system and most of my programs compiled for my "generation" of processors. They will be optimized to take advantage of features and optimizations unique to my specific processor (and even system configuration). Then he got an idea! An aweful idea! THE GEEK GOT A WONDERFUL, AWEFUL IDEA! "I know just what I'll do!" The Geek laughed in his throat. And he made a quick download, and boot disc he wrote. And he chuckled and chuckled, "What a great Geeky trick! With this chip and this board, my system'll be slick!" My plan, naturally, is to buy an AMD64 processor and build a system, piece by piece, around it. I'll need a motherboard, video card, memory, and a case, as well as all the other usual stuff. I also plan on getting a TV tuner and running MythTV. My goal is to configure it to run MythTV on my projector as a second monitor, while using my CRT as a primary monitor. That's why the keyboard I got is wireless, with an integrated pointing device (ideally suited for sitting on a couch, not at a desk). This is all subject to change, but I've already ordered a keyboard, so I'm pretty much committed. Lately I've been running lots of Open Source software on my laptop (Firefox, Gaim, Azurus, Vim, OOo, GIMP), and it's partially because of this that I've had enough faith in the quality of Linux to do this.

---

⁰ I recently paid a visit to my company's surplus outlet, of which I was previously unaware. If anyone wants a used 15" - 19" CRT (non-flat) for about $10, let me know. The flat-screens are $50. Actually, it's open to the public, but as an employee I get a discount. ¹ If you're wondering what Linux is, it's an operating system. "Umm..., what exactly is that?" you were probably going to ask. Windows XP is an operating system. You may have heard of OSX, which is an operating system that runs on Macs. Linux is just another way to run a computer. If you don't know all about it, it's because you're probably not geeky enough. ² In case you're wondering what it looks like (or rather, a few of the ways it can look), here are some screen shots.