I have many memories of Slashdot, some good, and some bad.

9/11
That Jon Katz asshat
Natalie Portman, and hot grits.

But I never visit any more.

Jr'er ab fgenatref gb ybir Lbh xabj gur ehyrf naq fb qb V N shyy pbzzvgzrag'f jung V'z guvaxvat bs Lbh jbhyqa'g trg guvf sebz nal bgure thl V whfg jnaan gryy lbh ubj V'z srryvat Tbggn znxr lbh haqrefgnaq Arire tbaan tvir lbh hc Arire tbaan yrg lbh qbja Arire tbaan eha nebhaq naq qrfreg lbh Arire tbaan znxr lbh pel Arire tbaan fnl tbbqolr Arire tbaan gryy n yvr naq uheg lbh.

Yes.

Yes. No.

When I was working for NASA, on the NISN network, we'd get these weird router crashes for the old Cisco router located at (or very near) the South Pole in Antarctica. It was always a memory problem, and I'd always have to call someone to get them to powercycle the router. It irritated me to keep bothering those guys, so I opened a case with Cisco TAC.

The TAC guy sent a terse response, saying that particular crash was a "transient memory error" due to "alpha radiation or sun spots." That really pissed me off -- Cisco TAC just gave me a standard BOFH response! I escalated, and swung the NASA club around some, and finally got a senior engineer on the phone. "You said this router's at the South Pole, right? So that means it's at very high altitude, with very little ozone shielding, right?" "Umm, yeah." "Well there you go. There's a lot more radiation at that altitude than at sea level. Our stuff's only rated for sea level. See if they can .. I dunno, put a lead blanket over it or something."

I relayed the info to my contact at McMurdo, and he laughed and said he'd figure something out.

On a hunch, I checked the other two "high-altitude" routers we had, and sure enough, they both had a statistically higher failure rate for "transient memory errors".

You don't need the whole Cygwin beast for this. Get the small compiled rsync binary from the BackupPC folks: http://sourceforge.net/projects/backuppc/files/ (scroll down, and look for 'cygwin-rsync'.

FYI BackupPC is pretty nice, itself.

In 1995, my pal Robert (or was it Jeff?) downloaded a Slackware distro -- via slow modem, onto floppies. It took about a week.

We all passed the floppy set around, installing Linux onto our computers. By February of 1996, id had released the Quake demo. I had Win95 on my old craptastic Packard Bell, but it simply wouldn't run Quake. I spent hours trying to get the SVGALib Quake to run. I distinctly recall nuking my system in an effort to get X running, and somehow typing (as root) "rm -rf / usr/local/lib". See that extra space? Yeah, that was fun.

I got a new computer, but couldn't get Win95 to run, so I switched to OS2/Warp. It wouldn't boot at all. Linux would run, but would crash a lot. I finally discovered that the scumbags who sold me the computer had swapped the new 486 Intel chip for a much older and slower Cyrix chip, and overclocked the hell out of it so that it'd show the appropriate Mhz at boot.

I finally switched that POS out for a new computer, and ran dual-boot Linux and Win95 for several more years. Today I use Macs, but they're mainly pretty window dressing for terminal sessions on Linux machines.