[OpenAFS] Linux packages for 1.5?
Wed, 07 Apr 2010 14:24:05 -0400
At what point should the 1.5.xx series be considered "usable" on Linux?
I'm thinking usable as 1.4.xx is, not trying disconnected mode, at the
I've tried Linux clients from 1.5.71-73 with varying amounts of
success, but in no case has it been sufficient. A quick look at my
domain, and you'll see that I'm likely connecting to a stunning (or
annoying) variety of servers, which might explain my results. In every
case, I've had "holes" in my data as viewed in /afs. Though those holes
have gotten smaller with each release, some still appear to be there
with 1.5.73. Is there something I can run that will furnish debug
information to be of some help? A quick glance through "pts help" or
"fs help" doesn't really suggest anything to me. I'm presuming I want
to identify missing data, and run something against the mount point or
against the server. With 1.5.72 I found that the mount points
themselves were missing for some data. I guess I also need to know how
to map a mount point to a server. By the way, this stuff is both
same-cell and cross-cell. For the testing I've done so far, any
cross-cell data is "system:anyuser rl" - I haven't gotten to getting
On 03/26/10 20:16, Simon Wilkinson wrote:
> On 27 Mar 2010, at 00:11, Jason Edgecombe wrote:
>> Are there any RPM or debian packages for 1.5?
> When I get the time, I've been producing RPMs for 1.5 using the
> 'standard' tool chain that we use for the 1.4.x RPMs.
> If people would like to see these on a more regular basis, let me know
> OpenAFS-info mailing list
Phone: (802) 769-6850
This e-mail and its attachments, if any, may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message from your system without copying it and notify sender of the misdirection by reply e-mail.