From: Benjamin LaHaise <bcrl@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: klibc and logging
Date: Tue, 13 Aug 2002 13:54:05 -0400 [thread overview]
Message-ID: <20020813135405.A12730@redhat.com> (raw)
In-Reply-To: <ajbgbf$7e7$1@cesium.transmeta.com>; from hpa@zytor.com on Tue, Aug 13, 2002 at 10:41:03AM -0700
On Tue, Aug 13, 2002 at 10:41:03AM -0700, H. Peter Anvin wrote:
> Requires too much to work before it's can be made available.
>
> Andrew Morton sent me a proposed patch last night which adds a klogctl
> (a.k.a. sys_syslog) which does a printk() from userspace. It was less
> than 10 lines; i.e. probably worth it. I have hooked this up to
> syslog(3) in klibc, although the code is not checked in yet.
Rather, why not have the file descriptor early userspace gets called
with point to a file that printk's whatever is written to it? That
makes more sense as the early init stuff really should end up in the
kernel's log buffer.
-ben
--
"You will be reincarnated as a toad; and you will be much happier."
next prev parent reply other threads:[~2002-08-13 17:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 7:12 klibc and logging H. Peter Anvin
2002-08-13 7:52 ` Erik Andersen
2002-08-13 8:04 ` Alexander Viro
2002-08-13 10:12 ` Erik Andersen
2002-08-13 10:38 ` Alexander Viro
2002-08-13 14:27 ` Eric W. Biederman
2002-08-13 18:05 ` H. Peter Anvin
2002-08-13 9:42 ` Miquel van Smoorenburg
2002-08-13 17:41 ` H. Peter Anvin
2002-08-13 17:54 ` Benjamin LaHaise [this message]
2002-08-13 17:59 ` H. Peter Anvin
2002-08-13 17:55 ` Randy.Dunlap
2002-08-16 5:05 ` Oliver Xymoron
2002-08-19 13:27 ` Russell King
2002-08-19 13:59 ` H. Peter Anvin
2002-08-19 16:54 ` Russell King
2002-08-19 16:58 ` H. Peter Anvin
2002-08-19 17:25 ` Russell King
2002-08-19 17:27 ` H. Peter Anvin
2002-08-19 17:29 ` H. Peter Anvin
2002-08-19 19:37 ` Alan Cox
2002-08-19 19:40 ` H. Peter Anvin
2002-08-20 13:22 ` Thunder from the hill
2002-08-20 14:45 ` Russell King
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=20020813135405.A12730@redhat.com \
--to=bcrl@redhat.com \
--cc=hpa@zytor.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.