All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Madhav Diwan" <mdiwan@wagweb.com>
To: <linux-kernel@vger.kernel.org>
Subject: tty stuff
Date: Wed, 14 Nov 2001 21:28:43 -0500	[thread overview]
Message-ID: <3BF3285B.D4F6EFC8@wagweb.com> (raw)

Arrrgh

How do i get the kernel messages to stop interupting my scripting? 
( YeS im editing as root .. because the files i edit are in roots
directory and are often executables.. yes i know thats bad)

I want to divert them all to the console tty1 ( why is the first console
tty1 and not tty0? )... or just not interrupt a vi session by not
posting to the screen when i am editing ?

Maybe there is a curses vi clone editor that can give me this?

Regardless is there a way to post the messages to the console tty1 ..
without having to resort to the lilo prompt .. and telling it
console=??..

also how do i log to multiple consoles .. or send only certain types of
messages .. based on the user/author of the message or content of the
message to different ttys?

Its late.. i should know this ... help


Thanks bunches in advance

Madhav


Note: The information contained in this message may be privileged and confidential and protected from disclosure.  If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.  Thank you.  Wagner Weber & Williams

                 reply	other threads:[~2001-11-15  2:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3BF3285B.D4F6EFC8@wagweb.com \
    --to=mdiwan@wagweb.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.