From owner-freebsd-stable@FreeBSD.ORG Fri Feb 10 16:06:22 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 BA792106566B for ; Fri, 10 Feb 2012 16:06:22 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from phoenix.eternamente.info (phoenix.eternamente.info [109.169.62.232]) by mx1.freebsd.org (Postfix) with ESMTP id 612D98FC0C for ; Fri, 10 Feb 2012 16:06:22 +0000 (UTC) Received: by phoenix.eternamente.info (Postfix, from userid 80) id 8D2421CC6F; Fri, 10 Feb 2012 12:48:36 -0300 (BRT) Received: from 187.115.182.229 (SquirrelMail authenticated user matheus) by eternamente.info with HTTP; Fri, 10 Feb 2012 13:48:36 -0200 Message-ID: <83648209d86469fa1da8ab36ad067f08.squirrel@eternamente.info> In-Reply-To: <20120210145604.Horde.ewjpSpjmRSRPNSH0YRHxgAk@webmail.leidinger.net> References: <20120210145604.Horde.ewjpSpjmRSRPNSH0YRHxgAk@webmail.leidinger.net> Date: Fri, 10 Feb 2012 13:48:36 -0200 From: "Nenhum_de_Nos" User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal 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 16:06:22 -0000 On Fri, February 10, 2012 11:56, Alexander Leidinger wrote: > Hi, > > during some big discussions in the last monts on various lists, one of > the problems was that some people would like to use freebsd-update but > can't as they are using a custom kernel. With all the kernel modules > we provide, the need for a custom kernel should be small, but on the > other hand, we do not provide a small kernel-skeleton where you can > load just the modules you need. > > This should be easy to change. As a first step I took the generic > kernel and removed all devices which are available as modules, e.g. > the USB section consists now only of the USB_DEBUG option (so that the > module is build like with the current generic kernel). I also removed > some storage drivers which are not available as a module. The > rationale is, that I can not remove CAM from the kernel config if I > let those drivers inside (if those drivers are important enough, > someone will probably fix the problem and add the missing pieces to > generate a module). > > Such a kernel would cover situations where people compile their own > kernel because they want to get rid of some unused kernel code (and > maybe even need the memory this frees up). > > 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? Its a great thing this Alexander, but for me mainly I need PF+ALTQ and soekris stuff (apart from things other said before). matheus -- We will call you Cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style