From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 'cd' into non-existent directory?
Date: Fri, 13 Feb 2009 08:34:54 -0500 [thread overview]
Message-ID: <ba413890765b74510c77c306e99df28c@quanstro.net> (raw)
In-Reply-To: <af4b2163-fe8b-45ff-9d3d-5e878eef0d52@w34g2000yqm.googlegroups.com>
On Fri Feb 13 08:32:56 EST 2009, pavel.klinkovsky@gmail.com wrote:
> Alternatively, if '9fs' would 'mkdir' automatically, the sequence
> would be:
> - 9fs (automatic 'mkdir' and 'mount')
> - ...usage...
> - user 'unmounts' the fs...
> - ...and the directory is still present... :-(
actually, the more likely result would be "permission denied".
you'd need to mount ramfs on /n to do it this way.
- erik
next prev parent reply other threads:[~2009-02-13 13:34 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
2009-02-13 13:25 ` Bruce Ellis
2009-02-13 13:27 ` Pavel Klinkovsky
2009-02-13 13:34 ` erik quanstrom [this message]
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=ba413890765b74510c77c306e99df28c@quanstro.net \
--to=quanstro@quanstro.net \
--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).