Sorry, I was unclear, I meant stat("" ...)
On 22 December 2012 15:59, erik quanstrom wrote:
> , although I don't know
>> anything that relies on that.
> Following an attach, you're at the root, and a walk with no qids will
> leave you there, so stat will just work, although I don't know
> anything that relies on that.
cclone().
- erik
I don't think either of those is a special rule, or undocumented.
Indeed, I can't think of any behaviour that isn't covered in section 5.
Following an attach, you're at the root, and a walk with no qids will
leave you there, so stat will just work,
although I don't know anything that relies on tha
I like to 1+ this comment :)
On Fri, Dec 21, 2012 at 10:44 AM, Gorka Guardiola wrote:
> I normally use a combination of running iostats and ramfs with debugging and
> reading again and again intro(5).
>
> HTH.
>
> G.
>
> On Dec 21, 2012, at 7:23 PM, steve wrote:
>
>> hi,
>>
>> I writing another
IIRC, I think I wrote something about that in the 9.intro book.
But it's likely you already know all that's written there and you want
more details…
On Dec 21, 2012, at 7:23 PM, steve wrote:
> hi,
>
> I writing another non-disc file server after a gap of a few years
> and am making mistakes.
>
I normally use a combination of running iostats and ramfs with debugging and
reading again and again intro(5).
HTH.
G.
On Dec 21, 2012, at 7:23 PM, steve wrote:
> hi,
>
> I writing another non-disc file server after a gap of a few years
> and am making mistakes.
>
> is there a written spec
hi,
I writing another non-disc file server after a gap of a few years
and am making mistakes.
is there a written spec of how its supposed to work?
For example:
the initial stat of a zero length name should return the Dir
of the root dir.
and a walk up to the root directory tells mount driver t