From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <39b40e383b62db3da4792bcb3aa16692@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9p and how can I know when a write is finished
Date: Wed,  1 Mar 2006 20:15:33 +0000
From: rog@vitanuova.com
In-Reply-To: <4405FABC.6070501@lanl.gov>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 09020480-ead1-11e9-9d60-3106f5b1d025

> I can't think of a single good thing about using Tclunk to drive the ctl
> state machine.

i can.  it's the simplest way of doing things, works smoothly with
existing stuff (e.g.  echo blah > ctl), and would be just fine if the
control request is never likely to fail, and performance isn't an
issue.

i've used russ's method of "zero-length write if you care about the
result" before, and that works well, but i have to say i usually just
ended up using cat or cp (i.e.  ignoring errors).

for another way, look at the way cdfs(4) lets you fixate disks.  it's
a little odd, but it works.