From: Anthony Sorace <anothy@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 'cd' into non-existent directory?
Date: Fri, 13 Feb 2009 07:28:09 -0500 [thread overview]
Message-ID: <509071940902130428v1393b513n1c448717dfa3dec@mail.gmail.com> (raw)
In-Reply-To: <191fc5b1-2403-4b78-90bc-d31839dfd823@33g2000yqm.googlegroups.com>
9fs, for example.
i can do '9fs arbitrary-machine', and not have to worry about whether
/n/arbitrary-machine has been created ahead of time or now. that's the
most common use. without it, you'd have to create mount points in
advance of knowing what sets of things you'd want to mount.
it has downsides, like your "phantom cd", which is why it's only used
where it makes sense.
next prev parent reply other threads:[~2009-02-13 12:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 10:23 Pavel Klinkovsky
2009-02-13 10:39 ` Felipe Bichued
2009-02-13 10:40 ` Gorka Guardiola
2009-02-13 11:48 ` Pavel Klinkovsky
2009-02-13 12:28 ` Anthony Sorace [this message]
2009-02-13 13:25 ` Bruce Ellis
2009-02-13 13:27 ` Pavel Klinkovsky
2009-02-13 13:34 ` erik quanstrom
2009-02-13 14:17 ` Bruce Ellis
2009-02-13 20:21 ` Skip Tavakkolian
2009-02-15 20:33 ` Bruce Ellis
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=509071940902130428v1393b513n1c448717dfa3dec@mail.gmail.com \
--to=anothy@gmail.com \
--cc=9fans@9fans.net \
/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).