Noob comment seconded

Wonder if that'll mess with legacy NCR WaveLAN 915 MHz point to point network hauls?

I found them late in life, maybe in 2016 or so. It literally took my breath away the first time I walked in - it was like everything Radio Shack wanted to be in the 70s through the 90s, and more, and it felt even more so at the time, since Radio Shack was gone by then. I hadn't seen so many semiconductors and such in one place in... ever. Unfortunately every visit afterward underwhelmed me a little more. Kind of a shame, but they couldn't roll with the market and it got them in the end. RIP

I was debating using IS-IS as our routing protocol here at work, but wound up for more than one reason going with OSPF. For years it was pounded into us that Cisco's implementation of IS-IS was done better than Cisco's implementation of OSPF - I hear that's a non-issue these days. It was pretty plain that I'd have an uphill battle implementing something with a name like that without a really good reason.

I hear he retired to Patagonia and is living like a king.

A station wagon (with rear-facing seats, no less) full of ferromagnetic tapes perpetually circling the Library of Congress.

In the immortal words of Mr. Knight: "Telstar! Wow! Isn't that the satellite that's raining debris all over Europe?"

I saw our WinNT PDC crash when I mistakenly telnetted to it over port 53. Aside from that, it was pretty solid for me too.

If you really want to find that story, try Abebooks Booksleuth. They are amazing at finding stories with the barest amount of information.
http://forums.abebooks.com/abesleuthcom

IIRC, my first computer lab had: a handful of Apple II's, an Apple IIe (with Winchester drive), a handful of Commodore C64's, a few TRS-80 model 3, and 2 Osbornes. I loved the Apple IIe most of out of all of that mess. This would have been mid- to late-1983. I still vastly preferred sneaking over to the library to the teletype machine and playing Star Trek on the school board's mainframe when no one else was signed up.

Any sufficiently advanced technical description is indistinguishable from a line of dialog from a Star Trek episode.

Thank you for the feedback! I did indeed post that second post from my IOS device.

Well I know _someoneâ(TM)s_ gonna have to replace them. I donâ(TM)t imagine Fortinet will buy us new E-series boxes, but maybe Iâ(TM)ll be pleasantly surprised.
Just to clarify, the zdnet article says 6.0.7 fixes the issue, but the official fortinet site says 6.0.7 is vulnerable. https://fortiguard.com/psirt/FG-IR-18-100

I opened a priority ticket with them to verify, and the older hardware is not supported. The latest info from support is that FortiOS version 6.0.7 _is_ affected, and that older hw like the 200D is not patchable, since the 6.2.x train which fixes the problem is not available for that platform. I think this will be a painful experience by the time it's over, both for Fortinet and customers. Still hoping they come back and say that there is a 6.0.8 or something specifically to address this issue with slightly older platforms.

The missing component is magic. Proton didn't have a west pole, but Phaze did.