Δαφνη Ευτυχια Αρθουρος

Seriously pushed my body too hard at the start of the week. Trying to recover from that now. Was able to help with packing and such on Monday, then for half as long on Tuesday, and spent much of Wednesday resting or working on the computer. By Wednesday I was having difficulty walking and standing upright -- I'd start to feel okay, and get fatigued after 20-30 minutes of activity, so I spent a lot of the day in bed, trying to sleep. (Had trouble staying asleep more than an hour at a time.)

The moving van left yesterday, and after a bit of cleaning Ruth decided she didn't want to sleep on the floor in a dusty house; she'd earned a break. (I'm not the only one with allergy problems over there...) So we checked into a nearby hotel. She went back to the house early this morning and I'm still in the hotel room. Going to alternate between resting and doing work-I-get-paid-for on Ruth's laptop, and try to get back to being healthy enough to be useful again. Enough to survive the drive to West Virginia, at least; enough to help clean the house and load plants and animals into the rental truck ideally. No idea how the schedule goes today -- we're all imrovising.

Discovered I screwed up: before I left I tried to set up my Windows machines RuPaul and BoyGeorge, running 95 and NT respectively) at home to let me access them using VNC, but they were both being cranky and I ran out of time to do that. Figured the room they're in would get Way Hot during the week anyhow, and I only needed access to files, not tools, so I shut them down. Turns out I want a file off the D: drive of the NT box. Whoops. Just about everything else gets stored on the file server ... I did manage to recreate what I needed from that, but now I realize I need a tool on that machine, which I'd need VNC running in order to access it. (For just a file, I could Samba in from any of the Linux boxes I left running.) So if I do finish most of the thing I'm working on right now, my boss'll still have to wait until I get home before I can package it up for delivery.

Dunno why VNC didn't want to work. Before my trip to Toronto the winter before last, I had both Windows boxen running VNC and I set up port forwarding on Eon to let me into them from outside my LAN, and I was able to use them (with a bit of mouse latency) from Far Away with very few problems. (I did have to ask my landlord to drop by and reboot a machine during that trip.)

Also getting some strange network problems. Earlier I could log into my ISP from Ruth's laptop, but now I can't. But I can still telnet to it from my home machines. And I can't access all my home machines from each other: I can see the file server (ping/telnet/nfs) from my main shell machine, but I can't see it at all from my gateway. So I have to telnet to Eon, the gateway (the only exposed machine, since it's running masquerading (NAT)), then telnet from there to Tipton, the main "user" machine, and telnet from Tipton to Richards (the server) when I need to get into it, because I can't get from Eon to Richards. StJoan (the firewall) sees the box that Richards is running virtually on (using chroot -- long story involving motherboard failures and difficulty getting particular OS versions to boot on particular hardware; that wound up being the quickest way to get running again and I haven't gotten around to fixing it right in the past few months) but doesn't see Richards as Richards.

Hmm. I wonder what else is going on in my living room. Wood, the name server, must be working okay, because DNS seems to be working right. And if Cornbury (BSD machine, also syslog collector) crashes it won't affect my ability to get things done. I do feel a little handicapped not being able to touch my Windows machines though. I can deal with being completely disconnected, such as at Pennsic where I'm not trying to work, but if I need any of my tools I feel uncomfortable not having all my tools. *shrug*