From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
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 10:29:01 +0200 [thread overview]
Message-ID: <20050830082901.GA25438@bitwizard.nl> (raw)
In-Reply-To: <Pine.LNX.4.63.0508300954190.1984@cassini.linux4geeks.de>
On Tue, Aug 30, 2005 at 10:01:21AM +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.
It IS some "home phoning" and "spy software". However, when the
goal is to sign you up for more direct marketing, people tend to
object. When the goal is to keep track of running kernels, I'm
hopeful that people will recognise that this is different.
A trick to use would be to send an UDP packet at boot (after 1 minute
or so), and then randomly say "once a month" (i.e. about 1/30 chance of
sending a packet on the first day) The number of these random packets
recieved is a measure of the number of CPU-months that the kernel
runs.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
next prev parent reply other threads:[~2005-08-30 8:29 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 [this message]
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
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=20050830082901.GA25438@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--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