Date: Sat, 19 Dec 2015 10:30:34 -0800 From: Kevin Oberman <rkoberman@gmail.com> To: Mark Martinec <Mark.Martinec@ijs.si> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: Per-jail private loopback Message-ID: <CAN6yY1vLwAuwg6%2BwatHWPYzrrGQzL4Bm-c39KRBTQMiUEsrgGg@mail.gmail.com> In-Reply-To: <567421B4.6020302@ijs.si> References: <22131.18881.757188.951230@hergotha.csail.mit.edu> <CAG=rPVeuq8DM9wnaNAGrDKeMZs=DtcPh-5ZL46mi3apQ=ER3rg@mail.gmail.com> <56740DEA.8010704@freebsd.org> <567421B4.6020302@ijs.si>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 18, 2015 at 7:09 AM, Mark Martinec <Mark.Martinec@ijs.si> wrote: > It would be nice to use VIMAGE, but is not in a GENERIC kernel. > Using a custom kernel voids a comfort of using freebsd-update > for installing patch revisions and upgrades. > > Mark Not really. First, most updates don't touch the kernel. Even when they do, you just need to re-build your custom kernel, a rather trivial exercise when compared to maintaining a system manually. It is easy to do the actual build on a different system and just copy it to multiple systems. It is only required for the actual kernel, not modules. You do have to keep a copy of the GENERIC kernel as /boot/GENERIC. The Handbook says "Always keep a copy of the GENERIC kernel in /boot/GENERIC. It will be helpful in diagnosing a variety of problems and in performing version upgrades." If freebsd-update calls for a reboot, this is when you need to replace /boot/kernel/kernel with your custom kernel. If the kernel was not changed, you won't be required to reboot, though I do recommend doing so to be sure that no vulnerable code is left running. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vLwAuwg6%2BwatHWPYzrrGQzL4Bm-c39KRBTQMiUEsrgGg>