Re: Updating Question

[Antonio Huete Jimenez <ahuete.devel@xxxxxxxxx>]

--047d7b6778160041c404cd651317
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi,

We're trying to reproduce your scenario to get the best approach for your
upgrade process. We'll keep you posted.

Cheers.
 El 01/11/2012 02:18, "Justin Sherrill" <justin@shiningsilence.com>
escribi=F3:

> On Wed, Oct 31, 2012 at 4:59 AM, Konrad Neuwirth
> <konrad@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 =96 we're hitting one bug i=
n
> 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.
>
>

--047d7b6778160041c404cd651317
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<p>Hi, </p>
<p>We&#39;re trying to reproduce your scenario to get the best approach for=
 your upgrade process. We&#39;ll keep you posted.</p>
<p>Cheers.<br>
</p>
<div class=3D"gmail_quote">El 01/11/2012 02:18, &quot;Justin Sherrill&quot;=
 &lt;<a href=3D"mailto:justin@shiningsilence.com";>justin@shiningsilence.com=
</a>&gt; escribi=F3:<br type=3D"attribution"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
On Wed, Oct 31, 2012 at 4:59 AM, Konrad Neuwirth<br>
&lt;<a href=3D"mailto:konrad@mailathome.or.at";>konrad@mailathome.or.at</a>&=
gt; wrote:<br>
&gt; Dear reader,<br>
&gt;<br>
&gt; there is one production system that we have that is still running an a=
cient version:<br>
&gt;<br>
&gt; | DragonFly =A02.0.1-RELEASE DragonFly 2.0.1-RELEASE<br>
&gt;<br>
&gt; As you can imagine, I&#39;d like to update that =96 we&#39;re hitting =
one bug in the filesystem code there ever so often.<br>
&gt;<br>
&gt; Is there anything that would keep us from just doing the update? and w=
hat would be the smartest way to do so?<br>
<br>
If you follow /usr/src/UPDATING, that should cover any irregularities<br>
in updating from version to version. =A0It may be worth updating to 2.2,<br=
>
then 2.8, then I think 3.2, just because those seem to be the major<br>
releases where there were changes in the upgrade path. =A0I haven&#39;t<br>
tried it like that, so this is an educated guess.<br>
<br>
Don&#39;t forget to upgrade your Hammer filesystems too.<br>
<br>
</blockquote></div>

--047d7b6778160041c404cd651317--