In some cases, nothing. However, stupid kernel/libc bugs aside, if a user isn't running as root, the user can't infect the entire system. For home users, this is great, because they can set up one user account for web browsing and other dangerous stuff, and another user account for stuff like onlike banking, OpenPGP signing, etc.
I don't have any concrete examples, but I can recall many times when I've been annoyed by the random things IE does that are most definitely not up to standard.
I think what Gates means to say is that these problems are the result of attackers running third-party software. No Microsoft software is capable of mounting these attacks.
The two didn't play nice together, and as a result, the interface had to be reset the instant more than one program tried to access the network.
Assuming that's actually what was happening, it probably wasn't a problem with the hardware - it was broken drivers that didn't do locking where they should have. "Processes" are abstractions that are not visible at the hardware level.
There's another thing that might have happened: You might have had the (IIRC) 8390.o kernel driver loaded. At a company I used to work for, we had a Debian machine that kept getting really sluggish and crashing for no apparent reason. It turned out that the 8390 driver - which was a PCMCIA driver - was loaded, even though we had no PCMCIA hardware in the machine. Removing the driver from/etc/modules fixed the problem.
[For those of you who are wondering why the driver was listed in/etc/modules in the first place, it's because the Debian boot-floppies never used to have automatic hardware detection, so it presented the user with a list of drivers which could be loaded. We weren't entirely sure of what drivers we needed to load for our hardware, so we just tried installing various kernel modules until we got ones that loaded successfully. Thankfully, the new Debian installer is much smarter.]
Slashdot Mirror
Wrong! Some of us live in Mom's attic...
Because it's a compatibility layer that can be removed if you don't need it, which probably saves power, battery life, stability, etc?
In some cases, nothing. However, stupid kernel/libc bugs aside, if a user isn't running as root, the user can't infect the entire system. For home users, this is great, because they can set up one user account for web browsing and other dangerous stuff, and another user account for stuff like onlike banking, OpenPGP signing, etc.
BitTorrent isn't anonymous...
Volkswagen
Concrete examples are available at: Position is Everything
Both slants? WTF? How is this +5, Insightful?
What do you get if you multiply six by nine?
LANG=C doesn't work for me. I usually need LC_ALL=C.
But were they 5% of 1990 levels?
It's still there...
You mean statically-linked. "Hard-linked" means something else entirely.
Ever used Visual Studio lately?
Your parents do, if you're underage.
Anyway, subdermal tags are no match for an MRI... :-)
I think what Gates means to say is that these problems are the result of attackers running third-party software. No Microsoft software is capable of mounting these attacks.
... before people's fears make it illegal. When nothing bad comes from human cloning, people will hopefully quit being so fearful.
Have you looked at about:config?
What's better is to disable remote password authentication entirely, if you can.
Assuming that's actually what was happening, it probably wasn't a problem with the hardware - it was broken drivers that didn't do locking where they should have. "Processes" are abstractions that are not visible at the hardware level.
There's another thing that might have happened: You might have had the (IIRC) 8390.o kernel driver loaded. At a company I used to work for, we had a Debian machine that kept getting really sluggish and crashing for no apparent reason. It turned out that the 8390 driver - which was a PCMCIA driver - was loaded, even though we had no PCMCIA hardware in the machine. Removing the driver from /etc/modules fixed the problem.
[For those of you who are wondering why the driver was listed in /etc/modules in the first place, it's because the Debian boot-floppies never used to have automatic hardware detection, so it presented the user with a list of drivers which could be loaded. We weren't entirely sure of what drivers we needed to load for our hardware, so we just tried installing various kernel modules until we got ones that loaded successfully. Thankfully, the new Debian installer is much smarter.]
Cat got your tongue? (something important seems to be missing from your comment ... like the body or the subject!)
IPSEC is secure? See this.
I fail to see the controversy. These "notices" are spam. There is no question about it.
Yeah! And if you want oil, pump it up from your own soil!
Well, maybe you might hear something if you really had a wind power plant in your back yard (i.e. *literally* in your back yard)?