I, too, have started w/GENERIC and commented out h/w I don't have; these days, I don't bother, because we have plenty of memory & disk (relatively on modern machines). AND, if you (can) stick w/GENERIC -- then you can compare against the Official Release if there are problems.
Another reason I don't often mess w/GENERIC config is: the whole 'config' mechanism seems kinda brittle. I often break a config by doing things that seem obvious to me, but don't work. My advice: Stick with GENERIC, if you can; and add in / uncomment lines for the extra support you need. On Tue, Jun 29, 2021 at 4:05 AM Todd Gruhn <[email protected]> wrote: > I have never tried writing my own NetBSD config. I always > started with GENERIC, then commented out any hardware > that is not on my system. > > On Tue, Jun 29, 2021 at 12:50 AM Martin Husemann <[email protected]> > wrote: > > > > On Mon, Jun 28, 2021 at 08:48:31PM -0400, Todd Gruhn wrote: > > > Oh, wellll > > > > I write my own kernel configs as differences to GENERIC (or something > > already based on it (arch dependend)). > > > > Like: > > > > ---8<--- > > include "arch/sparc64/conf/MODULAR" > > no spkr* at audio? > > no config netbsd > > config netbsd root on "wedge:sb2k5root" type ? > > no sbus > > no wd* at atabus? > > wd0 at atabus4 drive 0 flags 0x0f00 # disable UDMA on our SD card > thingy > > wd* at atabus? drive ? flags 0 > > options DEBUG > > options LOCKDEBUG > > --->8--- > > > > > > This is not guaranteed to be future-proof, but very easy to adapt to > later > > changes. > > > > Martin >
