From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] clone files and Srv->clone
Date: Sat, 10 Dec 2005 15:40:06 -0500 [thread overview]
Message-ID: <ee9e417a0512101240k5632b620vdc26a4f5fe64970b@mail.gmail.com> (raw)
In-Reply-To: <8ccc8ba40512101014r135371c0y609a410db2e6b258@mail.gmail.com>
As Nemo points out, Srv.clone and
clone files like in the network stack
are completely different things.
In the original 9P protocol, there was
a Tclone message that was identical in
functionality to a 9P2000 Twalk with
nname==0. That's where the name
comes from.
Russ
next prev parent reply other threads:[~2005-12-10 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 17:43 Sascha Retzki
2005-12-10 18:14 ` Francisco J Ballesteros
2005-12-10 20:40 ` Russ Cox [this message]
2005-12-10 21:38 ` Francisco J Ballesteros
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=ee9e417a0512101240k5632b620vdc26a4f5fe64970b@mail.gmail.com \
--to=rsc@swtch.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).