From owner-freebsd-chat@FreeBSD.ORG Mon Jan 26 06:30:55 2004 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A445116A4CE for ; Mon, 26 Jan 2004 06:30:55 -0800 (PST) Received: from hannibal.servitor.co.uk (hannibal.servitor.co.uk [195.188.15.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AFDF43D39 for ; Mon, 26 Jan 2004 06:30:53 -0800 (PST) (envelope-from paul@iconoplex.co.uk) Received: from hannibal.servitor.co.uk ([195.188.15.48] helo=iconoplex.co.uk) by hannibal.servitor.co.uk with esmtp (Exim 4.14) id 1Al7lS-0008PY-Mq; Mon, 26 Jan 2004 14:30:58 +0000 Message-ID: <40152488.8070309@iconoplex.co.uk> Date: Mon, 26 Jan 2004 14:30:32 +0000 From: Paul Robinson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Colin Percival References: <4013EA9D.6040808@cream.org> <20040125134151.M52260@mail.tacorp.net> <20040125185753.GA12995@happy-idiot-talk.infracaninophile.co.uk> <40141B3D.9070901@cream.org> <20040125194721.GA28036@xor.obsecurity.org> <40143CC3.6010709@cream.org> <401514D3.7020808@iconoplex.co.uk> <6.0.1.1.1.20040126133123.0465b398@imap.sfu.ca> In-Reply-To: <6.0.1.1.1.20040126133123.0465b398@imap.sfu.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: chat@freebsd.org Subject: Re: Less messages to FreeBSD.org lists X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2004 14:30:55 -0000 Colin Percival wrote: > It's *fewer* messages, not *less* messages! I've just nicked your wallet you toff! :-) > I'd say that a more useful option would be to add code which > "pings" a server every day with a request for binary security > updates. Oooh.... now we're heading into the realms of Windows Update, and we know how badly that can behave at times. As long as it was completely optional, in fact something that sits in ports and not base, I'd think that would work OK. The problem is, with so many builds out there on so many platforms, linked with so many libraries, you can't just dispatch a list of MD5s and know a particular item is "broken". -- Paul Robinson