On 04/10/2011 19:08, Jens Staal wrote:
When I then try something like
cp -ar sources/plan9/sys/src/ape ape
I get an error stating:
unexpected open flags 050cp: can not open
”sources/plan9/sys/src/ape/9src/mkfile” for reading: Access denied
Hi,
This is working for me without plan9port
Hi.
First of all sorry if I through my ignorance am attempting something
completely stupid.
I have been trying to copy the APE sources using plan9port. The
purpose of this is that I am trying to make an APE augmentation
PKGBUILD to the kencc package [1] (and ultimately, I will try to
figure out
What I now wonder is: Is this the expected behaviour?
No. You are doing it fine.
It's working for me right now, authenticated and unauthenticated.
I don't know why it doesn't work for you.
Beware 9 mount should be spelled 9mount in your messages.
What kernel version are you using?
--
David
2011/10/4 David du Colombier 0in...@gmail.com:
What I now wonder is: Is this the expected behaviour?
No. You are doing it fine.
It's working for me right now, authenticated and unauthenticated.
I don't know why it doesn't work for you.
Beware 9 mount should be spelled 9mount in your
What does 'mount' (not 9 mount, just mount)
say after you mount the file system?
That will tell you whether the '9 mount' used
v9fs (Linux 9P driver) or 9pfuse (user-space
9P-to-FUSE translator).
Neither gets much use, so it is easy to believe
that there is a bug.
Russ
I can then cd and explore the bell labs sources via
plan9port, so that
works just fine.
When I then try something like
cp -ar sources/plan9/sys/src/ape ape
I get an error stating:
unexpected open flags 050cp: can not open
”sources/plan9/sys/src/ape/9src/mkfile” for reading:
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
2011/10/4 Russ Cox r...@swtch.com:
What does 'mount' (not 9 mount, just mount)
say after you mount the file system?
That will tell you whether the '9 mount' used
v9fs (Linux 9P driver) or 9pfuse (user-space
9P-to-FUSE translator).
Neither gets much use, so it is easy to believe
that there
2011/10/4 Russ Cox r...@swtch.com:
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
