From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@googlegroups.com
Subject: Re: todo
Date: Fri, 1 Apr 2011 02:12:26 +0100 [thread overview]
Message-ID: <B2FE32F0-9A14-4389-9298-14D257476339@fastmail.fm> (raw)
In-Reply-To: <AANLkTikvqCyMdbnn2F9v0+k6HxzLXzMEedSeMDY1uZBc@mail.gmail.com>
On 1 Apr 2011, at 1:59 am, Uriel wrote:
> On Thu, Mar 31, 2011 at 5:30 PM, Ethan Grammatikidis
> <eekee57@fastmail.fm> wrote:
>>
>> On 30 Mar 2011, at 9:02 pm, cinap_lenrek@gmx.de wrote:
>>>
>>> - add Tmove to 9p and fileservers
>
> This is plain gratuitous idiotic protocol breaking, you can do the
> same thing simply by providing an alternative attach name with ctl
> file(s) for fancy things like moving stuff around.
I always remember an example of network filesharing from the Labs:
you have foo's files under /n/foo and foo has bar's files under /n/
bar so you can access bar's files via /n/foo/n/bar without having to
set up permissions or whatever to directly access bar, and the
example carried on to show 4 or 5 levels. I think the example was in
V6 or V7 Unix's docs, maybe V8's or something.
In such a setup and given an alternative attach point you'd have to
double the work of every mount - or more like double the number of
things which could be forgotten, no?
next prev parent reply other threads:[~2011-04-01 1:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <405d44d0ddf24c71ff94c72804f03bec@gmx.de>
2011-03-30 20:57 ` todo Stanley Lieber
2011-03-30 22:39 ` todo cinap_lenrek
2011-03-30 22:46 ` todo Stanley Lieber
2011-03-30 22:04 ` todo uriel
2011-04-01 0:30 ` todo Ethan Grammatikidis
2011-04-01 0:47 ` todo Jacob Todd
2011-04-01 0:59 ` todo Uriel
2011-04-01 1:12 ` Ethan Grammatikidis [this message]
2011-04-01 4:40 ` todo aiju
2011-04-01 7:04 ` todo Uriel
2011-04-01 7:13 ` todo cinap_lenrek
2011-04-01 9:30 ` todo Uriel
2011-04-01 10:18 ` todo cinap_lenrek
2011-04-01 10:24 ` todo Uriel
2011-04-01 11:38 ` todo cinap_lenrek
2011-04-01 13:36 ` todo Ethan Grammatikidis
2011-04-01 13:54 ` todo Julius Schmidt
2011-04-01 17:41 ` todo Uriel
2011-04-01 19:02 ` todo Ethan Grammatikidis
2011-04-02 14:22 ` todo aiju
2011-04-02 14:52 ` todo Ethan Grammatikidis
2011-04-01 17:38 ` todo Uriel
2011-04-01 7:09 ` todo cinap_lenrek
2011-04-01 6:14 ` todo Taru Karttunen
2011-05-02 7:30 TODO Uriel
2011-05-02 13:25 ` TODO Julius Schmidt
2011-05-02 17:03 ` TODO Uriel
2011-05-02 18:24 ` TODO Iruatã Souza
2011-05-02 19:33 ` TODO ron minnich
2011-05-02 13:45 ` TODO Jacob Todd
2018-02-24 19:53 TODO Kurt H Maier
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=B2FE32F0-9A14-4389-9298-14D257476339@fastmail.fm \
--to=eekee57@fastmail.fm \
--cc=9front@googlegroups.com \
/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).