From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Fri, 29 Jul 2005 14:24:03 -0500 From: Eric Van Hensbergen To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] implmenting /mnt/9/clone In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Topicbox-Message-UUID: 71106766-ead0-11e9-9d60-3106f5b1d025 On 7/29/05, Ronald G. Minnich wrote: >=20 > I'm playing around with the p9p ramfs server, and was wondering about the > best way to implement a file for clone. >=20 > e.g. I have /mnt/9/clone, and when clone is opened, I want to to mean tha= t > /mnt/9/1/ctl is created and fid for that file returned to client, and the > next open of clone gets /mnt/9/2/ctl, etc. As usual, a read of the ctl > would return the # for that ctl file. >=20 One small problem I've noticed with v9fs and clone style file systems (in particular ACME) -- make sure things like stat don't trigger the creation of the resource, otherwise things like ls -l will end up creating windows, etc. I haven't found a good way around this from a Linux perspective. -eric