mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Erik Mouw <erik@harddisk-recovery.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 07:55:52 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0408110743020.15953@chaos> (raw)
In-Reply-To: <20040811114100.GB10047@harddisk-recovery.nl>

On Wed, 11 Aug 2004, Erik Mouw wrote:

> On Wed, Aug 11, 2004 at 07:24:42AM -0400, Richard B. Johnson wrote:
> > On Wed, 11 Aug 2004, Erik Mouw wrote:
> > > Please don't mislead newbies, Richard. /dev/console is NOT a link to
> > > /dev/tty0, it's a completely different device:
> > >
> > > erik@abra2:~ >ls -l /dev/console
> > > crw-------    1 root     tty        5,   1 Apr  7 09:13 /dev/console
> > > erik@abra2:~ >ls -l /dev/tty0
> > > crw-------    1 root     tty        4,   0 Feb 10  2000 /dev/tty0
> > >
> >
> > Bullshit. I know how to use `file`.
> >
> > Script started on Wed Aug 11 07:21:39 2004
> > # file /dev/console
> > /dev/console: symbolic link to /dev/tty0
>
> It might be a symlink on your machine, but that doesn't mean it's the
> right way. For almost 7 years, /dev/console is a separate device, not a
> symlink. Here's the relevant section from Documentation/devices.txt:
>
>   The console device, /dev/console, is the device to which system
>   messages should be sent, and on which logins should be permitted in
>   single-user mode.  Starting with Linux 2.1.71, /dev/console is managed
>   by the kernel; for previous versions it should be a symbolic link to
>   either /dev/tty0, a specific virtual console such as /dev/tty1, or to
>   a serial port primary (tty*, not cu*) device, depending on the
>   configuration of the system.
>
> Linux-2.1.71 was released on December 4, 1997. In your signature you
> claim to run linux-2.4.26. Please update your system.
>
>
> Erik

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.

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

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.


Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2004-08-11 11:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 21:03 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 [this message]
2004-08-11 12:51                 ` Erik Mouw
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=Pine.LNX.4.53.0408110743020.15953@chaos \
    --to=root@chaos.analogic.com \
    --cc=cool_kid@future-ericsoft.com \
    --cc=erik@harddisk-recovery.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.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

all inboxes | Powered by JetHome®