• Welcome to Valhalla Legends Archive.
 

Why Windows crashes, and Linux doesn't

Started by Mephisto, December 14, 2003, 09:02 PM

Previous topic - Next topic

Grok

Well since Adron's absolutely right, there's no need to reply.

iago

Quote from: Grok on December 23, 2003, 10:17 PM
Well since Adron's absolutely right, there's no need to reply.

Yet you still felt the need to reply.  Odd!
This'll make an interesting test for broken AV:
QuoteX5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*


Grok

Quote from: iago on December 23, 2003, 10:31 PM
Quote from: Grok on December 23, 2003, 10:17 PM
Well since Adron's absolutely right, there's no need to reply.

Yet you still felt the need to reply.  Odd!


.... to the issue.

Forged

Quote from: Mephisto on December 14, 2003, 09:02 PM
My friend and I had come up with an idea that perhaps the reason why Windows crashes more than Linux is that it runs off one file, Explorer.exe.  So when Explorer gets mad and has some complications, your whole computer does and results in a crash.  Because Linux runs off of several files, when one gets complications, your whole program doesn't end up crashing as Windows would.  Also, this could be why Linux gets better uptimes because it doesn't rely on just one file like Windows does.  Windows may just go off of one file since they want to keep their source closed, and managing one file is just easier than multiple.  Maybe Linux runs faster because it has multiple files handling data and processing it.   My friend and I don't really have a lot of evidence backing up this theory, and we're not 100% sure if Linux even does run off of multiple files, but if it's true, perhaps this why?  Dunno... what do you guys think?

Linux mainlly runs of one kernell. Microsoft runs off of hundreds of .dll files.  If one of the many needed windows files becomes corrupt or experinces an error, it crashes.  It requires a major fuck up to crash the single kernell. Kinda had it backwards on both accounts.
QuoteI wish my grass was Goth so it would cut itself

iago

kernel*

Linux also has .dll equivolants!  
This'll make an interesting test for broken AV:
QuoteX5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*


Banana fanna fo fanna

Quote from: Forged on December 23, 2003, 11:00 PM
Quote from: Mephisto on December 14, 2003, 09:02 PM
My friend and I had come up with an idea that perhaps the reason why Windows crashes more than Linux is that it runs off one file, Explorer.exe.  So when Explorer gets mad and has some complications, your whole computer does and results in a crash.  Because Linux runs off of several files, when one gets complications, your whole program doesn't end up crashing as Windows would.  Also, this could be why Linux gets better uptimes because it doesn't rely on just one file like Windows does.  Windows may just go off of one file since they want to keep their source closed, and managing one file is just easier than multiple.  Maybe Linux runs faster because it has multiple files handling data and processing it.   My friend and I don't really have a lot of evidence backing up this theory, and we're not 100% sure if Linux even does run off of multiple files, but if it's true, perhaps this why?  Dunno... what do you guys think?

Linux mainlly runs of one kernell. Microsoft runs off of hundreds of .dll files.  If one of the many needed windows files becomes corrupt or experinces an error, it crashes.  It requires a major fuck up to crash the single kernell. Kinda had it backwards on both accounts.

Ugh, no.

Raven

Quote from: Forged on December 23, 2003, 11:00 PM

If one of the many needed windows files becomes corrupt or experinces an error, it crashes.  

Not true. Only if one of the crucial files (there aren't THAT many of them) is corrupt, it'll malfunction, but you'll still often be told that File %s is corrupt, go fix it plz. That is also the case with many other DLL files, in which the OS will function normally until the specific file is invoked, in which case once again, it'll tell you it's malfunctioning and you should go fix it.

As a bit of an addon to a previous statement, Explorer.exe is NOT a necessary file. You can endtask it, and Windows will still run normally, except that you will mostly lose the GUI desktop. However, you can still manually start processes. I sometimes do that if I want a particular operation running as smoothly as possible because Explorer is a resourcehog. ;)

Banana fanna fo fanna

Let's either let this drop, or make it funny. Don't answer intelligently, please.

Newby

"Don't answer intelligently, please."

i read in a linux form that all inwdows r bakcdroooerd the admin said so and somebody said no and he banned him therefore they really r bkcdoored omfg i </3 microsoft now

Hows that?
- Newby

Quote[17:32:45] * xar sets mode: -oooooooooo algorithm ban chris cipher newby stdio TehUser tnarongi|away vursed warz
[17:32:54] * xar sets mode: +o newby
[17:32:58] <xar> new rule
[17:33:02] <xar> me and newby rule all

Quote<TehUser> Man, I can't get Xorg to work properly.  This sucks.
<torque> you should probably kill yourself
<TehUser> I think I will.  Thanks, torque.