Andi Kleen wrote:
I can see where you're coming from, but logically, this is wrong.
There's a huge slew of enterprise machines that only have DVD on SATA.
... and enterprise systems don't really care about a few KB more of code.
In fact you definitely want to have SATA compiled in in case you need
to recover the machine later when the SAN is down.
On the other hand, all of these machines will have SCSI disk devices on
various other transports, so no harm is done, it's just an inelegant
solution.
Do you know of a better one?
Let's step back a moment and consider the actual scale and impact of the
problem at hand.
The vast majority of users are consumers of pre-compiled kernels, built
by People With Clue(tm), who figured this stuff out as soon as it was
introduced.
The current setup expresses the dependencies as they exist -- OPTIONAL
extras, and that is a problem once a year or so, when someone builds
their own kernel but must learn this fact anew.
There is simply no compelling need at all to change things from the
current setup.
Our Kconfig system is for people who already know the kernel, not Aunt
Tillie.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
