On 4 Sep 2003, Steffen Neumann wrote:

> I am not too sure about 6.0.x, but it could be:
>
> 	cfs mkmount /coda/your.server.co.uk/ ROOTVOLUME

No, ROOTVOLUME's name is taken from a file created during vice-setup
dialogue. No mountpoints can be created directly under /coda

> and	cfs mkmount /coda/your.server.co.uk/mytest test

This one is right.

> Once that works, go back to the archive and 6.0 announcement,
> and think about a decent naming scheme for your volumes.
> IIRC you could name your root '/' and volumes /home/ian
> so that they're automagically mounted if you access
>
> 	/coda/your.server.co.uk/home/ian
>
> Since I've never used this scheme, I got
> to refer you to the list archives.

To be able to remember the mapping between volume names and mountpoints,
I suggest creating volumes named like their mountpoints' paths,

i.e. "createvol_rep / ... ..."    given that you have told vice-setup
that your root volume is called "/"

and likewise  "createvol_rep /mytest ......"  being to be mounted on
/coda/your.server.co.uk/mytest

Then you can use the short form of the cfs mkmount:

cfs mkmount /coda/your.server.co.uk/mytest

that works like

cfs mkmount /coda/your.server.co.uk/mytest /mytest

> > BTW I'm trying to get eg. my home directory into the coda server, if
> > that isn't obvious!
> Not a good idea. Some programs need e.g. locking (e.g. evolution ?),
> and behave differently when on ext2 or coda. You don't want your
> mozilla cache on coda either. Do a normal /home/ian
> and populate with symlinks where needed. Create a tar
> of the symlinks, put in /coda/home/ian, and extract on "new" clients.

I use a quite opposite approach, giving the users homedirs under
/coda/..../somewhere/...
It works fine except for some broken programs which need wrappers
to put their sockets or temporary files out of the homedir.
Those are rather few and hopefully will be fixed in the future as it is a
bug - expect a certain behaviour of a home directory,
like that its path is shorter than 108 chars :) for UNIX sockets
or that is supports locking.

An important thing is that the users have to be able to acquire their
credentials at login time. It needs unfortunately proper client
configuration (I'm using pam).

Regards,
--
Ivan