From: Stefani Seibold <stefani@seibold.net>
To: James Simmons <jsimmons@suse.com>
Cc: Thunder from the hill <thunder@ngforever.de>,
linux-kernel@vger.kernel.org
Subject: Re: patch for 2.4.0 disable printk
Date: Mon, 29 Jan 2001 21:17:54 +0100 [thread overview]
Message-ID: <01012921175400.01429@deepthought.seibold.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0101290938560.6646-100000@euclid.oak.suse.com>
In-Reply-To: <Pine.LNX.4.21.0101290938560.6646-100000@euclid.oak.suse.com>
Am Montag, 29. Januar 2001 18:40 schrieb James Simmons:
> > 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.
>
> What do you suggest we do with /dev/console and stdin, stdout, stderr?
> The kernel needs a /dev/console to boot with.
This patch does not modify the /dev/console, nor stdin/stdout/stderr. I think
you should try it, bevor you are posting...
-
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/
next prev parent reply other threads:[~2001-01-29 20:19 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
2001-01-27 10:57 ` Stefani Seibold
2001-01-29 17:40 ` James Simmons
2001-01-29 20:17 ` Stefani Seibold [this message]
-- 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=01012921175400.01429@deepthought.seibold.net \
--to=stefani@seibold.net \
--cc=jsimmons@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder@ngforever.de \
/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