On Thursday, April 06, 2006 02:19:11 AM -0400 Marcus Watts <[EMAIL PROTECTED]>
wrote:
For the file servers, it's usually possible to upgrade fileserver
software without moving volumes. I haven't found many production
sites willing to risk this with real data. There have been and
probably w
Jeffrey Hutzelman <[EMAIL PROTECTED]> wrote:
> On Wednesday, April 05, 2006 11:54:55 PM -0500 "Christopher D.
> Clausen" <[EMAIL PROTECTED]> wrote:
>> I would recomend doing server upgrades as close as possible though to
>> minimize problems that may occur.
>
> FUD. Mixed-server-version cells work
On Apr 6, 2006, at 2:19 , Marcus Watts wrote:
For the file servers, it's usually possible to upgrade fileserver
software without moving volumes. I haven't found many production
sites willing to risk this with real data. There have been and
We do this somewhat regularly --- sort of. The AFS
On Thu, 6 Apr 2006, Marcus Watts wrote:
* The first rule is that for a given server (ptserver, vlserver,
buserver), all the servers that are up should be running exactly the
same version. There have been various changes going from transarc to
modern openafs in the ubik inter-server protocol;
Various wrote:
> Message-ID: <[EMAIL PROTECTED]>
> From: "Christopher D. Clausen" <[EMAIL PROTECTED]>
> To:
> References: <[EMAIL PROTECTED]>
> Subject: Re: [OpenAFS] Changes for Mosaic's AFS cell...
> Sender: [EMAIL PROTECTED]
> Date: Wed, 5 Apr 2006 23:54:55 -0500
>
> Rodney M Dyer <[EMAIL PROT
On Wednesday, April 05, 2006 11:54:55 PM -0500 "Christopher D. Clausen"
<[EMAIL PROTECTED]> wrote:
Rodney M Dyer <[EMAIL PROTECTED]> wrote:
Does it matter whether the cell servers are upgraded
first? Obviously not, since our existing test server already works.
I've never upgraded a cell se
Rodney M Dyer <[EMAIL PROTECTED]> wrote:
> Does it matter whether the cell servers are upgraded
> first? Obviously not, since our existing test server already works.
> I've never upgraded a cell server myself, and the person who last
> upgraded our cell servers has "left the building".
Other tha
All,
We are finally in a position to consider making some changes (very soon
now) to our Mosaic Computing OpenAFS setup here in the College of
Engineering at UNC Charlotte. As some of you may already know, I've been
working with OpenAFS and Kerberos 5 for quite some time so some of the
quest
On Wednesday, April 05, 2006 05:14:42 PM -0700 Miles Davis
<[EMAIL PROTECTED]> wrote:
1. When using multiple @sys names, is there a way to reference a
specific sysname in the list? e.g, given
$ fs sysname
Current sysname list is 'i386_linux26' 'foo'
can I create a link to @sys or somethin
1. When using multiple @sys names, is there a way to reference a
specific sysname in the list? e.g, given
$ fs sysname
Current sysname list is 'i386_linux26' 'foo'
can I create a link to @sys or something that point to foo without using
i386_linux26?
2. Is there some standard way to set the s
On Wed, 5 Apr 2006, Douglas E. Engert wrote:
The AFS file root.client/usr/bin/afs64 is the kernel extensions. Its about
2.5MB.
This needs to be copied to the /usr/conf/mod/afs64 Then you need to rebuild
the
kernel or tell it to use the new "mod" using SAM. (There may be a command
line
interf
lal anil wrote:
Hi All
I am a newbie to afs and HP-UX
I am successfull in configuring afs 1.4.1 on linux and solaris machines and also in hp 11.11. but I have got a requirement in configuring on hp-ux 11.23 which i feel is entirely different from the older version. I am not able to see a
Michael Heinrich <[EMAIL PROTECTED]> writes:
> Russ Allbery <[EMAIL PROTECTED]> writes:
>
>> 1.4.0 doesn't suspend properly with kernel versions later than 2.6.13 or
>> .14 (I forget exactly which one) due to changes in the kernel
>> refridgerator interface. 1.4.1-rc10 is supposed to work properl
13 matches
Mail list logo
