Date: Tue, 7 Aug 2012 20:41:52 -0700 From: Jason Helfman <jgh@FreeBSD.org> To: Eitan Adler <eadler@freebsd.org> Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org, Robert Watson <rwatson@freebsd.org> Subject: Re: svn commit: r39249 - head/en_US.ISO8859-1/books/faq Message-ID: <CAMuy=%2BjeMqWFaJzbMVHOZBZ0m1yyvcCpSp9DRipg2He1mZTSHw@mail.gmail.com> In-Reply-To: <CAF6rxgkOb2XX0k6FbGeYyu5JjFv4qWQP%2BggirDgVLTkWRvVKSQ@mail.gmail.com> References: <201207222219.q6MMJeAL032049@svn.freebsd.org> <alpine.BSF.2.00.1207281106040.53430@fledge.watson.org> <CAF6rxgkOb2XX0k6FbGeYyu5JjFv4qWQP%2BggirDgVLTkWRvVKSQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 5, 2012 at 12:52 PM, Eitan Adler <eadler@freebsd.org> wrote:
> On 28 July 2012 03:07, Robert Watson <rwatson@freebsd.org> wrote:
> > On Sun, 22 Jul 2012, Eitan Adler wrote:
> > A further consideration in the source code-related sections is that
> building
> > your own {world, kernel} will bump you off the support path for binary
> > updates and upgrades with freebsd-update. This is increasingly a
> > consideration for our default kernel configuration: kernel options that
> > require recompilation force users not to use the most user-friendly
> upgrade
> > path we have.
>
> I've committed some text to this effect.
>
> --
> Eitan Adler
> Source & Ports committer
> X11, Bugbusting teams
>
And the other side of this, is if you decided to run your own custom
kernel, you can run your own update server, and follow the patches from
upstream security. Here is an article I wrote to this affect.
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/freebsd-update-server/
--
Jason Helfman | FreeBSD Committer
jgh@FreeBSD.org | http://people.freebsd.org/~jgh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMuy=%2BjeMqWFaJzbMVHOZBZ0m1yyvcCpSp9DRipg2He1mZTSHw>