Date: Sun, 18 Dec 2005 11:05:45 +0800 From: Erich Dollansky <oceanare@pacific.net.sg> To: Scott Long <scottl@samsco.org> Cc: Peter Jeremy <PeterJeremy@optushome.com.au>, stable@freebsd.org, =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= <gabor.kovesdan@t-hosting.hu>, current <current@freebsd.org> Subject: Re: FreeBSD Update is the binary update solution [Re: HEADS UP: Release schedule for 2006] Message-ID: <43A4D209.2000609@pacific.net.sg> In-Reply-To: <43A4B91D.8040304@samsco.org> References: <43A266E5.3080103@samsco.org> <20051217215434.GB92180@svcolo.com> <20051217220807.GA28741@freebie.xs4all.nl> <43A492B6.6050305@t-hosting.hu> <20051217232856.GT77268@cirb503493.alcatel.com.au> <43A4B91D.8040304@samsco.org>
index | next in thread | previous in thread | raw e-mail
Hi, Scott Long wrote: > Peter Jeremy wrote: > >> I think FreeBSD Update shows the way forward but IMHO there needs to >> be an "official" binary update tool accessible from www.freebsd.org. >> > > FreeBSD Update was written by, and is continuously maintained by the > actual FreeBSD Security Officer. It's as official as it gets. If > the only barrier to acceptance is that it's not distributed from the > FreeBSD.org domain, then a) that's a silly argument, and b) it's easily > solvable so long as Colin agrees. > isn't this the problem Microsoft faces all the while when users download the latest security patch from somewhere in the Internet? Teaching water and drinking wine? Erichhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43A4D209.2000609>