From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 13:57:08 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AD9B56C4 for ; Tue, 20 Jan 2015 13:57:08 +0000 (UTC) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 768E6183 for ; Tue, 20 Jan 2015 13:57:08 +0000 (UTC) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 341B520902 for ; Tue, 20 Jan 2015 08:57:07 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Tue, 20 Jan 2015 08:57:07 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= x-sasl-enc:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; s=mesmtp; bh=4l5jEYbGy8ZUw1iDn9QvcuRI6Ag=; b=kDXVE5oyl7XPcg4CK5 u8Ee2wyGnRMJPnFvjXqUaHuj4LApXenvOUDKku819cn1T41T7JkPe1JIQZ3NbjNJ 3TyaMYE+TD9Za1ml/CZEW0D8Kt0CeSCbGFWX0vVrIDyyQrfm/ei8dozZSUi8ErEw +921wpzFo7lw61OLxf2aa2W7g= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:date:from:to:subject :message-id:in-reply-to:references:mime-version:content-type :content-transfer-encoding; s=smtpout; bh=4l5jEYbGy8ZUw1iDn9Qvcu RI6Ag=; b=QHigMh/mGDmb/kIlqB/G3WELLF8E22os1Kjgv0LZDOKkbL4A1mfTRO +vA5Az6/dFTcQUt5s3tUwmYok+tyNoAU4MU4B6zL/ksaRBv/f6K8QasFenFX4E52 4P5BqEjbQVkTy1+bsryLAKUuK//HT0BPiFmYEmHKz6LRlUJlM9FzU= X-Sasl-enc: IR4ohm+RGhm/PYRrOk4lfGhKScYnJ9YXztpAL2oNWUjP 1421762226 Received: from alonso-desktop.sodgeit.de (unknown [46.237.203.179]) by mail.messagingengine.com (Postfix) with ESMTPA id BE9146800FD for ; Tue, 20 Jan 2015 08:57:06 -0500 (EST) Date: Tue, 20 Jan 2015 14:57:04 +0100 From: "Schaich, Alonso" To: freebsd-stable@freebsd.org Subject: Re: Keep -STABLE updated! Message-Id: <20150120145704.9882c30b83455d2dff9ed98a@fastmail.fm> In-Reply-To: References: <54BDB10D.4000603@gmail.com> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.25; amd64-portbld-freebsd10.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2015 13:57:08 -0000 On Tue, 20 Jan 2015 08:30:16 -0500 Paul Mather wrote: > On Jan 19, 2015, at 8:54 PM, Brandon Allbery wrote: > > > On Mon, Jan 19, 2015 at 8:36 PM, Yass Amed wrote: > > > >> I'd like to clarify a certain info regarding FreeBSD -STABLE. > >> Currently, I am running 10-STABLE and need to know if it is mandatory to > >> rebuild kernel and world every time I sync the source using "# svn up > >> /usr/src"? > >> > > > > A running FreeBSD system never needs /usr/src. But if you are running > > STABLE (or CURRENT), sometimes you will want to look at the source to > > something in the running system (usually because it just did something > > unexpected...) and so it's helpful to have /usr/src match the running > > system. So, not necessary but often a good idea. > > > It's correct that, once built and running, a FreeBSD system never needs /usr/src. However, a -STABLE or -CURRENT FreeBSD system will need /usr/src to apply any security advisories or errata (as happened recently, re: OpenSSL). Unlike -RELEASE branches, -STABLE and -CURRENT don't get updates via freebsd-update. > > Also, it's handy to have /usr/src and rebuild if ever there is a feature MFC'd that you'd like to have available on your -STABLE system (e.g., the bhyve support for AMD processors that was MFC'd not so long ago). That's usually the main reason for running -STABLE, actually. > > Cheers, > > Paul. Also, nvidia, VirtualBox and some other packages contains kernel modules, which require a kernel source code and your setup might be affected by more updates of those ports than the system is affected by security erratas. Alonso