From: Dan Malek <dan@mvista.com>
To: Rod Boyce <rod_boyce@DMCWave.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Redirecting printk to a file
Date: Tue, 31 Jul 2001 20:11:28 -0400 [thread overview]
Message-ID: <3B674930.EAD7ED1C@mvista.com> (raw)
In-Reply-To: 9DCCE20055ACD311BBE200104B08D8340127490D@EXCHWENZ01
Rod Boyce wrote:
> We are having a bit of a quandary we are trying to redirect the output of
> printk
Don't assign a system console, or bump the loglevel real high.
Then just use the syslog daemon to move it from the kernel circular
buffer to a file. This is all standard Linux stuff.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-01 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 23:51 Redirecting printk to a file Rod Boyce
2001-08-01 0:11 ` Dan Malek [this message]
2001-08-01 13:30 ` James Petterson
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=3B674930.EAD7ED1C@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rod_boyce@DMCWave.com \
/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.