From: Marcin Dalecki <dalecki@evision.ag>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pavel Machek <pavel@elf.ucw.cz>,
Albert Cranford <ac9410@bellsouth.net>,
Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2/9] 2.5.6 lm_sensors
Date: Fri, 26 Jul 2002 15:29:49 +0200 [thread overview]
Message-ID: <3D414ECD.3050004@evision.ag> (raw)
In-Reply-To: 1027694678.13429.40.camel@irongate.swansea.linux.org.uk
Alan Cox wrote:
> On Fri, 2002-07-26 at 11:46, Pavel Machek wrote:
>
>>Someone should write windows virus killing thinkpads -- to get some
>>nice publicity for IBM. Hardware that commits suicide on i2c access is
>>just not nice.
>>
>>Hmm, perhaps bugtraq article with "severe DoS on thinkpad hardware"
>>would be nice, too.
>
>
> Given an afternoon someone competent can easily write a worm that
> destroys every scsi hard disk, almost every PC bios, your IDE firmware,
> some laptop batteries some USB devices and far more.
>
> The "you cant break the computer" thing is simply not true for almost
> any PC class device.
>
> I wouldn't pick on IBM here.
And it would be after all a bit hard to get an exponential propagation
curve, becouse the incubator is killing himself in this case :-).
next prev parent reply other threads:[~2002-07-26 13:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 14:06 [patch 2/9] 2.5.6 lm_sensors Albert Cranford
2002-07-20 2:07 ` Alan Cox
2002-07-20 1:04 ` Arnaldo Carvalho de Melo
2002-07-20 3:33 ` Oliver Xymoron
2002-07-20 4:08 ` Kelledin
2002-07-20 4:11 ` Gabor Kerenyi
2002-07-20 4:14 ` Arnaldo Carvalho de Melo
2002-07-20 4:13 ` Arnaldo Carvalho de Melo
2002-07-20 20:12 ` Alan Cox
2002-07-26 10:46 ` Pavel Machek
2002-07-26 14:44 ` Alan Cox
2002-07-26 13:29 ` Marcin Dalecki [this message]
2002-07-26 16:46 ` Florian Weimer
2002-07-29 22:24 ` Pavel Machek
2002-07-30 20:08 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D414ECD.3050004@evision.ag \
--to=dalecki@evision.ag \
--cc=ac9410@bellsouth.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
--cc=pavel@elf.ucw.cz \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox