From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <df49a7370712110530v388901c8ye54bdea3ee32fa4b@mail.gmail.com>
Date: Tue, 11 Dec 2007 13:30:16 +0000
From: "roger peppe" <rogpeppe@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Ideas for an printer filesystem
In-Reply-To: <775b8d190711302054g12c4868cv2575ab16c718a43c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20070906235628.GC26188@nibiru.local>
	<13426df10711302042x78d36291n54f50beb964aa068@mail.gmail.com>
	<775b8d190711302054g12c4868cv2575ab16c718a43c@mail.gmail.com>
Topicbox-Message-UUID: 1533db82-ead3-11e9-9d60-3106f5b1d025

On Dec 1, 2007 4:54 AM, Bruce Ellis <bruce.ellis@gmail.com> wrote:
> i wrote a clonefs that changes a walk to the directory created for
> the server to an attach  with ctl.  it saves a lot of replicated code.
> i wonder what happened to it.  it's not too hard.

i'm not quite sure what you mean here. do you mean something
like a filesystem that layers over (for instance) /net, so doing

    walk(net/tcp)

actually does

    id = open(/net/tcp/clone)
    walk(/net/tcp/id)

?

how do would you then open a file in the new directory
wthout going doing the same thing (and hence writing
to a different directory)?