I believe read only segments are for the VM so that it can get a page fault when there is an access and know what parts of memory have been used recently.
"Mild spoiler: It features a giant flying rock head that vomits guns on barbarians. I am not making this up. Giant flying head made of stone, guns are projected from its mouth..."
OK, after reading that spoiler I laughed so hard I just have to see this movie! It's a comedy right?
"and the shitty OS that allowed itself to be infected"
OK, come on I'm as much a FLOSS (ie, "Linux") advocate as anyone else, but what happens when it changes from.vbs and.bat to.sh and.csh scripts in the emails? Sure, at least it will only affect the single user if they're not running as root, but FLOSS is susceptable to attact at the human level also.
Oh, you say the script doesn't have the executable bit, but look at mozilla and thunderbird. For a while they made you save your attachments before opening them. And there was a large percentage of the user base that wanted "double click on attachement opens file" functionality.
Move people to a FLOSS OS like Linux or BSD, and you'll get the same pressures.
"You probably thought of slapping the powerplant example right in my face, where critical systems can become compromised, and can become a real life threatening danger to people, and that's very, very seriously bad. But you know that those systems should be protected well enough so that such things simply can't go wrong when that magnitude of risk is involved. They build airplane- and bomb- proof cages around nuclear reactors for a reason. Why is it so strange to ask for similar stringent approaches when software is involved? The real fuckwit is not the killer, it is the one that doesn't care enough and so allows the catastrophe to happen."
Those protections wouldn't be around the power plants unless there was some risk of people trying to exploit the explosiveness of the power plant. If there weren't crazy people thretening the power plant, or the cold war those protections simply would not be there.
The funny thing is that it's the same people who complain about the military budget and costs of those things to *protect* people that say we need these other protections in the same logical direction (thick cages to protect against bomb and airplane attack).
andr0meda hasn't come out saying that virus writers shouldn't be punished, just that they serve a purpose. I say that you'd lose a lot of virus writers if doing that didn't have punishment. They wouldn't be l33t anymore, but you'd get overwhelmed with the others that don't care about leetness and get even more people than when it was banned.
Anyway, you have an entire industry supported by virus writers. Antivirus, just like you have an entire industry supported by crooks and robers, the police. The larger effect from virus writers isn't going to be larger penetration of OSS anti-virus and anti-spam, it's going to be more freedoms lost because the majority of people don't understand how computers work and will ask for laws to protect them, and their IT people who are telling them it's partly the vendor's fault they were infected are just extremeists and the vendor will never get the blame.
They didn't shutdown, and just pressed the power button, right?
Well, unless all filesystem syncrinously mounted, linux is vulnerable to that also, even with journaling your data isn't completely guaranteed if the right timing and function calls against your files happen...
Slashdot Mirror
Be sure to change "722" to a number over 1000 or else it won't downgrade...
Then downgrade you packages to working versions.
/etc/apt/preferences and then running "apt-get install " to perform the downgrade of specific packages:
You can do it with apt by adding these lines to
package: *
pin: release a=unstable
Pin-Priority: 711
package: *
pin: release o=Debian
Pin-Priority: 722
Why not spend $40 and sponsor your pet bug to be fixed in mozilla?
I read that the Linux people asked the BSD people if they could copy the BSD TCP/IP stack, but the BSD people declined.
So, the Linux network stack should be different code.
If you look at the typical contract, you will see that the "copyright holder" *is* the record company.
Fucking brits!
Hey, that's not such a bad idea...
And windows has obviously benefited from that!
Poor AC, did you just reply to yourself?
I believe read only segments are for the VM so that it can get a page fault when there is an access and know what parts of memory have been used recently.
Read-only doesn't prevent execution.
As long as Billy boy wants some pussy, Clippy/Clipit will be in Office.
'Nuff said.
No, just one moderator that saw your post before all of the replies...
How about merging what the distros have done into the base distribution?
And what if the impact was during the time antartica wasn't covered by ice?
How about a discount if you last *longer*?
That way guys guys might have an encentive to become better lovers. I mean, if you have to pay for it, that has to say something...
"Mild spoiler: It features a giant flying rock head that vomits guns on barbarians. I am not making this up. Giant flying head made of stone, guns are projected from its mouth..."
;)
OK, after reading that spoiler I laughed so hard I just have to see this movie! It's a comedy right?
Or maybe it's so bad it should've been one?
"and the shitty OS that allowed itself to be infected"
.vbs and .bat to .sh and .csh scripts in the emails? Sure, at least it will only affect the single user if they're not running as root, but FLOSS is susceptable to attact at the human level also.
OK, come on I'm as much a FLOSS (ie, "Linux") advocate as anyone else, but what happens when it changes from
Oh, you say the script doesn't have the executable bit, but look at mozilla and thunderbird. For a while they made you save your attachments before opening them. And there was a large percentage of the user base that wanted "double click on attachement opens file" functionality.
Move people to a FLOSS OS like Linux or BSD, and you'll get the same pressures.
I've had that sig so long that I haven't read it since I put it in.
Thanks, it should be corrected now.
Mike
"You probably thought of slapping the powerplant example right in my face, where critical systems can become compromised, and can become a real life threatening danger to people, and that's very, very seriously bad. But you know that those systems should be protected well enough so that such things simply can't go wrong when that magnitude of risk is involved. They build airplane- and bomb- proof cages around nuclear reactors for a reason. Why is it so strange to ask for similar stringent approaches when software is involved? The real fuckwit is not the killer, it is the one that doesn't care enough and so allows the catastrophe to happen."
Those protections wouldn't be around the power plants unless there was some risk of people trying to exploit the explosiveness of the power plant. If there weren't crazy people thretening the power plant, or the cold war those protections simply would not be there.
The funny thing is that it's the same people who complain about the military budget and costs of those things to *protect* people that say we need these other protections in the same logical direction (thick cages to protect against bomb and airplane attack).
andr0meda hasn't come out saying that virus writers shouldn't be punished, just that they serve a purpose. I say that you'd lose a lot of virus writers if doing that didn't have punishment. They wouldn't be l33t anymore, but you'd get overwhelmed with the others that don't care about leetness and get even more people than when it was banned.
Anyway, you have an entire industry supported by virus writers. Antivirus, just like you have an entire industry supported by crooks and robers, the police. The larger effect from virus writers isn't going to be larger penetration of OSS anti-virus and anti-spam, it's going to be more freedoms lost because the majority of people don't understand how computers work and will ask for laws to protect them, and their IT people who are telling them it's partly the vendor's fault they were infected are just extremeists and the vendor will never get the blame.
Nope.
Right handed for those lefties out there.
Be sure to file an installation report for this...
Let me guess.
They didn't shutdown, and just pressed the power button, right?
Well, unless all filesystem syncrinously mounted, linux is vulnerable to that also, even with journaling your data isn't completely guaranteed if the right timing and function calls against your files happen...
Make sure your kernel has highmem support compiled in...
The problem is that you didn't show any effort put into researching the issues yourself, and that's why people are flaming you.
It's like complaining someone gave you the finger when you stand in the middle of the intersection...
If it's going to save you millions I think you can afford a few extra people optimizing loops.
You will have that If you use one of the indexers from this[1] post on top of AFS.
1 16038&c id=9824114
[1]
http://linux.slashdot.org/comments.pl?sid=