Here are a couple of screenshots, to serve as conversation points. One belongs to me, and one doesn’t.
On the left is one that pete.t sent, and if you look close, you can see a clever splicing of both dvtm and dvm at work. Using one multiplexer shouldn’t discourage you from nesting another within it, sort of like I mentioned a while back with screen.
pete.t said that machine is an Athlon XP 1500 with a lowly GeForce4 video card, but it doesn’t seem the least bothered by the workload … if htop is any indicator. I can vouch for the video card, by the way: I believe used to have a mobile version, and it was no sluggard.
The host (and by host, I mean it in the host-and-parasite sense) is that less-than-spectacular K6-2 I brought home a few weeks ago. I’ve been tinkering with it off and on, and debating its future.
Technically, it’s a has-been. It has a number of quirky points which make it ripe for disassembly, and yet on the other hand, it’s still gameworthy.
I could list all its faults, but if this little adventure pans out like I want, I might have something to show off. I’ll save the details for later.
As it stands, the machine is running Debian 6.0, with only conky, xplanet and openbox on board. Given the siliconmotion driver’s general and ongoing state of disrepair, that’s about all it can handle.
The goal here is to get the machine to boot straight to X, download and render the weather maps at regular intervals, hide the mouse cursor, and — if I feel overly ambitious — cut power to the backlight at night and restore it in the morning.
If I can get everything working how I like, I’ll literally tear away all the components that don’t work (like the keyboard) and move on to the second step: mounting it on the wall.
But that’s a little bit into the future. And I have a couple of issues to solve before then … like how in the heck I can do a factory reset on my wireless router, after accidentally setting it to serve as an access point. That’s a whole different story though. …