Date: Fri, 02 Jan 2015 18:46:37 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Roger Marquis <marquis@roble.com> Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-14:31.ntp Message-ID: <86y4plgjnm.fsf@nine.des.no> In-Reply-To: <20141231195427.AECE022B@hub.freebsd.org> (Roger Marquis's message of "Wed, 31 Dec 2014 11:54:18 -0800 (PST)") References: <20141223233310.098C54BB6@nine.des.no> <86h9wln9nw.fsf@nine.des.no> <549A5492.6000503@grosbein.net> <868uhx43i5.fsf@nine.des.no> <20141226200838.DE83DACE@hub.freebsd.org> <8661cy9jim.fsf@nine.des.no> <20141231195427.AECE022B@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Roger Marquis <marquis@roble.com> writes: > Problem with freebsd-update is that it has some of the same scope issues > as installworld. We've also had problems defining "-r" (in a jail) when > the booted kernel is not the revision we want to build to. Doesn't help > that "-r" doesn't parse patch levels. I do it all the time: $ sudo env UNAME_r=3DX.Y-RELEASE freebsd-update fetch install Patch levels don't matter to freebsd-update, it will look at what's actually installed and not what the kernel says (which is not necessarily correct anyway, because some updates don't touch the kernel). It just needs to know the correct release. Not sure what you mean by scope issues. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86y4plgjnm.fsf>