Dale Ghent wrote:
I'm using this email to report on the problem, what I've found, and lay
out what our options are.
3) This is Rob's idea, so blame him if you reel back in horror. We find
a conditional by testing for a netstack symbol in the kernel ip module.
If TRUE, we have a pointer function that points to the new ILL_
functions with the extra argument. If FALSE, we point to the old ones.
Yum. This would certainly involve the least amount of code.
5) Continue to use the ILL method and release OpenAFS 1.4.5 with the
code being compatible with s10u4. We simply tell people that if you want
to run OpenAFS client version 1.4.5 or greater, you also need to run
Solaris KU 120012-14 (x86) or whatever the analog is if you're running
SPARC.
6) Any other idears?
7)
Do a combination of 3 and 5, building two versions of libafs64u4.o and
libafs64u4.o
in addition to the libafs64.o and libafs84.nfs.o using #ifdefs.
This is assuming that you can build a version on the u4 platform using the u4
macros
that can run on a pre-u4 kernel.
8) I addition to a sun4x_510 distribution build a sun4x_510u4. It could still
use
sysname=sun4x_510 This assumes that a #ifdef could test for the additional
argument
to the ill_* functions.
/dale
--
Dale Ghent
Specialist, Storage and UNIX Systems
UMBC - Office of Information Technology
ECS 201 - x51705
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
--
Douglas E. Engert <[EMAIL PROTECTED]>
Argonne National Laboratory
9700 South Cass Avenue
Argonne, Illinois 60439
(630) 252-5444
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
