On Sun, Sep 30, 2001 at 07:25:47PM +0200, Sangohn Christian wrote:
> But /coda looks like this:
> sikasso:~# ls -l /coda/
> total 0
> lrwxrwxrwx    1 root     root           11 Sep 30 16:59 adama-deb.store -> 
> #deb.store.
> -rw-r--r--    1 root     root            0 Jun 12 23:47 NOT_REALLY_CODA

							  ^^^^^^^^^^^^^^^

Did you actually start venus, does mount show that Coda is mounted on
/coda.

jaharkes_at_ravel:~/coda-HEAD-obj/coda-src/smon2$ mount | grep coda
Coda on /coda type coda (rw)

> What?s gone wrong?

You probably just created a 'magic-mount symlink' in the regular ext2
filesystem before Coda is mounted over the /coda mountpoint.

> BTW how do I make directory tree from the server visible to a client? How do 
> I "export" it`?

You can't, Coda server need a lot more metadata than a normal filesystem
has available (version-vectors, ACL's etc.). The server also needs to
break callbacks when modifications are made to files/directories. If you
would be able to export a regular fs the server would need to
continually try to track whether anything in the exported has been
changed by some other process, while now any modification is done
through the server itself.

You have to copy things into /coda and the server then stores all the
metadata (pathnames, version vectors, acls, file identifiers etc) in
it's RVM persistent memory, and only the bare contents of the files in
numbered files in the /vicepa tree/partition just to make it pretty hard
for you to change things in the exported tree without the server knowing
about the change.

Jan