9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Rudolf Sykora" <rudolf.sykora@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] mv on directory
Date: Sat,  1 Nov 2008 15:17:06 +0100	[thread overview]
Message-ID: <a560a5d00811010717u6adefad0h9be29838a5e42ee7@mail.gmail.com> (raw)
In-Reply-To: <4C2C9539-5ABB-4230-BC8A-A1765DFC0E1C@utopian.net>

> There is dircp (in tar(1)) for moving trees around, or the long-form " @{cd
> fromdir && tar cp .} | @{cd todir && tar xT} ", if you prefer.

I know that. It's a copy, not move.

> But "behavior deviates from the similarly-named command in
> lunix" cannot be the definition of "bug."

I just can't see any reason why to mention anything about any bug. I
didn't do that.

> Again, "What should mv do to a tree that resides on multiple file servers?"

what about: mv dirA dirB ==
mkdir dirB
dircp dirA dirB
rm -r dirA

... if you are able to 'rm -r' (which also may span multiple
fileservers) than I don't see any trouble with moving the directories.
Ruda



  reply	other threads:[~2008-11-01 14:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1225540801.26550.9fans@9fans.net>
2008-11-01 13:48 ` Josh Wood
2008-11-01 14:17   ` Rudolf Sykora [this message]
2008-11-01 15:04     ` Eric Van Hensbergen
2008-11-01 21:05       ` Roman Shaposhnik
2008-11-02  2:12         ` Eric Van Hensbergen
2008-11-03  3:02           ` Roman Shaposhnik
2008-11-01 16:30 Josh Wood
2008-11-01 21:25 ` Roman Shaposhnik
  -- strict thread matches above, loose matches on Subject: below --
2008-10-31 20:15 Rudolf Sykora

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=a560a5d00811010717u6adefad0h9be29838a5e42ee7@mail.gmail.com \
    --to=rudolf.sykora@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).