ramfs: make Elocked[] more consistent (thanks fazlul)
Go expects the error to be one of the three errors returned in
Bell Labs Plan 9. As listed in
f7ba82d68f/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",
}
This commit is contained in:
parent
ebb9acecdd
commit
ac6cb9af29
1 changed files with 1 additions and 1 deletions
|
@ -11,7 +11,7 @@ char Eexist[] = "file already exists";
|
||||||
char Enomem[] = "no memory";
|
char Enomem[] = "no memory";
|
||||||
char Eperm[] = "permission denied";
|
char Eperm[] = "permission denied";
|
||||||
char Enotowner[] = "not owner";
|
char Enotowner[] = "not owner";
|
||||||
char Elocked[] = "file locked";
|
char Elocked[] = "file is locked";
|
||||||
|
|
||||||
enum {
|
enum {
|
||||||
Tdat = 0xbabababa,
|
Tdat = 0xbabababa,
|
||||||
|
|
Loading…
Reference in a new issue