From owner-freebsd-stable@FreeBSD.ORG Fri Feb 10 14:52:32 2012 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D57441065672 for ; Fri, 10 Feb 2012 14:52:32 +0000 (UTC) (envelope-from kp@sigsegv.be) Received: from mercury.codepro.be (mercury.codepro.be [IPv6:2001:4b98:dc0:51:216:3eff:feb7:3147]) by mx1.freebsd.org (Postfix) with ESMTP id 6454B8FC0A for ; Fri, 10 Feb 2012 14:52:32 +0000 (UTC) Received: from adrastea.jupiter.sigsegv.be (adrastea.jupiter.sigsegv.be [IPv6:2001:6f8:1498:1::3]) by mercury.codepro.be (Postfix) with ESMTP id 331E910D; Fri, 10 Feb 2012 15:52:31 +0100 (CET) Received: from thebe.jupiter.sigsegv.be (thebe.jupiter.sigsegv.be [172.16.1.5]) by adrastea.jupiter.sigsegv.be (Postfix) with ESMTP id 92282BD46; Fri, 10 Feb 2012 15:52:30 +0100 (CET) Received: by thebe.jupiter.sigsegv.be (Postfix, from userid 1000) id 65D4EBEA9; Fri, 10 Feb 2012 15:52:30 +0100 (CET) Date: Fri, 10 Feb 2012 15:52:30 +0100 From: Kristof Provost To: Alexander Leidinger Message-ID: <20120210145230.GC10865@thebe.jupiter.sigsegv.be> References: <20120210145604.Horde.ewjpSpjmRSRPNSH0YRHxgAk@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120210145604.Horde.ewjpSpjmRSRPNSH0YRHxgAk@webmail.leidinger.net> X-PGP-Fingerprint: E114 D9EA 909E D469 8F57 17A5 7D15 91C6 9EFA F286 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: stable@FreeBSD.org Subject: Re: Reducing the need to compile a custom kernel X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2012 14:52:32 -0000 On 2012-02-10 14:56:04 (+0100), Alexander Leidinger wrote: > The question is, is this enough? Or asked differently, why are you > compiling a custom kernel in a production environment (so I rule out > debug options zhich are not enabled in GENERIC)? Are there options > which you add which you can not add as a module (SW_WATCHDOG comes > to my mind)? If yes, which ones and how important are they for you? > VIMAGE and IPSEC I currently "require" both of them. The VIMAGE is sort of optional. I could run everything unjailed, but I prefer this. IPSEC is required, unless I add a separate device. That's for a little home gateway (HP Microserver thingy), doing file serving (NFS/ZFS), mail, web, backup, ... Regards, Kristof