> More and more people are trying to use GENERIC as a template for their
> own kernels and they're losing, of course, because generic sets many
> limits (like max children or open files) too low.
> Unfortunately, every time this issue has come up in the past it's also
> followed a rather set course, in 3 distinct stages:
[ ... ]
The problem with all of these stages is fanout. No matter which
"configuration" I select (is a 4 user config ever really optimal
for *any* usage???), I need the same controllers and virtual
devices on my machine, regardless of how many vnodes I allow to
be active at one time.
The config needs to be seperated into "machine" and "usage"
portions, IMO. Maybe adding the ability to use #include (or
equivalent) is really the thing to do, instead.
Any opinions in this posting are my own and not those of my present
or previous employers.