I can assure you he isn't the first person to discover a way to physically
destroy a disk via software. It's not hard.... I can think of 3 or 4 ways
to do it right off the top of my head.
The way I figure it, Andre is the expert on this topic. If he says that
his driver is allowing a violation of the spec which has some nasty
consequences, then we should listen to him.
I just wish I could help test his patch... but I don't have any machines
available for testing that... everything is allready allocated to other
products (or production environments).
Matt
On Fri, Jul 21, 2000 at 12:00:46PM -0500, Mike Castle wrote:
> On Fri, Jul 21, 2000 at 09:19:00AM -0700, Scott Long wrote:
> > 2.4. And no one in this office will, either. If all versions of Linux
> > are susceptible, maybe we'll look for a different OS where it is more
> > difficult to accomplish this damage. We cannot afford data destruction,
> > but even more importantly we CERTAINLY cannot afford having our disks
> > physically destroyed.
>
> What if there is no such OS, but rather a flaw in the whole hardware
> architecture design? Where do you run then?
>
> If Andre hadn't posted the code, someone eventually would had. It's not
> unfortunate he did that at all; but rather quite fortunate that he did.
> Because now it brings it out to the public. Do you really think he was the
> first one to notice this?
>
> mrc
-- Matthew Dharm Home: mdharm@one-eyed-alien.net Senior Engineer, QCP Inc. Work: mdharm@qcpi.comC: They kicked your ass, didn't they? S: They were cheating! -- The Chief and Stef User Friendly, 11/19/1997
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jul 23 2000 - 21:00:16 EST