From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <13426df10804062345w40381703w5a61e018f0c4d5b4@mail.gmail.com>
Date: Sun,  6 Apr 2008 23:45:27 -0700
From: "ron minnich" <rminnich@gmail.com>
To: 9fans@9fans.net
In-Reply-To: <13426df10804062335x7a1b95a0pb26f96afb660d89b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <a4e6962a0804060739x79bb31e8g5db40bc5ee0bcbff@mail.gmail.com>
	<90ba82d2d99c43b2a8d8790f09f15014@mteege.de>
	<13426df10804062335x7a1b95a0pb26f96afb660d89b@mail.gmail.com>
Subject: Re: [9fans] p9_errstr2errno unknown mode
Topicbox-Message-UUID: 89cef616-ead3-11e9-9d60-3106f5b1d025

btw, this 'unkown mode' -- what is all this you wonder?
what's
p9_errstr2errno: errstr :unknown mode: not found

Not found? Huh? This is the errstr (from plan 9) to errno (for
ancient, primitive OSes that don't have errstr, i.e. 'all of them').

I see in fossil/9p.c this for create:
	if(omode == OREAD || omode == ORDWR || omode == OEXEC)
		open |= FidORead;
	if(omode == OWRITE || omode == ORDWR)
		open |= FidOWrite;
	if((open & (FidOWrite|FidORead)) == 0){
		vtSetError("unknown mode");
		goto error;
	}

Or this for open:
	if((open & (FidOWrite|FidORead)) == 0){
		vtSetError("unknown mode");
		goto error;
	}

So, seems linux client is sending bad omode?

we sure could use that trace.

ron