Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Mar 2010 01:49:23 -0600
From:      Tim Judd <tajudd@gmail.com>
To:        =?KOI8-R?B?4c7Uz84g68zF09M=?= <antoniok.spb@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Which version of FreeBSD is it?
Message-ID:  <ade45ae91003180049v75460786vd3e56529e40dda0@mail.gmail.com>
In-Reply-To: <3f1c29e71003170745u55a4fad2rd8c6f39d02fa968f@mail.gmail.com>
References:  <3f1c29e71003170656u1b932fd2v37f5062440653e3b@mail.gmail.com> <0b9982274818d454f23bc89ac74d30f5@asterix.area536.com> <3f1c29e71003170745u55a4fad2rd8c6f39d02fa968f@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 3/17/10, =E1=CE=D4=CF=CE =EB=CC=C5=D3=D3 <antoniok.spb@gmail.com> wrote:
> That is what I suspected for.
>
> What is the most safe way to upgrade it, remembering that this is product=
ion
> server and I have to keep it working properly?
>
> 6.2-RC1 -> 6.2 RELEASE -> 7.2 RELEASE -> 8.0 RELEASE, or somehow in this
> style?

<snip>

Honestly, if a system is going to go through that large of a change,
here's what I'd recommend.  First scenario is the quickest running,
then continue with the second to keep it up-to-date


Since *ALL* configuration of base and ports is done by /etc and
/usr/local/etc, back up those two directories to a tarball.  they're
all text files so it should compress very well.  Note the packages
currently on your system with a simple pkg_info.  This gets you a
prime data set that can restore 99%+ functionality if used.

Scenario 1:
  pkg_info >/root/pkg_info.txt
  tar -cPpzf /root/62rc1-config.tgz /etc /usr/local/etc /root/pkg_info.txt
  ** keep this /root/62rc1-config.tgz archive in a safe 2 spots.  2 spots.

  fresh install of 8.0R on the box.
  extract, at minimum, the /etc entries from the tarball kept safely
away from the box
  for each package listed in pkg_info.txt, install from packages that
package (just the QUICK way to bring a box to a usable state)
  extract the /usr/local/etc from the tarball.  **TRY** to restart
your services.

The reason I state 'try' is that config files may have changed from a
package version a.b to x.y, so you may need to tweak your config files
to match the current package.



Now that you have a live box again, able to serve requests, it's time
to keep it maintained.

Scenario 2:
  install portaudit
  run portaudit, fix any vulnerabilities
  ** at this time, your system is safe from most vulnerabilities
  run your favorite port management software to update the rest of the
ports who do not have vulnerability advisories.



I've used this tactic before, works well and WILL be faster than you
updating your system from 6.2 to 6.4 to 7.2 to 8.0


Let me know if you have questions.

--TJ



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ade45ae91003180049v75460786vd3e56529e40dda0>