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
> > solution?
> 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.

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?


Reply via email to