From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] fossil flushthread message
Date: Mon, 20 Mar 2006 17:11:44 +0100 [thread overview]
Message-ID: <8ccc8ba40603200811m7d2d00bem1155c167a5338fda@mail.gmail.com> (raw)
In-Reply-To: <441ECFF3.1040404@lanl.gov>
We do that a lot.
Specially useful when getting lots of planb debug messages :-)
On 3/20/06, Ronald G Minnich <rminnich@lanl.gov> wrote:
>
> I don't know if anyone else does this but ...
>
> I frequently pop up a rio window and put
> cat /dev/kprint
> in it to catch this fluff.
>
> Useful for unattended systems.
>
> ron
>
>
prev parent reply other threads:[~2006-03-20 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 8:57 kazumi iwane
2006-03-19 9:00 ` Federico Benavento
2006-03-20 15:53 ` Ronald G Minnich
2006-03-20 16:11 ` Francisco J Ballesteros [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=8ccc8ba40603200811m7d2d00bem1155c167a5338fda@mail.gmail.com \
--to=nemo@lsub.org \
--cc=9fans@cse.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;
as well as URLs for NNTP newsgroup(s).