Coda File System

Re: install-server and install-client targets conflict

From: Frederick Bruckman <>
Date: Sun, 20 Feb 2000 02:15:47 -0600 (CST)
On Sat, 19 Feb 2000, Jan Harkes wrote:

> On Sat, Feb 19, 2000 at 11:28:11AM -0600, Frederick Bruckman wrote:
> > In coda-5.3.5 (at least), install-server and install-client both
> > install "au" and "filcon". This causes a minor administrative problem
> > for the NetBSD packages constructed from those targets, coda-client-*
> > and coda-server-*. Installing both on the same machine produces
> > warnings, but worse, if someone installs the server, installs the
> > client, and then deinstalls the client, those programs will no longer
> > be present on the server. And vice-versa. Even if folks simply install
> > and upgrade both packages together, they're going to see warnings,
> > which will result in bug reports.
> I thought I had moved them already. au is more of an administrators
> tool, but the client package is a reasonable location. filcon got moved
> to a separate rpc2 package (rpc2 and rvm are now separate off like lwp).

Thanks for the response. For the NetBSD coda_{client,server}-5.3.5
packages, I've made it so "filcon" only gets installed with the
server, and "au" only with the client.

<plug> Coda packages for NetBSD-1.4.2 should start to appear
concurrently with the NetBSD-1.4.2 release. The release is sheduled to
be tagged today, but you know how that goes.

The trivial kernel mods for the client are only in some of the ports,
so clients should work out of the box only for arm32, i386, mac68k,
and sparc (but I've no access to an arm32 or sparc machine). Other
NetBSD archs (alpha, bebox, pmax, sun3, etc.) could only run servers.
Received on 2000-02-20 03:17:08