I’m going to be gone for the next week and a half (including some time at the ISDC) and am packing tonight and flying tomorrow (the next week will be in central Missouri). I’ll be doing the “have laptop, will travel” gig, though, because this is a working vacation, so I won’t be totally absent, but I’m unlikely to post much for the next day or so.
[Thursday morning update]
Travel went fine yesterday, but I didn’t get out the laptop until this morning. More posts anon.
I’ve gotten pretty tired of his continual distraction and obfuscation, and low S/N ratio.
How does the rest of the community here feel? I haven’t banned many commenters (I think they can be counted on one hand). What say you?
I’ve been using sshfs to do remote editing on my web server. I create a directory with the server name as a mount point, owned by me in my home directory. I then mount with
$ sshfs -p <portnumber> <servername>: <mountpoint>
I also have the keys set up so it does so without a password prompt. It seems to work, but I only have read-only access — when I try to write a file it tells me that I don’t have permission. Also, I notice that when the file system is mounted, I get an owner and group of “1009” for the mount point. Is this normal? Does anyone have any idea what’s going on?
[Tuesday morning update]
D’oh! I just noticed that my line command wasn’t displaying properly before. It’s fixed now.
…to all you mothers out there.
I may not have time to deal with it before the weekend. But if there’s a stylesheet doctor in the house, help would be appreciated.
Some readers may recall that my W2K machine died a couple months ago after an update (actually, it’s been over three months now). Well, a few days ago I finally found my install disk. Unfortunately, when I tried to use it to repair, it said it couldn’t find a Windows installation, so apparently the drive really got munged. I know all the data is there, because I mounted the drive on a Linux box and pulled it off, so I’m guessing that the boot sector is screwed up. Unfortunately, it’s a complicated situation, because it was actually set up to boot from Drive D (Drive C was a legacy 98 system, and both drives are partitions on a single drive). And of course, I don’t have a rescue disk, that I know of, for the current configuration.
So is it possible to go in and look at the boot sector in another machine and repair it manually? Anyone have any suggestions?
We’re going up to Michigan tonight for the weekend, for my nephew’s first communion. I may not even take a computer with me. Be back Monday afternoon.
[Friday night update]
We arrived safely, but things have been kind of hectic, including doing some nice handgun shooting practice in a gravel pit west of Ann Arbor this afternoon (0.22 long and short barrel, 0.380 and 44 Magnum). Visited with family late afternoon/evening, and more such festivities tomorrow and Sunday.
Be nice in comments. Don’t make me come in there…
I just tried logging into one of my sites that I’ve password protected, and I stupidly used the wrong password multiple times. Now when I go to the site, I don’t get a username/password box. Instead, I just get a 403 error. Does the server somehow keep track of failed logins from a given IP and block it? If so, how do I fix it?
[Update a few minutes later]
OK, more clues. When I attempt to log in from my laptop, I get a username/password box, but when I correctly type in username/password, I get the same 403 error. This tells me there’s something going on with the server. Right?
One other bit of info. I can log in to other sites that use the same username/password, just not this one. Is it an Apache issue? If so, I’ll have to talk to support at my host. I don’t understand that, though, because it’s just for this one directory. It seems like a .htaccess problem, but I didn’t know that it would block an IP after a failed attempt, and I can’t find any info about how to unblock it.
[Wednesday morning update]
Well, it let me in this morning, so it must have had a time limit on the lock.
I’m actually working on this trip — in Torrance this morning, have to drive down to Seal Beach for lunch with an old Rockwell (now Boeing) colleague, then back up to El Segundo for a two o’clock meeting, then to Burbank this evening for Whittle’s half-century birthday. He didn’t look a day over forty-nine to me last night.
Then an early morning flight back to Florida in the morning, so probably not much new until Thursday. For those who read the New York Times, though, I may have some thoughts on North Korea there this afternoon. With a bonus picture.
I’m driving back to LA this morning (arriving afternoon). Obviously no posting till this evening.