Jan Harkes <jaharkes_at_cs.cmu.edu> writes:
> On Tue, Jul 29, 2003 at 06:35:48PM +0200, Steffen Neumann wrote:
[...]
> > is a pain in the a**. To exagerate it: why bother
> > about compatibility with 5.3.x clients, if neither
> 
> Because there are no server-side changes for realms. The only reason
> we're backwards compatibile is because the client-server protocol is
> still the same. I agree that it is a pain to switch to the new scheme,
> not just the name changes, but also the kernel patching.
Installing and setup is fine, you do this only once.

> However, there are some advantages. There is no need to set up a client
> for a specific realm, it is impossible to get a conflict on /coda that
agreed.

[...]
> New mountpoint
> --------------
> 
>     /coda-realms/			- normal 6.0 root
>     /coda -> /coda-realms/local.realm	- a symlink for our current realm
> 
>     (New programs/scripts should be modified to use /coda-realms/local.realm)
>     
>     required changes:
>     - There should be no changes necessary in the venus code.
>     - codaconfedit venus.conf mountpoint /coda-realms
>     - mkdir /coda-realms ; restart venus
>     - rmdir /coda ; ln -s /coda/local.realm /coda
> 
>     problems:
>     - Adds more to the already long pathnames.
>     - I don't like the /coda-realms mountpoint name, but can't come up
>       with anything better. (maybe /realms ?)

/realms is better if you use <tab> frequently :-)
This seems to be the way we will go.



Yours,
Steffen