IP address not resolving
There was a storm in Washington while wrog was in New Jersey, and the UPS did not bring everything back up. This, combined with some other misconfiguration of the secondary DNS server, is causing lambda.moo.mud.org to not resolve.
Until such time as wrog returns to Washington to fix the problem, you can use the IP address, which is 209.181.94.35.
Sorry for the inconvenience.
Update (5:20pm — wrog): My nameserver is back, but until Rob fixes his, nobody will be able to find it. In the meantime, if you badly want a name rather than a number, try lambdamoo.fyigm.com.
Update (6:16pm — wrog): Rob's wasn't actually broken. Note to self (and also anyone else out there who uses openwrt and the overlaid squashfs+something filesystems that they use):
Until such time as wrog returns to Washington to fix the problem, you can use the IP address, which is 209.181.94.35.
Sorry for the inconvenience.
Update (5:20pm — wrog): My nameserver is back, but until Rob fixes his, nobody will be able to find it. In the meantime, if you badly want a name rather than a number, try lambdamoo.fyigm.com.
Update (6:16pm — wrog): Rob's wasn't actually broken. Note to self (and also anyone else out there who uses openwrt and the overlaid squashfs+something filesystems that they use):
- Never edit anything in the /overlay directory; this does not do what you'd think. Not that I was actually intending to edit anything there. Which then leads to:
- Never keep emacs buffers open on the /overlay directory, or if you're prone to doing this (say because it's a convenient window on the List of Things That You've Changed from the Standard Distribution) then you might want to consider using uniquify.el. (of course this is probably all moot since I seem to be one of the 5 people left on the planet who still uses Emacs, but anyway...)