Date: Tue, 9 Sep 2008 07:35:48 -0400 From: John Almberg <jalmberg@identry.com> To: freebsd-questions@freebsd.org Subject: Re: safest way to upgrade a production server Message-ID: <9C33E030-B480-4E3C-B1A0-9AA7B77B7E3C@identry.com> In-Reply-To: <54db43990809081203x11e0bae3u2909c1158d44832b@mail.gmail.com> References: <20080908033359.D75A810656C2@hub.freebsd.org> <48C50960.17104.472ED1DE@iwrtech.iwr.ru.ac.za> <C356114F-FE1E-46BD-94B1-CADAB135F482@identry.com> <54db43990809081203x11e0bae3u2909c1158d44832b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Anyway, I guess what I should do is patch this to the latest 6.3 >> version? >> > > My strategy was to do a source-base upgrade to 6.3-RELEASE, and then > use freebsd-update to apply critical patches. Freebsd-update only > works on -RELEASE versions with generic kernels, but I find it much > faster and easier than trying to do upgrades from source. You also > need to keep track of ports that need updating: use portaudit for > that. Unfortunately, this sounds about right, to me. Well, I'm going to have to practice long and hard before trying this on our production machines... I need to get a feeling for just how dangerous a process this is, before trying it. It's one of those things you want to do right the first time! -- John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9C33E030-B480-4E3C-B1A0-9AA7B77B7E3C>