From: Russ Cox <russcox@gmail.com>
To: Sergey Reva <rs_rlab@mail.ru>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] srv to stdin, stdout
Date: Sat, 28 May 2005 14:24:14 -0400 [thread overview]
Message-ID: <ee9e417a05052811248dd30ea@mail.gmail.com> (raw)
In-Reply-To: <3028305906.20050528205558@mail.ru>
Oh, of course. If you're using stdin and stdout for
9P conversations, then you can't also print
debugging messages to standard out. The
kernel will think they are 9P messages and get all
confused.
Russ
prev parent reply other threads:[~2005-05-28 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 14:12 Sergey Reva
2005-05-28 16:34 ` Russ Cox
2005-05-28 17:55 ` Sergey Reva
2005-05-28 18:24 ` Russ Cox [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=ee9e417a05052811248dd30ea@mail.gmail.com \
--to=russcox@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=rs_rlab@mail.ru \
/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).