Well, replace "load kernel" with "boot system", and we're in violent
agreement :-)
> So we can fix it in userspace, and decided a sensible non-zero default
> there, but are somehow incapable of doing that *inside* the kernel? Sorry,
> I don't buy that.
No, you still have to make a guess, but you don't need to involve
the kernel. (I think Redmond owns most of the intellectual property
on "if you don't know where to put it, put it in the kernel, for it
will be faster and more secure that way", so we shouldn't use this
paradigm too often :-)
Since choosing this default is something between the distribution
maker and the user, they can
- choose to leave it silent ("expert mode")
- perhaps use other information they've gathered at install time
- reuse old stored settings (e.g. look for an aumixrc)
- pop up a dialog
- print a warning
etc.
> The old "document the bugs" arguement.
;-) True, but in this case, you're very likely to run into problems
if you don't religiously follow Documentation/Changes anyway. And
there are people I fully expect to read this line by line - namely
the distribution makers. And they're exactly the ones who need to
be aware of this issue.
> Bugs should be fixed, not documented.
It's a feature :-)
- Werner
-- _________________________________________________________________________ / Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net / /_http://www.almesberger.net/____________________________________________/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/