Date: Mon, 11 Mar 2019 09:35:57 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: samir.otmane@numericable.fr, freebsd-questions@freebsd.org Subject: Re: Barebone kernel options request Message-ID: <44lg1lbkjm.fsf@be-well.ilk.org> In-Reply-To: <23686.24032.265558.282058@jerusalem.litteratus.org> (Robert Huff's message of "Mon, 11 Mar 2019 09:08:48 -0400") References: <ea-mime-5c8509f6-a788-2c4256bf@webmail.numericable.fr> <20190311080756.6191bb55.freebsd@edvax.de> <23686.24032.265558.282058@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Huff <roberthuff@rcn.com> writes: > Polytropon writes: > >> You will then make a copy of the GENERIC kernel configuration file >> and adjust it to your needs, i. e., remove all the entries you do >> not need. > > Proceed with caution here. > I do not know if it is currently true, but it has in the past > been the case that (e.g.) option Q depends on device F which depends > on device B; while the relationship between Q and F is documented in > the config file, the one between F and B is not. > The easy targets are disk(/RAID) drivers and network cards. > After that? Stay alert; trust no-one; keep your un-delete key handy. Furthermore, just because there isn't a dependency today doesn't mean there won't be one next year. This doesn't happen often, and it can still happen if you go the nodevice route, but it's still a bit safer to include all of GENERIC and remove things from there.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44lg1lbkjm.fsf>