Date: Fri, 10 Feb 2012 15:36:01 +0100 From: "Marek 'Buki' =?utf-8?Q?Kozlovsk=C3=BD?=" <freebsd@dev.null.cz> To: freebsd-stable@freebsd.org Subject: Re: Reducing the need to compile a custom kernel Message-ID: <20120210143601.GB42565@dev.null.cz> 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
--rQAi4ZBraoACHIeu Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 10, 2012 at 02:56:04PM +0100, Alexander Leidinger wrote: > Hi, >=20 > 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. >=20 > 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). >=20 > 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). >=20 > 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? I need (not on every machine, granted) IPSEC and MROUTING > Bye, > Alexander. >=20 > --=20 > Cheit's Lament: > If you help a friend in need, he is sure to remember you-- > the next time he's in need. >=20 > http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 > http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 Buki --rQAi4ZBraoACHIeu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk81K1EACgkQPzhIkpLLm09yJwCgyi5xAYIer0TAijygi2B1D4fC ss4AnA09mFyrmCBKV+hj2lmjnHqrky3k =07eo -----END PGP SIGNATURE----- --rQAi4ZBraoACHIeu--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120210143601.GB42565>