From owner-freebsd-net@freebsd.org Sat Dec 19 18:30:35 2015 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E3618A4B558 for ; Sat, 19 Dec 2015 18:30:35 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B348818D6 for ; Sat, 19 Dec 2015 18:30:35 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-io0-x22f.google.com with SMTP id o67so120407727iof.3 for ; Sat, 19 Dec 2015 10:30:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=0Z+kQZXL7Ev/oIXqKaOzGqwDl9rgvAMNwvDRbmRuY+o=; b=TrjI3ItcGQkIcMdJsIEn9BCXQjwJ7zVHNkoz0D6/9v5Gmrfz8j0CgA8sLRact0ZaJ6 MuftzKmICyFXeIeICAGrRP5ctLQNZQe17QF0wDbrAQnV6eDmmkVeWD9oW3iq9O46jtbA KdNAjEVYSVXddoJfUJkWXliZ6GEBW3L2xLd4cGafUoz/MuZSrZMElE6jtvWU82SPLrGn 7Rrlvu1zw8yQHFkGEjC2zXxvrkLC7YLrtEYrGBkJeemzSBcIu24NLN+QmN7lRQghJPZL xXUzVCAFwkUe18mK/r2A0vdBLHMAyjHOXAhgKssmnmnpJOwHvxH1ttNgiQ/9Rc3p0B8+ pUag== MIME-Version: 1.0 X-Received: by 10.107.6.156 with SMTP id f28mr10729445ioi.46.1450549835067; Sat, 19 Dec 2015 10:30:35 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.36.2.16 with HTTP; Sat, 19 Dec 2015 10:30:34 -0800 (PST) In-Reply-To: <567421B4.6020302@ijs.si> References: <22131.18881.757188.951230@hergotha.csail.mit.edu> <56740DEA.8010704@freebsd.org> <567421B4.6020302@ijs.si> Date: Sat, 19 Dec 2015 10:30:34 -0800 X-Google-Sender-Auth: u9LOUn67tMg_r1cbyzc7Ss-EvvE Message-ID: Subject: Re: Per-jail private loopback From: Kevin Oberman To: Mark Martinec Cc: "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2015 18:30:36 -0000 On Fri, Dec 18, 2015 at 7:09 AM, Mark Martinec 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