Date: Fri, 6 Jan 2006 02:43:09 -0800 From: Jo Rhett <jrhett@svcolo.com> To: Ender <ender@tog.net> Cc: stable@freebsd.org, freebsd-stable@freebsd.org, current <current@freebsd.org>, K?vesd?n G?bor <gabor.kovesdan@t-hosting.hu>, Peter Jeremy <PeterJeremy@optushome.com.au> Subject: Re: FreeBSD Update is the binary update solution [Re: HEADS UP: Release schedule for 2006] Message-ID: <20060106104309.GD54324@svcolo.com> In-Reply-To: <43BD64C4.4090307@tog.net> References: <43A266E5.3080103@samsco.org> <200512231126.51500.doconnor@gsoft.com.au> <20060105093220.GJ1358@svcolo.com> <200601052112.09446.doconnor@gsoft.com.au> <43BD64C4.4090307@tog.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 05, 2006 at 01:26:12PM -0500, Ender wrote: > I think what "integrated with the core OS" means from a user standpoint > is: from a fresh minimum install of freebsd I can type > "freebsd-update-whatever" and it will update my system. Just "freebsd-update" ;-) That works fairly well with the current freebsd-update (or bsdupdates.com) solutions. For most GENERIC installed systems, it works fairly well. I use on 3 systems at my home for this, and I'm pretty happy with it. It doesn't work very well in environments with compiled options, custom kernels, and other situations. That's what I'm trying to tackle here. -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060106104309.GD54324>