From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Sven Ladegast <sven@linux4geeks.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: KLive: Linux Kernel Live Usage Monitor
Date: Tue, 30 Aug 2005 15:36:50 +0100 [thread overview]
Message-ID: <1125412611.8276.9.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.63.0508300954190.1984@cassini.linux4geeks.de>
On Maw, 2005-08-30 at 10:01 +0200, Sven Ladegast wrote:
> The idea isn't bad but lots of people could think that this is some kind
> of home-phoning or spy software. I guess lots of people would turn this
> feature off...and of course you can't enable it by default. But combined
> with an automatic oops/panic/bug-report this would be _very_ useful I think.
Wrong way around - you need to let people turn it on. Perhaps distribute
it with the kernel so you can
make register
[Reports hardware, stashed a unique sha-1 hashed cookie]
[Asks for permission, installs UDP ping daemon]
make unregister
but it would have to be opt in. That might lower coverage but should
increase quality, especially id the id in the cookie can be put into
bugzilla reports, and the hardware reporting is done so it can be
machine processed (ie so you can ask stuff like 'reliability with Nvidia
IDE')
Alan
next prev parent reply other threads:[~2005-08-30 14:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 3:09 KLive: Linux Kernel Live Usage Monitor Andrea Arcangeli
2005-08-30 8:01 ` Sven Ladegast
2005-08-30 8:29 ` Rogier Wolff
2005-08-30 8:53 ` Sven Ladegast
2005-08-30 9:40 ` Rogier Wolff
2005-08-30 9:54 ` Bernd Petrovitsch
2005-08-30 15:10 ` Andrea Arcangeli
2005-08-30 16:33 ` Alan Cox
2005-08-30 16:16 ` Andrea Arcangeli
2005-08-30 16:56 ` Alan Cox
2005-08-30 16:40 ` Andrea Arcangeli
2005-08-31 18:32 ` Pavel Machek
2005-09-01 15:19 ` Andrea Arcangeli
2005-08-30 16:36 ` Jesper Juhl
2005-08-30 22:11 ` Bill Davidsen
2005-08-31 1:49 ` Andrea Arcangeli
2005-08-31 19:14 ` tony.luck
2005-08-31 19:47 ` Andrea Arcangeli
2005-09-05 18:26 ` Andrea Arcangeli
2005-08-30 14:45 ` Andrea Arcangeli
2005-08-30 14:36 ` Alan Cox [this message]
2005-08-30 22:43 ` Sven Ladegast
2005-08-30 23:25 ` Alan Cox
2005-08-30 23:19 ` Sven Ladegast
2005-08-31 13:34 ` Alan Cox
2005-08-31 14:28 ` Sven Ladegast
2005-08-31 21:23 ` Andrea Arcangeli
2005-08-30 14:56 ` Andrea Arcangeli
2005-08-31 18:20 ` Pavel Machek
2005-09-01 15:23 ` Andrea Arcangeli
2005-09-01 12:26 ` Sven Ladegast
2005-09-05 22:05 ` Marc Giger
2005-09-05 23:13 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2005-08-30 17:08 Wilkerson, Bryan P
2005-08-30 17:44 ` linux-os (Dick Johnson)
2005-08-30 20:31 ` Andrea Arcangeli
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=1125412611.8276.9.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sven@linux4geeks.de \
/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