@kdfrawg The most painful was running a USENET feed off a NT4 Server box. It's as if the Compaq Proliant was screaming, "Killllll Meeeeee". Just like that scene in "The Fly"

//

@kdfrawg I keep this around for a reason. Whenever someone has a dumb idea that sounds great in theory, I point at it and the discussion ends.
//

IMG_0207.JPG

@kdfrawg Ugly and dated UI but I miss the stability. First Winows I could run for an entire week without having to restart.

NT 4 server was a different matter.

We ran a ISP with it. Lost count of the times I had to go to the office in the middle of the night and cold-boot the stupid thing from the memory leaks.

//

It's doable if you fight with XDM long enough.

We had a "We're going to try thin clients across a network" edict many years ago that ended with..

"You got your wish. There it is. Now, can we throw this crap out and file the whole debacle away as a brainfart?"

"Yes", was the answer.

// @kdfrawg

It's a shame there isn't a telecommuting option of some sort.

// @kdfrawg

FreeBSD is probably the better supported, hardware-wise, of the two.

Takes too much futzing around to make it into a desktop though. At least, that's the way I feel about it. They have a Desktop-specific re-spin but I've not tried it.

// @kdfrawg

Dave Mustaine was never what you would call a gifted singer.

Age is not doing him any favors in this regard.

Hate to say that, but, there we are.

@kdfrawg There are certain headless server tasks I need a dirt simple and reliable *nix for. BSD has filled that role nicely.

For my personal stuff, I was in the "couldn;t care less about it anymore" camp.

I'm starting to reconsider my stance after recent events.

//

@kdfrawg It doesn't pay to render it to a company that has already made up it's mind and is only asking for sake of appearances.

@kdfrawg I think the BSDs is about as close as you're going to get.

//