From: Russ Cox <russcox@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] an idea
Date: Mon, 26 Apr 2004 12:59:10 -0400 [thread overview]
Message-ID: <C95F3C78.4E79259B@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0404260945260.28350-100000@maxroach.lanl.gov>
> These are neat ideas but there is one thing I still like about '#' -- it
> distinguishes what for me is non-private stuff from private stuff. I.e. in
> my (probably too simplistic) way of thinking, all the '#' stuff in
> addition to being devices means 'if bound in a name space, it's common to
> all'. If all the # stuff becomes things in /srv we'll lost the distinction
no it doesn't. #d. #c/user. etc.
i think what you're really getting at is that # always
means what you want it to mean and not what your
parent process set it up to mean. and yes, there is
a tension between really getting the recursion right
and being able to do this. but a convention that
/srv/sharp was always the root of the name space
would be enough. even now, #p doesn't always
means the process table. sometimes it means
"you're running RFNOMT -- go away."
next prev parent reply other threads:[~2004-04-26 16:59 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-11 19:14 [9fans] german keymap Scusi
2004-04-11 19:28 ` boyd, rounin
2004-04-11 20:00 ` Scusi
2004-04-11 20:03 ` boyd, rounin
2004-04-11 22:10 ` Geoff Collyer
2004-04-11 22:39 ` Russ Cox
2004-04-11 22:55 ` Geoff Collyer
2004-04-12 0:01 ` Russ Cox
2004-04-12 0:06 ` Geoff Collyer
2004-04-12 0:22 ` Charles Forsyth
2004-04-12 2:42 ` boyd, rounin
2004-04-12 2:57 ` countryjoe
2004-04-12 4:02 ` boyd, rounin
2004-04-12 2:40 ` boyd, rounin
2004-04-12 2:35 ` boyd, rounin
2004-04-12 2:33 ` boyd, rounin
2004-04-21 17:43 ` rog
2004-04-21 17:44 ` boyd, rounin
2004-04-21 17:56 ` rog
2004-04-21 18:03 ` boyd, rounin
2004-04-21 18:41 ` rog
2004-04-21 18:42 ` Rob Pike
2004-04-21 19:16 ` rog
2004-04-21 18:43 ` boyd, rounin
2004-04-21 18:47 ` boyd, rounin
2004-04-21 18:57 ` Rob Pike
2004-04-21 18:58 ` boyd, rounin
2004-04-21 19:20 ` rog
2004-04-21 19:58 ` boyd, rounin
2004-04-21 20:26 ` rog
2004-04-21 21:26 ` [9fans] an idea rog
2004-04-26 7:57 ` Fco.J.Ballesteros
2004-04-26 8:04 ` Charles Forsyth
2004-04-26 8:10 ` Fco.J.Ballesteros
2004-04-26 8:13 ` Charles Forsyth
2004-04-26 16:41 ` rog
2004-04-26 16:43 ` Charles Forsyth
2004-04-26 16:57 ` rog
2004-04-26 16:48 ` Fco.J.Ballesteros
2004-04-27 1:44 ` Scott Schwartz
2004-04-27 6:43 ` Fco.J.Ballesteros
2004-04-26 15:12 ` Russ Cox
2004-04-26 15:49 ` ron minnich
2004-04-26 16:42 ` rog
2004-04-26 16:59 ` Russ Cox [this message]
2004-04-26 17:05 ` Charles Forsyth
2004-04-26 18:04 ` Philippe Anel
2004-04-26 18:16 ` rog
2004-04-26 18:36 ` Philippe Anel
2004-04-26 20:27 ` rog
2004-04-27 7:44 ` Philippe Anel
2004-04-27 8:13 ` Fco.J.Ballesteros
2004-04-26 18:20 ` rog
2004-04-26 18:09 ` rog
2004-04-26 18:44 ` [9fans] local 9p multiplexing Russ Cox
2004-04-26 18:54 ` [9fans] remote " Russ Cox
2004-04-26 19:44 ` rog
2004-04-28 17:37 ` [9fans] Vmware-4 and Plan 9 Ishwar Rattan
2004-04-28 17:58 ` Hugo Santos
2004-04-28 18:01 ` vic zandy
2004-04-26 18:55 ` [9fans] an idea Charles Forsyth
2004-04-26 20:12 ` rog
2004-04-26 20:40 ` Charles Forsyth
2004-04-26 23:26 ` rog
2004-04-26 19:51 ` ron minnich
2004-04-26 20:49 ` Charles Forsyth
2004-04-22 1:57 ` [9fans] german keymap Michael Jeffrey
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=C95F3C78.4E79259B@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).