[OpenAFS] 1.1.0 client on RH 7.1

[Derek Atkins]

The 'fs sysname' incompatibility was a bug and will be changed back in
the next release.

The question is: is the actual location of AFS applications an issue
to many people?

-derek

Rudolph T Maceyko <rtm@cert.org> writes:

> OK...  I'll keep building it locally, since we're in a transitional 
> environment where I'd like to be able to consider OpenAFS as somewhat 
> interchangeable with the old Transarc AFS (for clients, at least).  The 
> compat package gives those old scripts a fighting chance of working w/o 
> modifications.  In fact, so far the only thing that caused any grief at 
> all was the change to fs sysname, so the needed compatibility was 
> provided (for us, at least).
> 
> No biggie, but I thought others would be in the same spot...
> 
> -Rudy
> 
> --On Wednesday, July 25, 2001 13:41:39 -0400 Derek Atkins 
> <warlord@MIT.EDU> wrote:
> 
> > I've applied most of this patch (I didn't take the openafs-compat
> > changes).  Personally I don't see much of a need, really, and trying
> > to maintain that much compatibility is just, um, challenging.  There
> > are a lot of things that are done differently in the RPMs than a
> > standard "afsws" install.
> 
> 
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord@MIT.EDU                        PGP key available