Date: Fri, 10 Feb 2012 16:05:06 +0100 From: Andreas Nilsson <andrnils@gmail.com> To: =?ISO-8859-1?Q?Marek_=27Buki=27_Kozlovsk=FD?= <freebsd@dev.null.cz> Cc: freebsd-stable@freebsd.org Subject: Re: Reducing the need to compile a custom kernel Message-ID: <CAPS9%2BSuX5yDA1VZMF61V9iYzjCdWm8=VqgNgB09nz17_wqirPw@mail.gmail.com> In-Reply-To: <20120210143601.GB42565@dev.null.cz> References: <20120210145604.Horde.ewjpSpjmRSRPNSH0YRHxgAk@webmail.leidinger.net> <20120210143601.GB42565@dev.null.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
2012/2/10 Marek 'Buki' Kozlovsk=FD <freebsd@dev.null.cz> > On Fri, Feb 10, 2012 at 02:56:04PM +0100, 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? > > I need (not on every machine, granted) IPSEC and MROUTING > > > Bye, > > Alexander. > > > > -- > > Cheit's Lament: > > If you help a friend in need, he is sure to remember you-- > > the next time he's in need. > > > > http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063= FE7 > > http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077= 137 > > Buki > IPFIREWALL_DEFAULT_TO_ACCEPT, DEVICE_POLLING and HZ=3D1000. /Andreas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPS9%2BSuX5yDA1VZMF61V9iYzjCdWm8=VqgNgB09nz17_wqirPw>