Re: [OpenAFS] Re: [OpenAFS-devel] Thinking about 1.6

2009-12-16 Thread Jeffrey Hutzelman
--On Wednesday, December 16, 2009 11:24:10 PM + Simon Wilkinson wrote: On 16 Dec 2009, at 23:03, Jeffrey Hutzelman wrote: How do you propose to automate that, given that the existing configuration could provide arbitrary arguments or even use arbitrary binaries for the various fs bnode

Re: [OpenAFS] Re: [OpenAFS-devel] Thinking about 1.6

2009-12-16 Thread Simon Wilkinson
On 16 Dec 2009, at 23:03, Jeffrey Hutzelman wrote: How do you propose to automate that, given that the existing configuration could provide arbitrary arguments or even use arbitrary binaries for the various fs bnode commands? If you're using my package, you'd better be using my binaries. I

Re: [OpenAFS] Re: [OpenAFS-devel] Thinking about 1.6

2009-12-16 Thread Russ Allbery
Jeffrey Hutzelman writes: > Russ Allbery wrote: >> The package should recognize that an upgrade is happening and adjust >> the bos configuration accordingly. > How do you propose to automate that, given that the existing > configuration could provide arbitrary arguments or even use arbitrary >

Re: [OpenAFS] Re: [OpenAFS-devel] Thinking about 1.6

2009-12-16 Thread Jeffrey Hutzelman
--On Wednesday, December 16, 2009 12:40:18 PM -0800 Russ Allbery wrote: "Buhrmaster, Gary" writes: Many (linux) packaging systems will just replace older versions without a discussion with the installer about what else they need to change (it is actually a pet peeve of mine that there is no

Re: [OpenAFS] Re: [OpenAFS-devel] Thinking about 1.6

2009-12-16 Thread Russ Allbery
"Buhrmaster, Gary" writes: > Many (linux) packaging systems will just replace older versions without > a discussion with the installer about what else they need to change (it > is actually a pet peeve of mine that there is nothing equivalent to the > SMP/E "HOLD(DOC)" capability(*) in most packag

Re: [OpenAFS] Re: [OpenAFS-devel] Thinking about 1.6

2009-12-16 Thread Derrick Brashear
On Wed, Dec 16, 2009 at 3:23 PM, Andrew Deason wrote: > On Wed, 16 Dec 2009 11:41:47 -0800 > "Buhrmaster, Gary" wrote: > >> > Right, but if it is part of the initial 1.6 release, I think people >> > will quite a bit more cautious then just replacing binaries anyway >> > since it is a major versio

RE: [OpenAFS] Re: [OpenAFS-devel] Thinking about 1.6

2009-12-16 Thread Buhrmaster, Gary
> Right, but if it is part of the initial 1.6 release, I think people > will quite a bit more cautious then just replacing binaries anyway > since it is a major version change then then a .x update. Not all the people running openAFS will be as knowledgably (even as to the numbering system of a 1.

Re: [OpenAFS] Re: [OpenAFS-devel] Thinking about 1.6

2009-12-16 Thread omalleys
Quoting "Steven Jenkins" : First, I think this is a *really* good idea. However, the bos configuration for the fileserver changes from non-DAFS to DAFS, so we need to make sure that people know that as part of the upgrade. If you just replace the binaries and restart, you won't be happy. Ri