mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sven Ladegast <sven@linux4geeks.de>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: KLive: Linux Kernel Live Usage Monitor
Date: Tue, 30 Aug 2005 10:53:13 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.63.0508301044150.1984@cassini.linux4geeks.de> (raw)
In-Reply-To: <20050830082901.GA25438@bitwizard.nl>

On Tue, 30 Aug 2005, Rogier Wolff wrote:

> 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.

The problem is that people made bad experiences with home-phoning software 
in the past. Changing their opinion about this issue isn't easy I think.
I can almost see the headlines: Spy software found in recent Linux 
kernels... :o)

Although home-phoning can be useful under certain circumstances it is the 
wrong way to implement it in a kernel. IMHO a userspace tool is the better 
solution: Everyone can decide if he/she wants to report what kernel 
version is running on their systems.

> 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.

This could be a sloution but like you know UDP packets may or may not 
arrive the destination address. So the packet loss with this method could 
be very high, expecially if you send only one packet. Using a 
TCP-connection for this is a lot more stable and the payload can be 
encrypted too.

Once again: I think this is a userspace task.

Sven


  reply	other threads:[~2005-08-30  8:53 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30  3:09 Andrea Arcangeli
2005-08-30  8:01 ` Sven Ladegast
2005-08-30  8:29   ` Rogier Wolff
2005-08-30  8:53     ` Sven Ladegast [this message]
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
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=Pine.LNX.4.63.0508301044150.1984@cassini.linux4geeks.de \
    --to=sven@linux4geeks.de \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®