From owner-freebsd-arch@FreeBSD.ORG Tue Aug 29 01:40:24 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2866A16A4DE; Tue, 29 Aug 2006 01:40:24 +0000 (UTC) (envelope-from fbsd-arch@mawer.org) Received: from mail-ihug.icp-qv1-irony6.iinet.net.au (ihug-mail.icp-qv1-irony6.iinet.net.au [203.59.1.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9BAE43D46; Tue, 29 Aug 2006 01:40:22 +0000 (GMT) (envelope-from fbsd-arch@mawer.org) Received: from 203-206-173-235.perm.iinet.net.au (HELO [127.0.0.1]) ([203.206.173.235]) by mail-ihug.icp-qv1-irony6.iinet.net.au with ESMTP; 29 Aug 2006 09:40:21 +0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.08,177,1154880000"; d="scan'208"; a="432546790:sNHT14961892" Message-ID: <44F39ACB.6090703@mawer.org> Date: Tue, 29 Aug 2006 11:39:23 +1000 From: Antony Mawer User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: "Marc G. Fournier" References: <20060825233420.V82634@hub.org> <20060826112115.GG16768@turion.vk2pj.dyndns.org> <20060826132138.H82634@hub.org> <200608261848.16513.max@love2party.net> <20060826165209.V82634@hub.org> <20060828130247.GA77702@lor.one-eyed-alien.net> <20060828170450.M82634@hub.org> In-Reply-To: <20060828170450.M82634@hub.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Max Laier , freebsd-arch@freebsd.org Subject: Re: BSDStats - What is involved ... ? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2006 01:40:24 -0000 On 29/08/2006 6:07 AM, Marc G. Fournier wrote: > On Mon, 28 Aug 2006, Brooks Davis wrote: > >> While I understand (or think I understand) the motivations for this >> design goal, it's contrary to allowing collection of statistics from >> many people. I'd love to be able to publish data from the FreeBSD >> systems (300+) at work, but unless I can do it in an anonymized >> aggregate form it's not going to happen. I just can't justify leaking >> that much internal configuration information given a policy of hiding >> it (right or wrong and not subject to debate). If I could run my own >> stats server and publish from it that might be possible. > > Agreggate submissions will never be possible, as it will definitely > break any attempts at keeping the data 'clean' :( I do understand that > we will never be able to get *everyone* reporting, but we will try as > much as possible to make it easy for as many as possible to report > *within* limits ... > > I'm going to work on an 'email submission' method in September, that > would allow repoting to go *thru* one mailbox, and will include a > confirmation/challenge stage *per* server though ... Brooks, what sort of information are you looking to "anonymise" before sending it out? Aggregating to say that I have X of this kind of CPU, Y of this IDE chipset, etc, rather than linking it specifically to each machine? Where would you feel a comfortable balance lay? Obviously some effort needs to be made to minimise fraudulent entries Perhaps aggregate submissions could be conducted using a registration mechanism... Other thoughts would be having a local stats aggregation server that pushes summaries up to the master server... the aggregation server keeps the individual details, and some sort of challenge mechanism could be randomly selected by the master server to reduce the ease with which the numbers can be 'faked'? ... just rambling as I thought of potential ways around this ...