Dont forget virtual memory also allows process isolation (aka protected mode) to happen. In 32-bit environment, each process gets its own copy of 2GB of virtual memory or 3GB if they are compiled with/3GB flag.
x86 system are designed in this way so they could not corrupt each other accidentally. In practice, you can have any program crashing as often as it wants, without bring down the entire system.
Also, when they say "Windows reserves 2/3GB of memory for user mode process" or "Windows reserves 1GB of memory for kernel space", it means that is the absolute upper limit for memory usage. You should read it as "each process cannot allocate more than the 2/3GB limit, trying to do so will result in 'Out of Memory' exception", rather than "That process exclusively own the 2/3GB, nobody else can use it".
Sounds like a bad idea to me. I have never used a Mac before, but this is a no no in Windows.
It might makes sense that more layer of AV means more security, unfortunately in practice things doesn't work that way.
AV works by installing hooks in OS itself to monitor system activities. (eg. open a file) Having multiple AV means different AV might interfere each other. In the end, you might end up with unstable system instead of more security.
Slashdot Mirror
I tried that and it works. Unfortunately now I miss my favorite past time of skimming through log files for amusing failed username and passwords...
From TFA, Native Client is abbreviated as NaCl aka table salt?
Dont forget virtual memory also allows process isolation (aka protected mode) to happen. In 32-bit environment, each process gets its own copy of 2GB of virtual memory or 3GB if they are compiled with /3GB flag.
x86 system are designed in this way so they could not corrupt each other accidentally. In practice, you can have any program crashing as often as it wants, without bring down the entire system.
Also, when they say "Windows reserves 2/3GB of memory for user mode process" or "Windows reserves 1GB of memory for kernel space", it means that is the absolute upper limit for memory usage. You should read it as "each process cannot allocate more than the 2/3GB limit, trying to do so will result in 'Out of Memory' exception", rather than "That process exclusively own the 2/3GB, nobody else can use it".
Mark has a good explanation about this. http://blogs.technet.com/markrussinovich/archive/2008/11/17/3155406.aspx
Time to get a new wife
Sounds like a bad idea to me. I have never used a Mac before, but this is a no no in Windows.
It might makes sense that more layer of AV means more security, unfortunately in practice things doesn't work that way.
AV works by installing hooks in OS itself to monitor system activities. (eg. open a file) Having multiple AV means different AV might interfere each other. In the end, you might end up with unstable system instead of more security.
Next time we have to reference amounts of data sorted as n Google Sort.
If human can have souls, so shall we
Compile once, exploit everywhere.
Am I the only one who misread "Turn Table" as the round disk with rhythms?