public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thunder from the hill <thunder@ngforever.de>
To: Stefani Seibold <stefani@seibold.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: patch for 2.4.0 disable printk
Date: Fri, 26 Jan 2001 17:09:31 -0700	[thread overview]
Message-ID: <3A7211BB.AF85D0BC@ngforever.de> (raw)
In-Reply-To: <01012612051000.01240@deepthought.seibold.net>

Stefani Seibold wrote:
> 
> Hi Linus,
> Hi Alan,
> Hi everybody,
> 
> 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.
> 
> On my system this saves about 10% of disk- and ramspace.
> 899664
> For example: My standart desktop kernel is 994834 bytes, without printk
> messages it is only 899664 bytes long. The basic kernel ram usage is also 10%
> less than the same kernel with printk messages.
> 
> Greetings,
> Stefani
> 
> BTW: this is my first try to submit a kernel patch
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...


-
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/

  reply	other threads:[~2001-01-27  8:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-26 11:05 patch for 2.4.0 disable printk Stefani Seibold
2001-01-27  0:09 ` Thunder from the hill [this message]
2001-01-27 10:57   ` Stefani Seibold
2001-01-29 17:40     ` James Simmons
2001-01-29 20:17       ` Stefani Seibold
  -- strict thread matches above, loose matches on Subject: below --
2001-01-26 20:46 Stefani Seibold
2001-01-26 21:13 ` David Weinehall
2001-01-27 22:31 Stefani Seibold
2001-01-28  0:44 ` Andrew Morton
2001-01-28  9:27   ` Stefani Seibold
2001-01-28 17:32     ` Jamie Lokier
2001-01-29  2:48   ` Paul Gortmaker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A7211BB.AF85D0BC@ngforever.de \
    --to=thunder@ngforever.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefani@seibold.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox