From: "H. Peter Anvin" <hpa@zytor.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Benjamin LaHaise <bcrl@redhat.com>,
Andrew Morton <akpm@zip.com.au>,
Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] printk from userspace
Date: Tue, 13 Aug 2002 21:33:24 -0700 [thread overview]
Message-ID: <3D59DD94.6040406@zytor.com> (raw)
In-Reply-To: Pine.GSO.4.21.0208140016140.3712-100000@weyl.math.psu.edu
Alexander Viro wrote:
>
> I have a better suggestion. How about we make write(2) on /dev/console to
> act as printk()? IOW, how about making _all_ writes to console show up in
> dmesg?
>
> Then we don't need anything special to do logging _and_ we get output
> of init scripts captured. For free. dmesg(8) would pick that up, klogd(8)
> will work as is, etc.
>
/dev/console is probably unsuitable for this (/dev/console is an
interactive device), but something like /dev/kmsg would probably be a
good idea -- it can also replace /proc/kmsg.
However, Andrew's sys_syslog() change does what I need, since users are
used to calling syslog(3) to log messages anyway.
-hpa
prev parent reply other threads:[~2002-08-14 4:29 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
2002-08-14 4:33 ` H. Peter Anvin [this message]
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=3D59DD94.6040406@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@zip.com.au \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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.