From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] pprint and exportfs (and others)
Date: Wed, 17 Apr 2013 19:52:15 +0200 [thread overview]
Message-ID: <85949202d2993506b5739a15d1f1126e@proxima.alt.za> (raw)
In-Reply-To: <3012616258e3da50de2c97c070a8a39e@ladd.quanstro.net>
> there is no kprint in plan 9. neither can one
> syslog from the kernel.
I was going to be clearer, then got lazy:
-lr--r----- c 0 lucio lucio 0 Mar 21 20:44 /dev/kprint
that's the console, I've never investigated how the kernel writes to
it, but it sounds like the right place for diagnostics that should not
get mixed up with the user's stderr.
++L
next prev parent reply other threads:[~2013-04-17 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 16:52 Charles Forsyth
2013-04-17 17:35 ` lucio
2013-04-17 17:43 ` erik quanstrom
2013-04-17 17:52 ` lucio [this message]
2013-04-17 21:07 ` Charles Forsyth
2013-04-17 21:55 ` cinap_lenrek
2013-04-18 2:20 ` erik quanstrom
2013-04-20 19:15 ` cinap_lenrek
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=85949202d2993506b5739a15d1f1126e@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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).