I'd love to see a more vibrant market for this. The cost paid per bug (perhaps normalized by product revenue) would be a really useful measure of software reliability.
This is not correct. An officer may briefly detain a suspect if he has reasonable suspicion of criminal activity, even if he does not have grounds to arrest the individual. (Terry v. Ohio: http://en.wikipedia.org/wiki/Terry_stop)
Really, you'd just need to put enough series inductance on the D- and D+ lines to foul up any data transfer. That way systems like the iPhone's charge sensing resistor trick would still work.
Self-modifying code, like the JVM is using all the time on my local machine, as we speak? Sure, I have to do memory protection carefully, and a whole page at a time, but self-modifying code is most certainly not dead.
If you really wanted cheap and simple, a network of AVRs would be approximately what he has here. Meanwhile, I can use the Apple IIe boards to restore more Apple IIe's...
Of course, nowadays the generic PC is a cluster computer. How many single-core machines do you see these days? Factor in the GPU, and you pretty much are hacking on a mid-80s vector computer.
There are very strict rules of evidence that require you to PROVE that you didn't tamper with data. Mounting a disk read/write certainly violates those rules. Attaching the disk to a computer that CAN mount the disk read/write (as opposed to using a hardware write blocker) probably violates them.
The brilliance of this is that even if the Flip itself flops, Cisco still wins in the long run. As long as the Flip and the insane marketing hype surrounding it increased the popularity of HD video sharing on the web, people are going to need more routers in the network itself. I wonder who the ISPs and YouTubes of the world will be going to then...
Cisco never needed to sell the Flip as a physical product, they just needed to sell the idea of shooting LOTS of video and sharing it across the web. It seems like they've succeeded.
OTR doesn't actually use the keys it stores for the encrypted message. When you start a new conversation, both sides generate a new set of session keys randomly. The stored key is then used to sign the session keys so that the other party can trust that the session key is valid, and from you.
If you lose your keys, an attacker can pretend to be you until you update the public keys that your friends will be looking for, but previous messages aren't compromised. In that way, it's a fair bit safer than PGP.
While the primary SD interface is kinda complex, SD cards are required to support an SPI interface, which is pretty much the most brain-dead simple interface imaginable.
Most microcontrollers will support it natively, and it's incredibly simple to implement in hardware and software. It's what I usually use when I need to back a PIC with lots of storage.
This isn't how modern statistics is done. The pseudo-random number generators used in statistical research are entirely predictable when their initial seed is known, but are otherwise statistically random. They must obey certain requirements of "statistical randomness" that make the output look like pure entropy for essentially any form of real statistical examination, other than an attempt at determining the sequence directly. Monte carlo computation is always done with PRNGs so that the experiments are actually repeatable.
The modern PRNG, something like the Mersenne twister algorithm, is random enough that if you repeated the experiment done in the article with a true entropy source a bunch of times, and compared them to the results from running the PRNG based simulation, you should find identical distribution of results. If you don't, you'd have a statistical find much, much more interesting than baseball. The point of a good algorithm is that it won't have a visible "bias" in results.
Now, it is possible that a really bad PRNG could impact research results, and they have in the past. The RANDU algorithm is a particularly good example, but it was really, really, really astronomically bad. I doubt the authors used something like this.
PS3 or not, Blu-Ray players (as with most modern A/V stack components) put out a boatload of heat. They really shouldn't be stacked without at least some breathing room. I'd bet that the top of the PS3 was designed like it was for that express purpose.
There were other considerations with the 45nm cell that should increase yields that were mentioned in their talk. (I was there. Page 86 of your digest, for those of you who just pulled the digest off your shelf to re-read the paper;-)) The yields were low enough that they said they were much more careful with design for manufacturing, which is a relatively new field of study. They didn't redo any of the major floorplanning, but the synthesized blocks were resynthed using newer techniques, which should improve overall yeild. Basically, they just avoided the kind of geometry that was likely to break. The tool they used to scale the geometry was also modified to be mindful of yield. The results are not as significant as just the plain old area drop, but they should be useful.
The n series, while it comes with FreeDOS, doesn't actually come with FreeDOS installed. It's just a media kit. I would assume that the only reason they do this is to fulfill some licensing agreement they have with someone about not shipping an OS-free computer. I would guess that the vast, vast majority of n series machines never see FreeDOS beyond sitting next to the CD in the box.
Well, now that we're being pedantic, it's actually not "MacOS" anymore. "MacOS" was for the classic versions, OS X is spelled "Mac OS X", with the space, so "OS X" is correct.
The problem with these sort of things is that NASA is placed in an absolutely impossible situation if someone cries wolf to the press, and there isn't a wolf to be found. The same sort of thing happened with the A380.
This engineer felt that there was a fundamental design issue with an IC used in the pressurization system of an airliner. His bosses and fellow engineers, all the way up the chain felt otherwise. This has been an absolute nightmare for Airbus, and even if we assume that the directors have no sense of morals and are just looking at the bottom line, it would likely have been cheaper just to fix whatever problem was there than deal with the aftermath of some engineer writing to any newspaper that'll print him, so they looked. And, in the opinion of all the other engineers in the program, there wasn't a problem. Now what? You either keep him on and let this guy spout off forever about how dangerous your product is, likely causing the shareholders to demand a vendor switch even with nothing at all wrong just because it will look bad for the airframe, a hugely expensive gamble for the Airbus group, or you fire him and try to shut him up, and now everybody screams cover-up.
I'm not necessarily saying this is an analogous situation. I don't know what went on in the meetings where he got transferred, or what he said to piss people off. I am saying that it's not always as simple as people think.
Pretty sure I wouldn't be able to either. I mean, the Katami, being a much earlier chip probably has about half the number of pins that the Conroe has and might be lighter, but the Conroe uses BGA, so it'd probably hurt less, being less spiky. In the end, though, Conroe, Katami or 6502, I'd mainly just be pissed that you hit me in the head with one.
Slashdot Mirror
I'd love to see a more vibrant market for this. The cost paid per bug (perhaps normalized by product revenue) would be a really useful measure of software reliability.
http://www.amazon.com/TiVo-TCD649080-80-Hour-Digital-Recorder/dp/B000ER5G58/ref=sr_1_1?ie=UTF8&qid=1328644598&sr=8-1
You can still buy a perfectly good Series2 TiVo. Analog tuner and all.
This is not correct. An officer may briefly detain a suspect if he has reasonable suspicion of criminal activity, even if he does not have grounds to arrest the individual. (Terry v. Ohio: http://en.wikipedia.org/wiki/Terry_stop)
Postscript, being a Turing Complete language, would seem to violate the "no interpreters" rule.
Okay, so buy two. Still cheaper and smaller.
The authors get practically nothing from textbook sales, depressingly. Almost all of the money goes to the publisher.
Really, you'd just need to put enough series inductance on the D- and D+ lines to foul up any data transfer. That way systems like the iPhone's charge sensing resistor trick would still work.
Self-modifying code, like the JVM is using all the time on my local machine, as we speak? Sure, I have to do memory protection carefully, and a whole page at a time, but self-modifying code is most certainly not dead.
If you really wanted cheap and simple, a network of AVRs would be approximately what he has here. Meanwhile, I can use the Apple IIe boards to restore more Apple IIe's...
Of course, nowadays the generic PC is a cluster computer. How many single-core machines do you see these days? Factor in the GPU, and you pretty much are hacking on a mid-80s vector computer.
They paid for a MASSIVE advertising push.
There are very strict rules of evidence that require you to PROVE that you didn't tamper with data. Mounting a disk read/write certainly violates those rules. Attaching the disk to a computer that CAN mount the disk read/write (as opposed to using a hardware write blocker) probably violates them.
The brilliance of this is that even if the Flip itself flops, Cisco still wins in the long run. As long as the Flip and the insane marketing hype surrounding it increased the popularity of HD video sharing on the web, people are going to need more routers in the network itself. I wonder who the ISPs and YouTubes of the world will be going to then...
Cisco never needed to sell the Flip as a physical product, they just needed to sell the idea of shooting LOTS of video and sharing it across the web. It seems like they've succeeded.
OTR doesn't actually use the keys it stores for the encrypted message. When you start a new conversation, both sides generate a new set of session keys randomly. The stored key is then used to sign the session keys so that the other party can trust that the session key is valid, and from you.
If you lose your keys, an attacker can pretend to be you until you update the public keys that your friends will be looking for, but previous messages aren't compromised. In that way, it's a fair bit safer than PGP.
Oh, that's why the McLaren F1 has three seats...
While the primary SD interface is kinda complex, SD cards are required to support an SPI interface, which is pretty much the most brain-dead simple interface imaginable.
Most microcontrollers will support it natively, and it's incredibly simple to implement in hardware and software. It's what I usually use when I need to back a PIC with lots of storage.
This isn't how modern statistics is done. The pseudo-random number generators used in statistical research are entirely predictable when their initial seed is known, but are otherwise statistically random. They must obey certain requirements of "statistical randomness" that make the output look like pure entropy for essentially any form of real statistical examination, other than an attempt at determining the sequence directly. Monte carlo computation is always done with PRNGs so that the experiments are actually repeatable.
The modern PRNG, something like the Mersenne twister algorithm, is random enough that if you repeated the experiment done in the article with a true entropy source a bunch of times, and compared them to the results from running the PRNG based simulation, you should find identical distribution of results. If you don't, you'd have a statistical find much, much more interesting than baseball. The point of a good algorithm is that it won't have a visible "bias" in results.
Now, it is possible that a really bad PRNG could impact research results, and they have in the past. The RANDU algorithm is a particularly good example, but it was really, really, really astronomically bad. I doubt the authors used something like this.
PS3 or not, Blu-Ray players (as with most modern A/V stack components) put out a boatload of heat. They really shouldn't be stacked without at least some breathing room. I'd bet that the top of the PS3 was designed like it was for that express purpose.
There were other considerations with the 45nm cell that should increase yields that were mentioned in their talk. (I was there. Page 86 of your digest, for those of you who just pulled the digest off your shelf to re-read the paper;-)) The yields were low enough that they said they were much more careful with design for manufacturing, which is a relatively new field of study. They didn't redo any of the major floorplanning, but the synthesized blocks were resynthed using newer techniques, which should improve overall yeild. Basically, they just avoided the kind of geometry that was likely to break. The tool they used to scale the geometry was also modified to be mindful of yield. The results are not as significant as just the plain old area drop, but they should be useful.
Of course, they won't discuss yield data...
The n series, while it comes with FreeDOS, doesn't actually come with FreeDOS installed. It's just a media kit. I would assume that the only reason they do this is to fulfill some licensing agreement they have with someone about not shipping an OS-free computer. I would guess that the vast, vast majority of n series machines never see FreeDOS beyond sitting next to the CD in the box.
I vote the three of us go out drinking some time. Not much else to do without g77/Intel easily had;-)
Actually being able to hear yourself think over the Mac? Priceless.
Well, now that we're being pedantic, it's actually not "MacOS" anymore. "MacOS" was for the classic versions, OS X is spelled "Mac OS X", with the space, so "OS X" is correct.
The problem with these sort of things is that NASA is placed in an absolutely impossible situation if someone cries wolf to the press, and there isn't a wolf to be found. The same sort of thing happened with the A380.
This engineer felt that there was a fundamental design issue with an IC used in the pressurization system of an airliner. His bosses and fellow engineers, all the way up the chain felt otherwise. This has been an absolute nightmare for Airbus, and even if we assume that the directors have no sense of morals and are just looking at the bottom line, it would likely have been cheaper just to fix whatever problem was there than deal with the aftermath of some engineer writing to any newspaper that'll print him, so they looked. And, in the opinion of all the other engineers in the program, there wasn't a problem. Now what? You either keep him on and let this guy spout off forever about how dangerous your product is, likely causing the shareholders to demand a vendor switch even with nothing at all wrong just because it will look bad for the airframe, a hugely expensive gamble for the Airbus group, or you fire him and try to shut him up, and now everybody screams cover-up.
I'm not necessarily saying this is an analogous situation. I don't know what went on in the meetings where he got transferred, or what he said to piss people off. I am saying that it's not always as simple as people think.
Pretty sure I wouldn't be able to either. I mean, the Katami, being a much earlier chip probably has about half the number of pins that the Conroe has and might be lighter, but the Conroe uses BGA, so it'd probably hurt less, being less spiky. In the end, though, Conroe, Katami or 6502, I'd mainly just be pissed that you hit me in the head with one.