From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <1317757198.32730.YahooMailClassic@web83904.mail.sp1.yahoo.com> References: <1317757198.32730.YahooMailClassic@web83904.mail.sp1.yahoo.com> Date: Tue, 4 Oct 2011 15:44:07 -0400 Message-ID: Subject: Re: [9fans] copying over 9P using plan9port From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Topicbox-Message-UUID: 32a748da-ead7-11e9-9d60-3106f5b1d025 To answer my question: the error message comes from 9pfuse. The extra bits are O_NOFOLLOW and O_LARGEFILE, both of which seem harmless in this context. Try this: diff -r 6db8fc2588f6 src/cmd/9pfuse/main.c --- a/src/cmd/9pfuse/main.c Mon Oct 03 18:16:09 2011 -0400 +++ b/src/cmd/9pfuse/main.c Tue Oct 04 15:43:16 2011 -0400 @@ -577,6 +577,13 @@ openmode = flags&3; flags &= ~3; flags &= ~(O_DIRECTORY|O_NONBLOCK|O_LARGEFILE|O_CLOEXEC); +#ifdef O_NOFOLLOW + flags &= ~O_NOFOLLOW +#endif +#ifdef O_LARGEFILE + flags &= ~O_LARGEFILE +#endif + /* * Discarding O_APPEND here is not completely wrong, * because the host kernel will rewrite the offsets @@ -594,7 +601,7 @@ * O_NONBLOCK -> ONONBLOCK */ if(flags){ - fprint(2, "unexpected open flags %#uo", (uint)in->flags); + fprint(2, "unexpected open flags %#uo\n", (uint)in->flags); replyfuseerrno(m, EACCES); return; }