| 1 |
On 2013-01-22, Robin H. Johnson wrote: |
| 2 |
|
| 3 |
> I'm raising this patch because of the recent spate of bugs with the |
| 4 |
> latest udev that now fails to boot your system if CONFIG_DEVTMPFS is |
| 5 |
> not available in your kernel. |
| 6 |
> |
| 7 |
> Bugs: 408947, 409393, 437320, 453074 |
| 8 |
> |
| 9 |
> CONFIG_CHECK has not been fatal for some years now, because there turned |
| 10 |
> out to be some cases where it cannot detect what the system really has |
| 11 |
> [1], or what is returned is wrong [2]. |
| 12 |
> |
| 13 |
> However, while this is has been superb in helping those corner-cases, |
| 14 |
> the fallout is that users frequently ignore the non-fatal warnings that |
| 15 |
> a configuration option is needed to run a binary later, and end up with |
| 16 |
> weird breakage. |
| 17 |
> |
| 18 |
> This patch introduces a new option, CONFIG_CHECK_FATAL, defaulting to |
| 19 |
> enabled, that explicitly causes a die if: |
| 20 |
> - CONFIG_CHECK cannot be performed successfully. |
| 21 |
> - Any CONFIG_CHECK options fail. |
| 22 |
|
| 23 |
[...] |
| 24 |
|
| 25 |
Is there any syntax to check if something is either disabled or built as |
| 26 |
a module? One case where being fatal by default would be annoying and |
| 27 |
perhaps wrong is net-wireless/broadcom-sta, where there is no problem in |
| 28 |
having b43 and ssb as modules, as far as they are not loaded when you |
| 29 |
want to use broadcom's binary driver. |
| 30 |
|
| 31 |
(In fact, even if it is not fatal right now, the message ends up being a |
| 32 |
bit misleading, because it *can* be set.) |
| 33 |
|
| 34 |
-- |
| 35 |
Nuno Silva (aka njsg) |
| 36 |
http://njsg.sdf-eu.org/ |
Archives