On 1/22/2013 05:56, Rich Freeman wrote:
On Tue, Jan 22, 2013 at 6:11 AM, viv...@gmail.com <viv...@gmail.com> wrote:
IMHO the number of cases where CONFIG_CHECK is reliable is so small that
making it fatal will only bloat make.conf and env with a new var for most
users.
Tend to agree. I just got an elog out of udisks complaining about
USB_SUSPEND not being set, and I have no idea why I'd need that on a
system that is powered 24x7. Even the kernel docs suggest that it
should be disabled if users aren't sure if they need it.
Maybe we need some way to distinguish between must-have and
nice-to-have situations? Clearly failure to boot is in a different
category than not-able-to-suspend.
Rich
I agree. During an update recently, I noticed that qemu complains if
KVM_INTEL isn't set on an AMD CPU. Making this fatal would be stupid,
but then nobody who runs qemu-kvm would ever get a fatal error about
missing DEVTMPFS.
--
♫Dustin
