From: Richard <greon@best.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rewriting paths [was: mv vs cp]
Date: Tue, 9 Oct 2001 07:19:40 -0700 [thread overview]
Message-ID: <E15qxjQ-0000m6-00@localhost> (raw)
In-Reply-To: <20011009062615.25BD719A0A@mail.cse.psu.edu>
Fco.J.Ballesteros writes:
>One thing I like in Plan 9 is that by keeping the fs alive,
>you can survive crashes on any other machine. The renamefs
>would make you more dependent on crashes not happening
>in the machine w/ renamefs before it moves everything around.
I see your point.
In renamefs's defense, I note that most users most of the time are
working on their own stuff, not making any chanages to the parts of the
network that everyone relies on. If the renamefs is running on your own
terminal or cpued to some cpu server, and your working on your own
stuff, a crash of the renamefs will not affect the other users.
Ie, do not use renamefs when you are adminning the network.
next prev parent reply other threads:[~2001-10-09 14:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <nemo@gsyc.escet.urjc.es>
2001-10-09 6:25 ` Fco.J.Ballesteros
2001-10-09 6:41 ` George Michaelson
2001-10-10 9:05 ` Douglas A. Gwyn
2001-10-09 14:19 ` Richard [this message]
2002-07-16 16:08 [9fans] useful language extension, or no? rob pike, esq.
2002-07-16 15:31 ` Sam
2002-07-16 17:24 ` [9fans] more extensions FJ Ballesteros
2002-07-16 16:26 ` Sam
2002-07-16 17:28 ` Howard Trickey
2002-07-16 17:09 ` [9fans] New language? Sam
2002-07-17 5:45 ` GBA
2002-07-17 6:23 ` Lucio De Re
2002-07-16 18:23 ` [9fans] more extensions Scott Schwartz
2002-07-16 18:47 ` Dan Cross
2002-07-16 19:05 ` Jon Snader
2002-07-17 8:58 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2001-10-07 16:23 [9fans] mv vs cp jmk
2001-10-08 17:43 ` [9fans] rewriting paths [was: mv vs cp] Richard Uhtenwoldt
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=E15qxjQ-0000m6-00@localhost \
--to=greon@best.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).