On 11/5/07, Nick Holland <[EMAIL PROTECTED]> wrote:
> Greg Thomas wrote:
> >
> > Hmmm, on my second upgrade today I did a 4.0 to 4.2 upgrade, i.e.
> > threw the 4.2 CD in a 4.0 machine, upgraded, and then followed the
> > directions for 4.0 to 4.1 and 4.1 to 4.2.   Am I putting myself at
> > risk?
>
> eh.
> The upgrade script occasionally has "fixes" stuck in it that help the
> migration from vX.Y to vX.Y+1.  SO, if there was any magic in the 4.1
> upgrade script, you missed it.
>
> The other issue is I write the upgradeXX.html docs and the
> upgradeXX.patch files based on a "one-step-at-a-time" process.  On one
> upgrade, I may say "copy over this file", and the next one, it might
> be "patch this file", and if you try to patch it with the later version
> before copying the previous version over, it may fail.  However, if you
> take the time to /understand/ what I am doing in that upgrade process,
> it is easy to customize it to your needs.  I don't hide much. :)

Thanks, this was a screw around box so no biggie.  Next is my wireless
AP/firewall which I will do correctly.

> ...
> >
> > I love "pkg_add -ui -F update -F updatedepends".
> >
> > Up until this upgrade I'd manually removed and added packages.
>
> cool, isn't it? :)

Awesome!

Greg
-- 
Ticketmaster and Ticketweb suck, but everyone knows that:
http://ticketmastersucks.org
http://lodesertprotosites.org
Dethink to survive - Mclusky

Reply via email to