From owner-freebsd-questions@FreeBSD.ORG Tue Oct 9 10:28:21 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 35AC78AC for ; Tue, 9 Oct 2012 10:28:21 +0000 (UTC) (envelope-from "cyb."@gmx.net) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by mx1.freebsd.org (Postfix) with SMTP id 78CCB8FC08 for ; Tue, 9 Oct 2012 10:28:19 +0000 (UTC) Received: (qmail invoked by alias); 09 Oct 2012 10:28:13 -0000 Received: from port-92-206-144-231.dynamic.qsc.de (EHLO CoreI5) [92.206.144.231] by mail.gmx.net (mp039) with SMTP; 09 Oct 2012 12:28:13 +0200 X-Authenticated: #4870692 X-Provags-ID: V01U2FsdGVkX18LFLdGAEsLYF3OtgMHZN1Tia/HSMx+jFct13hioc ShuJZdJjUOca4D Date: Tue, 9 Oct 2012 12:28:06 +0200 From: Andreas Rudisch To: Istvan Gabor Subject: Re: FreeBSD update Message-Id: <20121009122806.bfbc77cae06b6a5416cf8164@gmx.net> In-Reply-To: <7acef32e.2caae151.5073f296.83c70@lajt.hu> References: <1922c43c.49710c96.5072e8a8.f2f51@lajt.hu> <20121008173551.e2cc1aad608d691d426a640e@gmx.net> <7acef32e.2caae151.5073f296.83c70@lajt.hu> X-Mailer: Sylpheed 3.2.0 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2012 10:28:21 -0000 On Tue, 09 Oct 2012 11:47:02 +0200 Istvan Gabor wrote: > FreeBSD Handbook (at the end of section 25.2.2) says: > > "However, freebsd-update will always update the /usr/src/sys/conf/newvers.sh file. > The current patch level (as indicated by the -p number reported by uname -r) is obtained > from this file. Rebuilding your custom kernel, even if nothing else changed, will allow > uname(1) to accurately report the current patch level of the system." > > From this I conclude that if I rebuild the kernel (the general kernel, not a custom kernel), > it should reflect patch level correctly. Yes. > This raises another question: are the updates made sequentially, as p1, p2, etc.? > This would explain why the kernel stayed at p3 level while the system was updated to > p4. Yes. > I Suppose if the update was done in one step after fetching and applying all > update patches the kernel should reflect the system's patch level. Is this correct? Well, it 'should', but it does not, since freebsd-update does not work that way. p4 did not require rebuilding the kernel, so it had not been done. > I am confused a little bit. Feel free to browse the mailing lists, you are not the first one to be confused. Andreas -- GnuPG key : 0x2A573565 | http://www.gnupg.org/howtos/de/ Fingerprint: 925D 2089 0BF9 8DE5 9166 33BB F0FD CD37 2A57 3565