Lucho,
Yes this works great.
Thanks,
-Don
Latchesar Ionkov wrote:
It looks like the support of user authentication was dropped from v9fs
during some of the rewrites and it is going to take some time to put
it back in an official kernel.
I just sent a patch for approval that would allow you to add
unauthenticated users to xcpu so you can mount without the
authentication support. That was supposed to work, but I guess some
changes overlooked the feature and made it almost impossible to add
such users.
So what you should do after creating /etc/xcpu/admin_key is:
xuserset add localhost nobody 4294967295 xcpu-admin
mount -t 9p 127.0.0.1 /mnt/xcpu/1 -o port=6667,access=any
Let me know if it doesn't work. Once I fix v9fs, I'll create an xcpu-
mount utility that does authentication.
Thanks,
Lucho
On Mar 31, 2009, at 9:53 AM, Don W Rudish wrote:
The only case I can think of is that its uses this example in the
current documentation under xcpu-1.2.3/doc/xcpu.pdf. ...the ability
to mount a compute node over the network to the local file system is
a significant departure from the antiquated remote execution...
For my purpose I'd like to see what XCPU is all about and grasp a
better understanding on ways to use it.
-Don
Latchesar Ionkov wrote:
That's correct. You need to authenticate to mount xcpu. We normally
use xcpu without mounting (connecting from user-space 9P clients).
If you have a convincing case for using it mounted, I can probably
write a simple mounter that does the authentication before it handles
the connection to the kernel.
Thanks,
Lucho
On Mar 30, 2009, at 7:43 PM, Abhishek Kulkarni wrote:
On a cursory look, I think the issue here is that the v9fs client
tries to attach to the server with afid = NOFID (note: the afid=%u
option does not set the afid, a v9fs bug?)
and xcpufs does not support attaching with NOFID. (in other words,
xcpufs requires authentication).
On Mon, Mar 30, 2009 at 7:00 PM, Don W Rudish <[email protected]>
wrote:
I'm trying to mount an XCPU client on my local laptop but am having
problems doing so.
ssh-keygen -t rsa -f admin_key
mkdir /etc/xcpu
cp admin_key* /etc/xcpu
xcpufs -d
xgroupset add 127.0.0.1 root 0
xuserset add 127.0.0.1 root 0 root /root/.ssh/id_rsa.pub
xrx 127.0.0.1 /bin/date
That Works
Now I want to mount the client on /mnt/xcpu1/1 so I do:
mount -t 9p 127.0.0.1 /mnt/xcpu/1/ -o uname=root,port=6667
xcpufs reports:
<<< (0x15b42e0) Tversion tag 65535 msize 8192 version '9P2000.u'
(0x15b42e0) Rversion tag 65535 msize 8192 version '9P2000.u'
<<< (0x15b42e0) Tattach tag 0 fid 0 afid -1 uname root aname nuname
-1
(0x15b42e0) Rerror tag 0 ename authentication failed ecode 5
When I leave off the uname=root parameter I get:
<<< (0x15b42e0) Tversion tag 65535 msize 8192 version '9P2000.u'
(0x15b42e0) Rversion tag 65535 msize 8192 version '9P2000.u'
<<< (0x15b42e0) Tattach tag 0 fid 0 afid -1 uname nobody aname
nuname -1
(0x15b42e0) Rerror tag 0 ename unknown user ecode 5
I'm using a ubuntu 2.6.27-11-generic kernel with xcpu-1.2.3 running
all commands as root. Any ideas?
-Don
