At 1:26 AM -0500 12/3/05, Jeffrey Altman wrote:
What I am reading in this thread is that people are afraid
of the unknown.
No, I am afraid of my user community. They are a known quantity,
and I know I have reason to be afraid... They vary greatly in
what they use AFS for, and in how much
On Saturday, December 03, 2005 01:26:57 AM -0500 Jeffrey Altman
<[EMAIL PROTECTED]> wrote:
* Jan 2006 - Stable Windows client with byte range locking that is
mandatory to use
I have a better idea. I'll decide when byte-range locking support is
mandatory for my users to use. I can thi
On Saturday, December 03, 2005 01:26:57 AM -0500 Jeffrey Altman
<[EMAIL PROTECTED]> wrote:
One of the points that I am attempting to make is that the rate of change
in the Windows client is going to continue to out pace the rate of change
in the Unix-based implementations for at least the ne
Do you ever sleep?
Its 10:47 in Anchorage...
tedc
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
If the MIT presentation at the CMU Conference was on the web..
People would understand that 10E? of users rely on the windows client.
Reliability is not an option.
BTW: Are the CMU talks ever going to be posted?
tedc
___
OpenAFS-info mailing list
Ope
Jeffrey Hutzelman wrote:
On Saturday, December 03, 2005 01:26:57 AM -0500 Jeffrey Altman
<[EMAIL PROTECTED]> wrote:
* Jan 2006 - Stable Windows client with byte range locking that is
mandatory to use
I have a better idea. I'll decide when byte-range locking support is
mandatory for m
Jeffrey
Unfortunately in an MS environment where the users have been trained to
work with a windows fileserver and everything is done via shared
excel/word/access documents, persistent file corruption results if I
move their home directories to AFS at the moment, which means recovery
from tape.
T
