mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sven Ladegast <sven@linux4geeks.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: KLive: Linux Kernel Live Usage Monitor
Date: Wed, 31 Aug 2005 16:28:59 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.63.0508311623540.2012@cassini.linux4geeks.de> (raw)
In-Reply-To: <1125495297.3355.24.camel@localhost.localdomain>

On Wed, 31 Aug 2005, Alan Cox wrote:

>> Registering means to create an ID for the system? Something out of
>> timestamp plus your PCI IDs and CPU info and so on?
>
> Or have the other end issue you some kind of secure cookie, which was my
> thought. Generating it locally as you suggest would be even better as a
> hardware change would make a box change identity automatically

Reading twice is sometimes better. :) It must have been late yesterday...

Well changing ID automagically can be okay because a system changes its ID 
from time to time and so you cannot track a certain system/person easily.

Why not generating a unique system ID at compilation stage of the kernel 
if the apopriate kernel option is enabled? This needn't have something to 
do with klive...just a unique kernel-ID or something like that.

klive, if userspace or not, finally makes use of this ID to generate live 
stats of kernel usage. PCI-IDs, CPU and whatever else could be used as a 
salt to generate a really UNIQE ID...

Sven

  reply	other threads:[~2005-08-31 14:29 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
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 [this message]
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.0508311623540.2012@cassini.linux4geeks.de \
    --to=sven@linux4geeks.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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

Powered by JetHome