I found the FAQ about it. Unfortunately, it is going to worry some few of my users. The FAQ does *not* mention any way to shut it up.
Clues?
On Tue, Apr 2, 2013 at 6:45 AM, m.roth@5-cent.us wrote:
I found the FAQ about it. Unfortunately, it is going to worry some few of my users. The FAQ does *not* mention any way to shut it up.
Because there is no known way to shut it up. As stated in [1], "You need to open a bug or raise a support call [with upstream]". There is nothing CentOS can do about it.
That said, it is not impossible to silence the message. You can remove the part of the kernel code that displays it and build your custom kernel.
Akemi
[1] https://www.redhat.com/archives/rhelv5-list/2013-January/msg00011.html
Akemi Yagi wrote:
On Tue, Apr 2, 2013 at 6:45 AM, m.roth@5-cent.us wrote:
I found the FAQ about it. Unfortunately, it is going to worry some few of my users. The FAQ does *not* mention any way to shut it up.
Because there is no known way to shut it up. As stated in [1], "You need to open a bug or raise a support call [with upstream]". There is nothing CentOS can do about it.
That said, it is not impossible to silence the message. You can remove the part of the kernel code that displays it and build your custom kernel.
Thanks, Akemi. It's still annoying that they'd leave what I'd call a debug statement in a production delivery.
mark
-
Akemi Yagi -
m.roth＠5-cent.us