From: Erik Mouw <erik@harddisk-recovery.com>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Paul Jackson <pj@sgi.com>,
Eric Masson <cool_kid@future-ericsoft.com>,
linux-kernel@vger.kernel.org
Subject: Re: Fork and Exec a process within the kernel
Date: Wed, 11 Aug 2004 14:51:13 +0200 [thread overview]
Message-ID: <20040811125113.GC10047@harddisk-recovery.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0408110743020.15953@chaos>
On Wed, Aug 11, 2004 at 07:55:52AM -0400, Richard B. Johnson wrote:
> RedHat is NOT Linux. The MAJOR-MINOR 5.1 used in RedHat for the
> console has a very serious problem for anybody doing development
> work. If there are any kernel messages, they go to __all__ open
> terminals. This means that the only "quiet" terminals that may be
> available to kill off a runaway process are available iff you can
> log in over the network.
If you don't want console messages, you just disable console at all, or
you use a serial console (using the "console=" on the kernel command
line), or you adjust the kernel console log level. Please have a look
at the "dmesg" manual page, especially the "-n" parameter. In emergency
situations, Alt-Sysrq-[0-8] will allow you to do the same (on VGA
consoles for PCs, that is. for serial consoles use Break-[0-8]).
> Most everybody I know, who does serious development work, and
> certainly those who want to control where the %*)&$#!@ kernel
> messages go, will make sure they go to the "ALT-F1" as I have
> shown.
Not all the world is a PC, there is a lot of linux beyond x86. Looks to
me like you haven't done development on embedded systems that don't
have any VGA terminal at all.
Getting kernel messages on a certain pseudo tty is just a matter of
supplying the correct "console=" paramater to the kernel. For example:
"console=tty1" will get your console output on pseudo tty 1.
Alternatively, you can configure syslog to write all kernel messages to
a pseudo tty.
> The original query was about how to make kernel messages
> go to where, i.e., what VT do they come from. I have shown
> how you can control where they go.
Here is the original question:
Thanks for the pointer! My user mode program is running. Any idea how to
control which console it shows up on?
No reference on how to get kernel messages somewhere.
> Now, if you look at the kernel source, you will note that
> just prior to attempting to exec /sbin/init, /dev/console
> is opened. This means that you can properly use whatever
> you want if you continue to use a sym-link.
That was true for linux < 2.1.71, which was released almost 7 years
ago. Things have changed. Newer kernels use the "console=" kernel
command line to select the console. With multiple the "console="
parameter, you can even have mutiple consoles.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2004-08-11 12:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 21:03 Fork and Exec a process within the kernel Eric Masson
2004-08-09 23:10 ` Paul Jackson
2004-08-10 15:22 ` Eric Masson
2004-08-10 16:21 ` Paul Jackson
2004-08-10 18:20 ` Lee Revell
2004-08-10 19:03 ` Richard B. Johnson
2004-08-11 9:51 ` Erik Mouw
2004-08-11 11:24 ` Richard B. Johnson
2004-08-11 11:41 ` Erik Mouw
2004-08-11 11:55 ` Richard B. Johnson
2004-08-11 12:51 ` Erik Mouw [this message]
2004-08-11 15:24 ` Alan Cox
2004-08-10 16:33 ` Jan-Benedict Glaw
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=20040811125113.GC10047@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=cool_kid@future-ericsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=root@chaos.analogic.com \
/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