From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] spaces in filenames
Date: Sat, 1 Jun 2002 10:01:43 -0400 [thread overview]
Message-ID: <ecb4d092e6486a09039ef6b51f86ee42@plan9.bell-labs.com> (raw)
> I got myself into trouble recently by misunderstanding the syntax
> of the kfs 'rename' command. If you do something like
>
> disk/kfscmd 'rename /tmp/xxx /tmp/yyy'
>
> you end up with a file in /tmp with slashes in its name. Exercise
> for the reader: how do you get rid of it?
That's one of the first Plan 9 mistakes I ever made.
I killed off the partition and started afresh. (Not the right answer.)
Anyhow, you didn't misunderstand the syntax.
That should have worked. That's how the
install moves your old file system into /3e.
The case where src and dst are in same
directory must use the wrong name.
Russ
next reply other threads:[~2002-06-01 14:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 14:01 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-26 18:08 smiley
2011-04-26 18:42 ` Rob Pike
2011-04-26 18:44 ` erik quanstrom
2011-04-26 18:52 ` dexen deVries
2011-04-26 19:31 ` Rob Pike
2011-04-26 19:35 ` Paul Lalonde
2011-04-27 13:10 ` Digby Tarvin
2011-04-27 13:16 ` erik quanstrom
2011-04-27 13:21 ` Steve Simon
2011-04-28 9:58 ` Peter A. Cejchan
2011-04-26 18:43 ` erik quanstrom
2011-04-27 2:30 ` smiley
2011-04-27 2:39 ` erik quanstrom
2002-06-03 12:42 presotto
2002-06-01 22:17 Russ Cox
2002-06-01 22:25 ` William Josephson
2002-06-03 10:06 ` Axel Belinfante
2002-06-01 22:16 Russ Cox
2002-06-01 14:55 Richard Miller
2002-06-01 14:16 Russ Cox
2002-06-01 14:15 Russ Cox
2002-06-01 14:10 Russ Cox
2002-06-01 14:38 ` William Josephson
2002-06-01 13:55 Richard Miller
2002-06-01 14:05 ` William Josephson
2002-06-01 13:15 ` Sam
2002-06-01 13:46 Russ Cox
2002-06-01 5:02 Geoff Collyer
2002-06-01 13:41 ` Michael Baldwin
2002-06-01 3:35 Michael Baldwin
2002-06-01 16:54 ` Digby Tarvin
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=ecb4d092e6486a09039ef6b51f86ee42@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).