Georg Lehner <[EMAIL PROTECTED]> writes:
> Hello!
>
> Try to configure fossil to
>
> listen -N tcp!*!564
>
> This will allow the "none" user to connect.
I'm not really sure I want that though...
> You would have to authenticate first (as user ajft) and then mount
> from Linux, this I have not found out how to do yet.
The following is now working for me.
[EMAIL PROTECTED]:~$ factotum
[EMAIL PROTECTED]:~$ srv -a wyvern wyvern
!adding key: role=client proto=p9sk1 dom=home
user[ajft]:
password:
!
[EMAIL PROTECTED]:~$ sudo mount -t 9p -o user=$USER,uid=`id -u`,gid=`id
-g`,proto=unix `namespace`/wyvern /mnt
[EMAIL PROTECTED]:~$ ls /mnt/
386/ acme/ amd64/ dist/ lib/ LICENSE.gpl mips/ NOTICE sparc/
tmp/
68000/ adm/ arm/ env/ LICENSE lp/ mnt/ power/
sparc64/ usr/
68020/ alpha/ cron/ fd/ LICENSE.afpl mail/ n/ rc/ sys/
Somewhere along the line the filesystem type seems to have changed
from "9P" to "9p".
Now I get to see how useful it may be. Copying, editing, viewing
files seems to behave as I expected. Trying rsync or unison to copy
files from the linux filesystem to the mounted fossil failed
> Regards
>
> Jorge-León
ADrian
