Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!uunet!mcrware!dibble
From: dibble@mcrware.UUCP (Peter Dibble)
Newsgroups: comp.os.os9
Subject: Re: V_BUSY, who sets it?
Keywords: filemanager V_BUSY
Message-ID: <6593@mcrware.UUCP>
Date: 20 May 91 19:59:56 GMT
References: <16115@ganymede.inmos.co.uk> <1991May18.203057.25113@ncsu.edu>
Reply-To: dibble@mcrware.UUCP (Peter Dibble)
Followup-To: comp.os.os9
Organization: Microware Systems Corp., Des Moines, Iowa
Lines: 15

davidj@brad.inmos.co.uk (David Johnston) writes:
>  [problem with IRQ routine and no V_Busy set]
>  This kind of indicates that the filemanager is responsible for
> setting V_BUSY correctly, however none of my documemtation (Dibble,
> OS9 manuals & I/O tech ref) gives information on which routine should
> do this, or how.

See the last few lines on  page 311 of "Insights."  It's not what
you'd call a clear and detailed discussion, but it does show you
the standard OS-9 way for file managers to handle V_BUSY.

<This brings up a bug in the book's PCFM code.  PCFM should do
the IOQ/V_BUSY stuff for setstat calls. It doesn't.>

Peter