[OpenAFS] 1.1.0 client on RH 7.1

[Jan Hrabe]

On Thursday 26 July 2001 16:21, Sam Hartman wrote:
> >>>>> "Jan" == Jan Hrabe <hrabe@balrog.aecom.yu.edu> writes:
>
>     Jan> What is so bad about the links pointing the way I suggested?
>
> First, it requires me to install the compat package.  I want to see us
> moving towards GNU Coding Standards style paths (respecting --prefix
> etc) away from the broken build system we currently have.  I
> understand the needs of existing sites require compatibility, but I
> believe that for the vast majority of situations, symlinks from afsws
> to the correct OS paths will do the trick.
>

Yes, it is probably the best compromise solution. 

>
>     Jan> By all means. My point was that the upserver works, AFAIK,
>     Jan> with the directories. If you put the server programs in
>     Jan> /usr/sbin then the upserver would probably try to distribute
>     Jan> that whole directory.  You could of course give up
>     Jan> upclient/upserver in favour of RPM but that would be giving
>     Jan> up functionality.
>
> I think that having a deb or rpm or other package based update model
> for all your software distribution provides more functionality than
> upserver.  I don't really think upserver works that well for things
> besides AFS.  But to each his own.  The AFS community will need to
> support both because we have users using both styles of setup.

Could you please elaborate why RPM would provide more functionality
for the AFS server programs distribution than upserver? Currently, all
I have to do is issue a single command (bos install) for every platform
and everything else is taken care of for me. The update happens 
"automagically" and in sync on all servers. The distribution can even be 
encrypted. I don't see how the RPM system, otherwise great for individual 
computer upgrades, can do it as easily and "out of the box".

I agree both methods will be needed. An administrator of Linux-only
shop will want to have a single method for everything (RPM) and
an administrator of a mixed platform shop will want to have, well, 
a single method for everything (upserver) :-) .