Date: Thu, 03 Aug 2006 17:40:22 +1000 From: Antony Mawer <fbsd-questions@mawer.org> To: User Freebsd <freebsd@hub.org> Cc: Xiao-Yong Jin <xj2106@columbia.edu>, freebsd-questions@freebsd.org Subject: Re: Gotta start somewhere ... how many of us are really out there? Message-ID: <44D1A866.2030206@mawer.org> In-Reply-To: <20060803011653.G6529@ganymede.hub.org> References: <20060728164526.E27679@ganymede.hub.org> <17615.30414.314802.792740@jerusalem.litteratus.org> <ef10de9a0608011037w3609b5a6k1709aea61d43ed0f@mail.gmail.com> <20060801223754.U27679@ganymede.hub.org> <ef10de9a0608011859q45bdd636o757fb4aba2d3404d@mail.gmail.com> <20060801230301.Q27679@ganymede.hub.org> <df9ac37c0608012122q196a6434jf849cc7bd8c1156@mail.gmail.com> <44D09F46.6020300@dial.pipex.com> <ef10de9a0608021047u553a812fpbcf09c8c26df09b6@mail.gmail.com> <44D0F2FE.9020507@dial.pipex.com> <ef10de9a0608021216u455099a9yf66ea2d1698f4d19@mail.gmail.com> <20060802203604.A6529@ganymede.hub.org> <44D153D0.9000304@webanoide.org> <87wt9qzh2i.fsf@photon.homelinux.org> <20060803011653.G6529@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/08/2006 2:25 PM, User Freebsd wrote: >> b. Duplicates. > > Ted seems to have this covered with the CPU ID thing ... Isn't this one of those things that BIOS vendors added a "Disable" flag to their BIOS setup's for in order to prevent the wide-spread privacy concerns that cropped up when it was first released? I'm fairly sure this is disabled on most of the systems I've built... The token-based system mentioned by Mikhail Goriachev sounded interesting, although I haven't done any further thinking past what was originally mentioned... >> c. Fakery. > > IMHO, not a *really* big issue ... I could see someone bothering to do > it once or twice, but seems to be "alot of work for little gain" ... Agreed... I could probably add around 1,500 systems that could conceivably be setup to chime in with their numbers periodically; one of the pre-requisites for that would be that the access method be HTTP or HTTPS based so it could be relayed via a proxy... Another nice thing to include might be a hash of hardware inventory (a further opt-in thing beyond the basic checkins)... Mark alluded to this early in the piece, but it would be nice to be able to pull up something that said "hang on, out of the X% of users on file, Y% are using Adaptec SCSI cards, in particular model XYZ"... this would be very helpful when trying to get vendor support etc... Some form of hash calculated on these would allow you to detect if they had changed at all, and only re-send them in the event of a change... ... just thinking out loud ... ! -Antony
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44D1A866.2030206>