Re^2: The worst case scenario

Last I knew (I've not been keeping close track; "last I knew" is a couple of years old), hotmail still had numerous BSD boxes. M$ was finding these highly non-trivial to completely eliminate. An interviewed sysadmin said everytime they replaced one with a Windows box, another BSD box was installed elsewhere. I think he used an analogy to cockroaches, but I may be wrong.

emc

"Being forced to write comments actually improves code, because it is easier to fix a crock than to explain it. "
—G. Steele

Comment on Re^2: The worst case scenario

Replies are listed 'Best First'.
Re^3: The worst case scenario by samizdat (Vicar) on May 17, 2006 at 19:36 UTC
I had heard that, too, but the last word I'd heard (again, a while back) was that Management (!) was insistent upon eliminating BSD, no matter how many (hundreds of) boxen they had to add. <SHAMELESS PLUG> Here, our whole division's DNS and routing trees, and quite a few of our heavy load servers, are now happily FreeBSD. Every time the NT-oriented senior folks have a "moment", they task a junior admin with the problem and he solves it with FreeBSD. Our CAD systems admin would love to replace the RHL-E3 boxen that are used for EDA chip-simulation runs with FreeBSD, but he keeps running into places where the apps are Linux-specific, such as expecting a non-standard xterm. For the tools for which they do work, they're both faster and much more load-tolerant than the RH machines. </SHAMELESS PLUG> We SHALL overcome! :D Don Wilde "There's more than one level to any answer."	[reply]
Re^4: The worst case scenario by BerntB (Deacon) on May 20, 2006 at 23:30 UTC
Oh, OK. I shall, at long last, d/l and try it. Have been thinking about it for years and now I have free disk. (Last BSD for me, was SunOS, pre Solaris 2... :-)	[reply]


Perl: the Markov chain saw
	PerlMonks