From ac6cb9af2986745078a70b644d4f5fde49ba1b72 Mon Sep 17 00:00:00 2001 From: cinap_lenrek Date: Fri, 12 Jun 2020 01:35:37 +0200 Subject: 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 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", } --- sys/src/cmd/ramfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sys/src/cmd/ramfs.c b/sys/src/cmd/ramfs.c index 17b23bf0a..85bbe9e31 100644 --- a/sys/src/cmd/ramfs.c +++ b/sys/src/cmd/ramfs.c @@ -11,7 +11,7 @@ char Eexist[] = "file already exists"; char Enomem[] = "no memory"; char Eperm[] = "permission denied"; char Enotowner[] = "not owner"; -char Elocked[] = "file locked"; +char Elocked[] = "file is locked"; enum { Tdat = 0xbabababa, -- cgit v1.2.3