From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org, viro@math.psu.edu
Subject: klibc and logging
Date: Tue, 13 Aug 2002 00:12:10 -0700 [thread overview]
Message-ID: <3D58B14A.5080500@zytor.com> (raw)
Okay... I think klibc is starting to get pretty much to the point where
it will need to be, although I'm sure there will be plenty of bugs once
we start using it heavily -- and it still needs RPC support code for
mounting NFS :(
However, I'm wondering what to do about logging. Kernel log messages
get stored away until klogd gets started, but early userspace may need
some way to log messages -- and syslog is obviously not running. The
easiest way to do this would probably be to be able to write to
/proc/kmsg (which probably really should be /dev/kmsg) and push messages
onto the kernel's message queue; but we could also have a dedicated
location in the initramfs for writing logs, and do it all in userspace.
In the latter case there needs to be a convention to make sure this
file is actually present in the namespace at the time syslog starts, and
of course syslog needs to know about it...
-hpa
next reply other threads:[~2002-08-13 7:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 7:12 H. Peter Anvin [this message]
2002-08-13 7:52 ` klibc and logging 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
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=3D58B14A.5080500@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox