From: Jacob Todd <jaketodd422@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Q: moving directories? hard links?
Date: Fri, 15 Apr 2011 22:40:43 -0400 [thread overview]
Message-ID: <BANLkTimMYN+2zJ-eWvcx+jJgQBjL7yLB4Q@mail.gmail.com> (raw)
In-Reply-To: <8662qej52i.fsf@cmarib.ramside>
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
dircp and bind(1).
On Apr 15, 2011 10:39 PM, <smiley@zenzebra.mv.com> wrote:
> Hello,
>
> I've been about Plan 9... there are lots of goodies there under
> /sys/doc. However, I have a couple of lingering questions that don't
> seem to be answered anywhere:
>
> Observation 1: There doesn't seem to be any provision for moving a
> directory from one directory into another directory; that is, moving
> it to a different directory on the same <type,device> file system.
>
> Observation 2: There doesn't seem to be any support for hard links.
>
> My questions:
>
> Are these features, in fact, unsupported? Or did I overlook something?
>
> If they're unsupported, why? Were they simply overlooked? Are there
> compelling technical or theoretical reasons for not providing them?
>
> Are there any proposals afoot to implement either of these features? If
> not, are there any workarounds (besides cp&&rm and bind, respectively)?
>
> I've checked the docs under /sys/doc, the man pages, the 9fans archives,
> and the googleweb, but I can't seem to find any explanation for these
> two properties. (The case for omitting symlinks, I think is obvious:
> they make most file-related utilities 3x more complicated than they
> would be otherwise.)
>
> --
> +---------------------------------------------------------------+
> |E-Mail: smiley@zenzebra.mv.com PGP key ID: BC549F8B|
> |Fingerprint: 9329 DB4A 30F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B|
> +---------------------------------------------------------------+
>
[-- Attachment #2: Type: text/html, Size: 1962 bytes --]
next prev parent reply other threads:[~2011-04-16 2:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 2:36 smiley
2011-04-16 2:40 ` Jacob Todd [this message]
2011-04-16 4:22 ` ron minnich
2011-04-16 16:53 ` erik quanstrom
2011-04-16 17:33 ` smiley
2011-04-16 17:51 ` erik quanstrom
2011-04-21 15:32 ` smiley
2011-04-21 15:43 ` ron minnich
2011-04-16 18:22 ` Bakul Shah
2011-04-21 15:44 ` smiley
2011-04-21 15:49 ` ron minnich
2011-04-21 16:54 ` Bakul Shah
2011-04-21 20:17 ` Richard Miller
2011-04-21 21:10 ` Bakul Shah
2011-04-21 22:41 ` erik quanstrom
2011-04-21 23:17 ` ron minnich
2011-04-21 23:54 ` Bakul Shah
2011-04-21 23:55 ` erik quanstrom
2011-04-22 0:01 ` ron minnich
2011-04-22 0:04 ` erik quanstrom
2011-04-22 8:03 ` Bakul Shah
2011-04-22 8:27 ` dexen deVries
2011-04-22 13:05 ` erik quanstrom
2011-04-22 17:47 ` Bakul Shah
2011-04-24 18:58 ` erik quanstrom
2011-04-16 18:03 ` Richard Miller
2011-04-16 18:17 ` Skip Tavakkolian
2011-04-16 18:56 ` Rob Pike
2011-04-18 9:08 ` Aharon Robbins
2011-04-18 12:41 ` erik quanstrom
2011-04-18 12:59 ` Lucio De Re
2011-04-18 13:00 ` erik quanstrom
2011-04-18 13:11 ` Lucio De Re
2011-04-23 3:48 ` Ethan Grammatikidis
2011-04-21 9:22 ` Balwinder S Dheeman
2011-04-16 16:58 ` erik quanstrom
2011-04-19 15:36 ` Charles Forsyth
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=BANLkTimMYN+2zJ-eWvcx+jJgQBjL7yLB4Q@mail.gmail.com \
--to=jaketodd422@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).