re: Include DaynaPort by default in GENERIC?

> options         SYSVMSG         # System V message queues
> options         SYSVSEM         # System V semaphores
> options         SYSVSHM         # System V shared memory

you can't use a bunch of random pkgsrc stuff without these.

> options         USERCONF        # userconf(4) support
> <probably not ever used *at all* on sparc)

i used it a year or so ago.

> options         SYSCTL_INCLUDE_DESCR    # Include sysctl descriptions in=
 kernel
> <I never understood why we included the description strings in the first=
 place>

agreed.

[ ... ]

the problem is that modules aren't complete yet, and we have a general
policy in netbsd that modules should be avoided unless there are really
good reason like licensing.  that's the reason why GENERIC is still the
default kernel on amd64, not the MODULAR one.

the general fix is to match kernels and their modules together, not to
assume that some specific versioned path is the right thing, which
means that i can't go back to an slightly odler version that has the
same ABI version, the module has been replaced entirely with something
that may not be broken and i need additional recovery..

ie, the main problem is that when something goes wrong, it sucks to
recover from.  i'd rather give up /rescue than use modules for most
things... modules can break before i can even /rescue.


i'm inclined to add dse, but also to add a SUN4 and SUN4C kernel that
we build and offer (like GENERIC.MP).  that at least makes it possible
to create installs for these very limited systems.. (i always strove
to get my sun4c's to max ram :-)


.mrg.