On Mon, Jul 18, 2016 at 03:38:45PM +0800, Dave Young wrote:
> no printk.devkmsg= on kernel cmdline
> -> unlocked, default is off, writing to /dev/kmsg is forbidded
> -> usespace set sysctl printk.devkmsg=on
> -> writing to /dev/kmsg is allowed.
And that helps how exactly?
I don't understand why you're harping on the ratelimiting. It is a sane
default for the *default* case. Userspace should switch to its own
logging scheme when it has started anyway.
If you still want to see *all* messages, you boot with "=on" or set it
through sysctl.
So what is the problem?!
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
