There once was an incompatibility between AFS and DUX (HP's diskless
protocol), but it was fixed in some iteration of 3.3.
This business of
> Replacing system call 32 ( 2 19c2a4).
> warning: system call not unused.
> with ( 2 124008).
> Calling kernel with 463021...Restoring previous value of sysent[32]
> returned value=4212000, code = 0(797144)
...
> Replacing system call 32 ( 2 19c2a4).
> warning: system call not unused.
> with ( 2 4212040).
is telling. AFS uses a temporary system call to transfer control to
some initialization code in the newly-loaded cache manager. It appears
that something is already using the slot which we wish to use.
I've never heard of anything like "HP fixed HPUX to prevent AFS from
working...". That's not conclusive, of course.
I'm not completely clear on why this is happening -- I wonder what
HP product is using slot 32. At any rate, you should be able to get past
this problem by statically building a monolithic kernel instead of using
dkload.
