Date: Fri, 10 Feb 2012 15:52:30 +0100 From: Kristof Provost <kristof@sigsegv.be> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: stable@FreeBSD.org Subject: Re: Reducing the need to compile a custom kernel Message-ID: <20120210145230.GC10865@thebe.jupiter.sigsegv.be> In-Reply-To: <20120210145604.Horde.ewjpSpjmRSRPNSH0YRHxgAk@webmail.leidinger.net> References: <20120210145604.Horde.ewjpSpjmRSRPNSH0YRHxgAk@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2012-02-10 14:56:04 (+0100), Alexander Leidinger <Alexander@Leidinger.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120210145230.GC10865>