Thomas Schwinge <[EMAIL PROTECTED]> writes: > The only situations where this is _not_ what I'd expect from a kernel's > build system by default is when a) hunting bugs or b) building a large > number of kernels when testing specific issues (and you then only want to > compile the actually needed device drivers to save time). Are a) and b) > relevant to justify _not_ having the whole lot enabled by default?
There are also lots of cases historically where two drivers both work, but are incompatible and cannot coexist together. Sometimes these interactions are tricky. Also, drivers often have delays while waiting for devices to respond (manufacturer specs often call for things like a *one second* delay wait) and so booting can take a long time while you wait for a bunch of nonexistent devices not to respond. Thomas _______________________________________________ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd
