Date: Fri, 24 Oct 2008 13:27:03 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Dag-Erling Sm??rgrav <des@des.no> Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, marcel@FreeBSD.org, Warner Losh <imp@bsdimp.com>, src-committers@FreeBSD.org Subject: Re: svn commit: r184193 - in head/sys: arm/conf conf Message-ID: <20081024132703.GA81378@FreeBSD.org> In-Reply-To: <868wsewzos.fsf@ds4.des.no> References: <200810230151.m9N1ptUe044619@svn.freebsd.org> <20081023.190942.74668946.imp@bsdimp.com> <868wsewzos.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 24, 2008 at 03:26:43AM +0200, Dag-Erling Sm??rgrav wrote: > Warner Losh <imp@bsdimp.com> writes: > > We already have a better mechanism for including config files. We > > should be using that instead of poluting another port with the > > DEFAULTS file. > > Should we even have DEFAULTS files at all? IMHO they just confuse > matters by introducing "stealth" options into your config. I tend to second this. I always try to get everything possible out of my kernel to modules, and thus was surprised to see io.ko and mem.ko fail to load because they were silently included into my custom kernel. I understand that some things like 'device isa' and 'device npx' aren't really optional, but if something is useful to have, but can be loaded as a module, it belongs to GENERIC rather than DEFAULTS. Killing the latter altogether and throwing a comment that says particular option or device is mandatory in GENERIC is probably even better (and more transparent). ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081024132703.GA81378>