Date: Tue, 17 Oct 2006 19:11:59 -0400 From: Kris Kennaway <kris@obsecurity.org> To: FreeBSD Security Officer <cperciva@freebsd.org>, FreeBSD Stable <freebsd-stable@freebsd.org>, freebsd security <freebsd-security@freebsd.org> Subject: Re: FreeBSD 4.x EoL Message-ID: <20061017231159.GA67830@xor.obsecurity.org> In-Reply-To: <20061017230722.GH8866@gargantuan.com> References: <453531C9.7080304@freebsd.org> <20061017230722.GH8866@gargantuan.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 17, 2006 at 07:07:22PM -0400, Michael W. Oliver wrote: > Colin, >=20 > Thanks for the verbose and reasoned explanation. Since the email last > week, I have taken the opportunity to upgrade two machines, one here and > one remote (both with serial console) from 4.9->5.5->6.2PRE, and while I > can't say that I did it blindfolded, it wasn't too painful. The upgrade > instructions at... >=20 > http://www.freebsd.org/releases/5.3R/migration-guide.html >=20 > ...were as close to perfect as could be (and for those who might ask me > for a step-by-step howto, look to the above URL). A few things that I > should mention to others trying this are... >=20 > 0. Backup, and then check your backups! >=20 > 1. Be prepared to spend a lot of time in single-user mode, especially > for the 4->5 step, because there is a LOT for mergemaster to do. The > step from 5->6 is not nearly as painful. I didn't try to do the > installworld and mergemaster in multiuser, and if you do then have a > bigger set than I do. >=20 > 2. Trust the migration guide when it says to use a default kernel > configuration file unless you are 100% prepared to reap what you sow. >=20 > 3. Be prepared to spend a lot of time (depending on the speed of your > machines) rebuilding all of your ports. Don't skimp on this step. >=20 > 4. On one of my machines (the local one, thank God!), I started getting > weird pauses and bus errors when trying to rebuild my ports, and then > noticed that the acpi.ko wasn't being loaded at boot. Turns out that I > had disabled ACPI in the BIOS back when the machine was originally built > for v4. Since switching on ACPI in the BIOS, those issues have totally > cleared. Good advice. You can make step 3 easier by using the precompiled packages where possible, e.g. "portupgrade -faP" Kris --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFNWM/Wry0BWjoQKURAoOVAJ4pdcyMNe9xo3e8tbAkPgzRxKVRIgCgvf97 XtDc7KPBbLrC71w8xrmTl2k= =lUes -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061017231159.GA67830>