[OpenAFS] aklog oddness?

[Ken Hornstein]

>It's not true that "aklog doesn't work".  It's only true that "aklog
>doesn't work with pure krb5 tickets/tokens without using krb524".  Again,
>this will all be fixed in 1.4.1 which was due out last month.

(Note that in my original email, I said "probably won't work" - I stand
by that statement, especially in the case of a new installation where
people seem to be having the biggest problem)

I can only point out that a number of people are having a problem with
with the aklog that comes in the 1.4.0 RPMS, and they're posting on the
openafs lists about it.  The problems that I researched all boiled down
to the basic fact that those RPMS use an old aklog, and the users
mistakenly believed the 1.4.0 documentation regarding the way aklog
worked.  The whole situation was clearly not widely known until recently.

If that isn't a fucked-up situation, I don't know what is.  I know that
this situation is supposed to be corrected when 1.4.1 comes out, but we
all know that OpenAFS release timetables aren't something you shouldn't
bet the farm on.  What, exactly, is the problem with documenting this?

--Ken