Antonio Huete Jimenez
ahuete.devel at gmail.com
Wed Oct 31 18:38:20 PDT 2012
We're trying to reproduce your scenario to get the best approach for your
upgrade process. We'll keep you posted.
El 01/11/2012 02:18, "Justin Sherrill" <justin at shiningsilence.com>
> On Wed, Oct 31, 2012 at 4:59 AM, Konrad Neuwirth
> <konrad at mailathome.or.at> wrote:
> > Dear reader,
> > there is one production system that we have that is still running an
> acient version:
> > | DragonFly 2.0.1-RELEASE DragonFly 2.0.1-RELEASE
> > As you can imagine, I'd like to update that – we're hitting one bug in
> the filesystem code there ever so often.
> > Is there anything that would keep us from just doing the update? and
> what would be the smartest way to do so?
> If you follow /usr/src/UPDATING, that should cover any irregularities
> in updating from version to version. It may be worth updating to 2.2,
> then 2.8, then I think 3.2, just because those seem to be the major
> releases where there were changes in the upgrade path. I haven't
> tried it like that, so this is an educated guess.
> Don't forget to upgrade your Hammer filesystems too.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users