From: Rob Pike <rob@mightycheese.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] trace.c
Date: Wed, 28 Jan 2004 07:52:38 -0800 [thread overview]
Message-ID: <FF3A3D56-51A9-11D8-B35B-000A95B984D8@mightycheese.com> (raw)
In-Reply-To: <9c52cb5940aee78cafe96acb9a2c1e0f@plan9.bell-labs.com>
On Wednesday, January 28, 2004, at 05:00 AM, Sape Mullender wrote:
>> Also realtime(3) is not there.
>
> This has been replaced by proc(4)
is there a proc(4)? or did you mean proc(3).
i can't check because yet again i am getting inexplicable auth errors
connecting to sources when auth/debug says it should work.
-rob
next prev parent reply other threads:[~2004-01-28 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 19:48 mirtchov
2004-01-27 19:58 ` Peter Bosch
2004-01-28 8:13 ` Skip Tavakkolian
2004-01-28 10:46 ` Bruce Ellis
2004-01-28 13:06 ` boyd, rounin
2004-01-28 13:00 ` Sape Mullender
2004-01-28 15:52 ` Rob Pike [this message]
2004-01-28 16:21 ` Sape Mullender
2004-01-29 1:48 ` Geoff Collyer
2004-01-29 1:56 ` Peter Bosch
2004-01-29 2:34 ` Geoff Collyer
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=FF3A3D56-51A9-11D8-B35B-000A95B984D8@mightycheese.com \
--to=rob@mightycheese.com \
--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).