From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ports
Date: Mon, 6 May 2002 21:31:24 -0400 [thread overview]
Message-ID: <a6b681accfa16c491953fda9c25319e8@plan9.bell-labs.com> (raw)
bunzip2 is looping. i'm not sure what it's doing.
it's Ready because you're running ps and you only
have one processor. otherwise it would be Running.
next reply other threads:[~2002-05-07 1:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 1:31 Russ Cox [this message]
2002-05-07 1:37 ` Christopher Nielsen
-- strict thread matches above, loose matches on Subject: below --
2002-05-07 1:07 Russ Cox
2002-05-07 1:15 ` Christopher Nielsen
2002-05-06 22:02 Russ Cox
2002-05-07 0:47 ` Dean Prichard
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=a6b681accfa16c491953fda9c25319e8@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).