On Fri, 6 Dec 2019, Martin Husemann wrote:

On Sat, Dec 07, 2019 at 06:30:55AM +1100, matthew green wrote:
Why? I consider this totaly useless bloat, what was wrong with the boot.cfg

policy:  no default modules in the installation unless licenses
issues force such, until module+kernel solution.

OK, but this is gone awry. The boot.cfg solution is great if anoyne
really needs this dmesg sugar, everyone else can go on using pcictl
later instead.

If they need the sugar they can always edit their own /etc/boot.cfg
and/or drop to the boot loader and manually load the module.

So now the (reasonable) policy forces a (relatively harmless, as easily
overidable but still useless) change into bloat for everyone. Can we
just revert to the state before the initial boot.cfg change instead?

Agreed.  No need to bloat for everyone, just bloat-on-demand (as
above, or build a local kernel with ``options PCIVERBOSE'' defined).

| Paul Goyette       | PGP Key fingerprint:     | E-mail addresses:     |
| (Retired)          | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com     |
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org   |

Reply via email to