Re:CVE-2013-0871: Linux arbitrary kernel-mode code execution
by StefanKarpinski on Friday February 15, 2013 @11:09PM
(#5230342)
not sure if trolling or actually runs DOS
[ Parent
| on HN ]
Re:CVE-2013-0871: Linux arbitrary kernel-mode code execution
by sp332 on Friday February 15, 2013 @11:18PM
(#5230356)
COBOL ON COGS is a joke, plus I'm pretty sure a true user would get the spelling and capitalization right :) http://www.coboloncogs.org/INDEX.HTM
Re:CVE-2013-0871: Linux arbitrary kernel-mode code execution
by kintamanimatt on Saturday February 16, 2013 @12:05AM
(#5230466)
"(c) <DATE OVERFLOW>"
Oh dear!
Re:CVE-2013-0871: Linux arbitrary kernel-mode code execution
by frozenport on Saturday February 16, 2013 @12:40AM
(#5230536)
keeps his machine cool by using only 1 of 32 cores on his AMD bulldozer dual socket server board.
Re:CVE-2013-0871: Linux arbitrary kernel-mode code execution
by nilved on Friday February 15, 2013 @11:17PM
(#5230355)
Pretty obviously joking.
Re:CVE-2013-0871: Linux arbitrary kernel-mode code execution
by derleth on Saturday February 16, 2013 @12:57AM
(#5230567)
> Pretty obviously joking.
The problem with trying to sound so stupid you can't possibly be serious is that there are people who are seriously that stupid.
Re:CVE-2013-0871: Linux arbitrary kernel-mode code execution
by eclipxe on Saturday February 16, 2013 @01:28AM
(#5230638)
Poe's Law [1]
Re:CVE-2013-0871: Linux arbitrary kernel-mode code execution
by jpdoctor on Saturday February 16, 2013 @10:39AM
(#5231752)
Great list on that site, but I'm surprised they missed one of the granddaddies of such reports: http://en.wikipedia.org/wiki/Spaghetti_tree_hoax
Re:CVE-2013-0871: Linux arbitrary kernel-mode code execution
by raverbashing on Saturday February 16, 2013 @05:52AM
(#5231127)
Yeah, for me what gave away is the 9000 requests on Digital Ocean, because obviously you can do 10x that
just kidding, of course it was the last line
Re:CVE-2013-0871: Linux arbitrary kernel-mode code execution
by randomdata on Saturday February 16, 2013 @06:06AM
(#5231147)
There was a, presumably serious, post made here about Rails that was almost word-for-word, save the differing technical terms. The post here was obviously making fun of that other post, but I guess that would be lost without the prior context.