From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] /sys/src/cmd/ps.c
Date: Thu, 2 Sep 2004 22:48:58 -0400 [thread overview]
Message-ID: <ee9e417a04090219483dd96512@mail.gmail.com> (raw)
In-Reply-To: <6f9638a5b39fcfeba12510c418feed10@plan9.escet.urjc.es>
> I've (trivially) added a "-f procdir" option to ps(1) so that I could
> use a different source for the /proc information. It would have been
> as easy to spawn a new window and import the remote /proc in it, but
> I'm sure I'm not the only person who feels they may want access to the
> local and the remote /proc simultaneously. Is it worth documenting
> the option and submit a patch?
i'd rather you just used bind.
next all the debuggers will
need the flag too. where will
it stop?
we have shorthands like /proc
and /dev/mouse and the like
for a reason.
next prev parent reply other threads:[~2004-09-03 2:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 6:44 lucio
2004-09-02 7:45 ` Fco. J. Ballesteros
2004-09-03 2:48 ` Russ Cox [this message]
2004-09-03 5:29 ` lucio
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=ee9e417a04090219483dd96512@mail.gmail.com \
--to=russcox@gmail.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).