Date: Mon, 19 Aug 2013 05:31:07 +0200 From: Polytropon <freebsd@edvax.de> To: freebsd-lists@freebsd.org Cc: John <freebsd-lists@potato.growveg.org>, freebsd-questions@freebsd.org Subject: Re: freebsd 9.2 via svn Message-ID: <20130819053107.511189ba.freebsd@edvax.de> In-Reply-To: <20130819032215.GA2464@potato.growveg.org> References: <20130819012825.GA2420@potato.growveg.org> <20130819041702.d9f1ce38.freebsd@edvax.de> <20130819032215.GA2464@potato.growveg.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 19 Aug 2013 04:22:15 +0100, John wrote: > > If you don't use a custom kernel, why not use freebsd-update > > and follow the 9.2-RELEASE path with the security updates? > > Not sure if this is logic or "religon", but freebsd-update makes me > nervous. I'm allergic to automatic anything unless I've written it. The only > times I've run generic is when installing a new system, to see what I > need and what I don't. Maybe I'm just old. You demonstrated a valid argument for building from source. Using freebsd-update, a binary method is used for updating the _default_ system and the GENERIC kernel. If you have custom settings and therefore _intend_ to build from source, changing the version in your "svn co" command to the new -RELEASE-pX branch (security update branch) is safe. I've been using a similar approach with CVS to follow the -STABLE branch with a custom kernel and custom settings for building the system. If this makes me old, I should deserve several birthday parties per year. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130819053107.511189ba.freebsd>