Linux crashed!

More humour from the anonymous person who would have a new linux destory all the data on their hard drive because they asked how to back it up.

Regards,

Those OS's can crash just like any other. In fact, at one company I worked at, they had to IPL every night because of a memory leak in the latest patch of the OS. Took IBM 6 months to figure it out.

MVS can crash, it's just that IBM knows its hardware quite well and is able to, in most cases, deal with any quirks. The systems are designed for hot swappable upgrades. This is mostly the result of heavy redundancy in the hardware, not the OS (though the OS has to support it of course).

Anyone that claims any particular piece of software can't crash is the fool. Hell, things like cosmic rays can cause random glitches which can cause software to crash, and hardware failures, and just plain bugs.

It may be *UNLIKELY* that something will crash, but it's not impossible.

<CRAP!>

Notice how the cyber nitwit posts 90 messages to this bulletin, none of which request links, facts or anything of substance.....

Your brain has crashed into your ass Erik.

But it didnt crash.

No, it cant. Apparantly youve never actually worked with it.

Do you even understand the hardware that MVS runs on?

And it never crashes.

Please, do continue to talk out of your ass on topics of which you have absolutely no understanding at all.

Yes, it did crash. That's how we learned we had to IPL every night. It crashed quite a bit until IBM suggested we an IPL process to our nightly processing.

I see.

What's your point?

Ahh yes. That's why this article is entitled 'Why Mainframes *RARELY* Crash' instead of 'Why Mainframes *NEVER* Crash' http://os390-mvs.hypermart.net/mvscrash.htm

That's why it says 'These systems, like PCs, do fail,'

Even IBM doesn't claim that it can't crash. So why should anyone believe your assertions when even IBM doesn't claim that.

Aw Charlie......I can't believe you're now saying the same things MS users tell their users when they can't explain a problem.

No, it isn't guaranteed that this problem is a Hardware Problem. I've encountered the same problem dr. square is complaining about now. It is known as running beta software that has a bad memory leak...in my case that was an old version of Pan. When your machine's stack gets corrupted, you most certainly can get an error that will stop the processor and leave you with a totally locked up machine (and no, that isn't a segfault that occurs because a program/data pointer has gone awry). The good news is that it is very easy to find the stack problem (if any) with Open Source programs if you're motivated enough. With closed source programs (like MS) you don't get a real answer, just a coverup so you don't blame them.

Forty lashes to you for explaining away an unknown problem as a 'Hardware

No, it didnt crash.

Then you havent. Do halt this end of the argument in that case.

My point is that if you even understood the basics of the sort of big iron MVS runs on, you would understand how even a power outage would not cause the OS to crash. Half the system could be on fire, and the OS would not crash.

I'm not talking about mainframes, specifically.

Because I am not generally proven wrong on topics discussed in COLA, and you very often are.

You just dont respond to those.