Okay, I've been falling a bit behind here. That's a bit representative of other portions of my life as well ;-)

Star Wars was enjoyable, regardless of what anyone else says. As was Star Wars Risk, though that was far different from any other Risk game I've played.

Nate, Spartacus, Lon, and I enjoyed a game of standard Risk a week or two ago. We're looking forward to playing a game of Civilization sometime soon.

The CPLUG Server is going to lose it's home at the end of the month. The new server we've been building is nearing completion. I've setup most of the services that belong on here. The biggest things left are the mailing list migration, and the CPLUG website. I'll handle the cplug mailing list this weekend (hpm is already done), the CPLUG website has to be done by Andy. And if it's not completed soon, we'll switch to a wiki until it is ;-) (we have a wiki working for the HPM website, and figured out how we could use the existing CPLUG website template in a wiki)

The MythTV box I have at home keeps going haywire. It runs out of space, and that seems to be causing the filesystem to go corrupt. Odd. The drive was only 40GB though, so we bought a larger drive. 300Gb ought to do it (it was only $128!). Hopefully I'll get that setup this weekend.

The Arts Festival is this weekend. This is always fun, we'll probably head over there on Saturday.

Most of the cd's I've ordered have arrived. They're all great, it's been good having some new tunes at work.

Yeah, I'm a bit torn as well as to why that happened.

I had filesystems in the past fill up with no problems at all (aside from the expected "no space left on filesystem" errors). It's even happened at work a few too many times.

However, on the Myth box, the filesystem has gone corrupted twice. Each immediatly after it filled up.

There might be something different here though. Usually, when the FS fills, there's only minimal attempts to write more data. On Myth, it fills when a show is recording. The mpeg's Myth creates are about 2.2GB for an hour, which translates into roughly half a MB a second if my math is correct.

After it filled, it probably went several hours each time before I noticed -- all the while Myth was trying to store half a MB each second. Perhaps the rate at which it continued to attempt to perform writes was part of the issue.

I would actually love to do something like that, it would solve many problems.

Alas, there's one outstanding issue that seems as if it may prevent that.... I'm not sure I have enough bandwidth going to the MythTV box in order to pull that off. It only has an 802.11b connection.

It's a long term goal to get that area wired, but that's going to be a bit tricky.

Let me know if you feel otherwise though :-)