On Mon, 10 Sep 2012 14:36:34 -0400 Derrick Brashear <[email protected]> wrote:
> and figure out where you will store the addresses, since at least as > is the vldb won't. > > if you fork, you could define your own format there and store it. all > your vldbs would have to be > "TFS" vldbs. This is not strictly true. I have a list of IPv4 addresses for a fileserver MH record. If I don't care about working with old clients, that is basically an array of opaque 32-bit values. I can store an IPv6 address in that. (Well, it is true that that won't "work" if you try to revert to a 'normal' vlserver, of course.) Come to think of it, you can probably make that work without even having new RPCs. You wouldn't even have to modify the vlserver; and if you manually put the stuff in NetInfo yourself, I don't think you'd even have to modify the fileserver. (that is, besides making the vlserver/fileserver work with ipv6-rx) All of that kinda depends on how 'correctly' vs 'one-off kludge' you would want to do it. But it's possible. -- Andrew Deason [email protected] _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
