From owner-freebsd-questions@freebsd.org Mon Mar 11 13:43:17 2019 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE149154393D for ; Mon, 11 Mar 2019 13:43:16 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id 5AB3396919 for ; Mon, 11 Mar 2019 13:43:16 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from lowell-desk.be-well.ilk.org (router.lan [172.30.250.2]) by be-well.ilk.org (Postfix) with ESMTP id 3419033C22; Mon, 11 Mar 2019 09:35:58 -0400 (EDT) Received: by lowell-desk.be-well.ilk.org (Postfix, from userid 1147) id 998F8150C488; Mon, 11 Mar 2019 09:35:57 -0400 (EDT) From: Lowell Gilbert To: samir.otmane@numericable.fr, freebsd-questions@freebsd.org Subject: Re: Barebone kernel options request References: <20190311080756.6191bb55.freebsd@edvax.de> <23686.24032.265558.282058@jerusalem.litteratus.org> Date: Mon, 11 Mar 2019 09:35:57 -0400 In-Reply-To: <23686.24032.265558.282058@jerusalem.litteratus.org> (Robert Huff's message of "Mon, 11 Mar 2019 09:08:48 -0400") Message-ID: <44lg1lbkjm.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-Rspamd-Queue-Id: 5AB3396919 X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [1.77 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.37)[0.369,0]; NEURAL_HAM_LONG(-0.07)[-0.072,0]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[ilk.org]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.57)[0.571,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: be-well.ilk.org]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7922, ipnet:23.30.0.0/15, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.09)[ip: (0.09), ipnet: 23.30.0.0/15(0.07), asn: 7922(-0.55), country: US(-0.07)] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2019 13:43:17 -0000 Robert Huff 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.