Re: patch for 2.4.0 disable printk

[Stefani Seibold <stefani@seibold.net>]

You are right... this patch make no sense on a computer system with human 
interactions. But think on tiny hidden computers, like in a dishwasher or a 
traffic light. This computer are standalone, if it crash, then it will be 
rebooted.
Nobody will attach a terminal to this kind of computer, nobody is interessted 
on a logfile. Nobody will see a oops, because nobdy is there. 
The hardware of this computer are espacilly designed and will never be 
changed. It is not like a pc, where many different hardware will be attached.
Believe me, i am programming embedded systems since 10 years... i know this 
buissines.
It is also a fine thing for rescued disk, where you never have enough space 
to put all the tools togetehr which are needed.
And rememberf: It is an option, you should it only use, iof u know what u do, 
like many other building a kernel.

Greetings,
Stefani

> What sense does it make to ripp the kernel off its "tongue"? This means
> to make it completely silent, a oops() could _not_ be noticed! This
> means that you don't know when your system has nearly crashed.
> You'd better leave printk where it is.
>
> Thunder
> ---
> Woah... I did a "cat /boot/vmlinuz >> /dev/audio" - and I think I heard
> god...
> Stefani Seibold wrote:
> > this kernel patch allows to disable all printk messages, by overloading
> > the printk function with a dummy printk macro.
> >
> > This patch is usefull for embedded systems, where the hardware never
> > changes and normaly no textconsole is attachted nor any user will see the
> > boot messages. Also, it is nice for rescue disks.
> >
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/