[OpenAFS] 1.3.70 comments?

[Dale Ghent]

On Aug 16, 2004, at 11:45 PM, Derrick J Brashear wrote:

> I notice the comments aren't rolling in on this release. We need 
> feedback to fix remaining issues so 1.4 can be released. Is anyone 
> actually using this?

We need to shore up Solaris 9 support and further verify Solaris 10 
support.

Besides the outstanding vfsck issue, there are also two instances where 
OpenAFS code uses u_int32_t (or was it u_int64_t? I forget , the code 
isnt in front of me.) Anyhow, Solaris uses POSIX, and so there are no 
public typedefs with the non-POSIX (and apparently used in Linux) u_ 
prefix. The POSIX analogs are of course uint32_t and uint64_t, as 
defined in <sys/inttypes.h>

I guess the patch to fix this so that compilation on Solaris is one 
step closer depends on where the allegiance, for lack of a better word, 
of the OpenAFS maintainers are. Do we typedef for non-POSIX or do we do 
it for POSIX; and then patch whoever falls outside of that?

/dale