@sys in /afs directory on arla-0.13 works ?

[Jon S. Stumpf]

Magnus Ahltorp wrote:

> > It may make more sense, but it's not what the rest of the AFS world is using
> > so it's a problem when talking to existing AFS installations with existing
> > linux-afs clients.
> >
> > FWIW we're using i386_linux2 for libc5, i386_linux2g currently for libc6,
> > but we're going to switch to i386_linux3 when the "official unofficial"
> > glibc linux-afs port comes out (it will use i386_linux3 for glibc2/libc6).
> > I'm not overly fond of it, but it's what I have to live with.
>
> Since arla has more support for linux compared to Transarc, and has
> not come out with the glibc port yet, arla was typically first.
>
> I'm not going to support more Transarc weirdnesses than
> neccessary. It's already enough. You don't have to live with it.

I tried to change this when I was a customer for 2.5 years and I tried while I was
a Transarc employee for 4 years.  Although I could get some consensus that it
didn't make sense to use "compiled OS", there was no real motivation to change
it.  As a customer, I forced the change of each particular OS to something that
made sense at each client.  This way, my infrastructure made sense to me and
anyone that was brought on to support it.

Since Transarc isn't inclined to promote the change, use arla to do it for them.

- jss

Open Source: If it's broke, fix it.