From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: serial console (was Re: [patch] printk from userspace)
Date: Thu, 15 Aug 2002 12:43:23 +0000 (UTC) [thread overview]
Message-ID: <ajg7lb$rtr$2@ncc1701.cistron.net> (raw)
In-Reply-To: 87eld1s9l7.fsf_-_@arm.t19.ds.pwr.wroc.pl
In article <87eld1s9l7.fsf_-_@arm.t19.ds.pwr.wroc.pl>,
Arkadiusz Miskiewicz <misiek@pld.ORG.PL> wrote:
>btw. is there any reason to not display initscripts messages
>on all consoles in such setup:
>append="console=tty0 console=ttyS0,57600n8"
>serial=0,57600n8
>?
Yes. It is not implemented in the kernel and it would not
be trivial to do so (or even wanted)
>kernel messages are available on both - tty0 and ttyS0 while
>userspace messages (from initscripts) only on last specified
>- in such case ttyS0.
That's because printk() in the kernel uses a very different codepath than
the userland write(console, "hello")
Mike.
next prev parent reply other threads:[~2002-08-15 12:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-14 3:18 [patch] printk from userspace Andrew Morton
2002-08-14 3:58 ` Benjamin LaHaise
2002-08-14 4:00 ` H. Peter Anvin
2002-08-14 4:05 ` Benjamin LaHaise
2002-08-14 4:10 ` Alexander Viro
2002-08-14 4:11 ` Andrew Morton
2002-08-14 4:07 ` Benjamin LaHaise
2002-08-14 4:20 ` Alexander Viro
2002-08-14 4:26 ` Linus Torvalds
2002-08-14 4:35 ` Benjamin LaHaise
2002-08-14 4:42 ` H. Peter Anvin
2002-08-14 4:44 ` Linus Torvalds
2002-08-14 4:44 ` H. Peter Anvin
2002-08-14 4:48 ` Benjamin LaHaise
2002-08-14 4:58 ` Andrew Morton
2002-08-14 5:32 ` H. Peter Anvin
2002-08-19 11:28 ` Daniel Phillips
2002-08-14 7:59 ` Miquel van Smoorenburg
2002-08-14 16:12 ` serial console (was Re: [patch] printk from userspace) Arkadiusz Miskiewicz
2002-08-15 12:43 ` Miquel van Smoorenburg [this message]
2002-08-14 4:33 ` [patch] printk from userspace H. Peter Anvin
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='ajg7lb$rtr$2@ncc1701.cistron.net' \
--to=miquels@cistron.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox