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