From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wopr.sciops.net ([216.126.196.60]) by ewsd; Thu Jun 11 16:06:55 EDT 2020 Received: (qmail 26994 invoked by uid 1001); 11 Jun 2020 13:06:47 -0700 Date: Thu, 11 Jun 2020 13:06:47 -0700 From: Kurt H Maier To: 9front@9front.org Subject: Re: [9front] [PATCH] ramfs: change Elocked error string to Go expectation Message-ID: <20200611200647.GB21685@wopr> Mail-Followup-To: 9front@9front.org References: <20200611200250.GA114633@delta.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200611200250.GA114633@delta.localdomain> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: mobile base XML full-stack hardware On Thu, Jun 11, 2020 at 04:02:50PM -0400, Fazlul Shahriar wrote: > Go expects the error to be one of the three errors returned in > Bell Labs Plan 9. As listed in > https://github.com/golang/go/blob/f7ba82d68f90e20aa9e6aa973cb6f12321abec71/src/cmd/go/internal/lockedfile/lockedfile_plan9.go#L16: > > // Opening an exclusive-use file returns an error. > // The expected error strings are: > // > // - "open/create -- file is locked" (cwfs, kfs) > // - "exclusive lock" (fossil) > // - "exclusive use file already open" (ramfs) > var lockedErrStrings = [...]string{ > "file is locked", > "exclusive lock", > "exclusive use file already open", > } hjfs uses "file locked" as well