Date: Mon, 07 Jun 2004 23:08:27 +0200 From: Roman Kennke <roman@ontographics.com> To: Lucas Holt <Luke@FoolishGames.com> Cc: freebsd-questions@freebsd.org Subject: RE: Upgrading FreeBSD to a new release Message-ID: <1086642506.7492.9.camel@moonlight.localdomain> In-Reply-To: <200406071523.i57FN6dj074033@adsl-68-76-19-75.dsl.klmzmi.ameritech.net> References: <200406071523.i57FN6dj074033@adsl-68-76-19-75.dsl.klmzmi.ameritech.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-4Y7+DAnn1GY9PxpmazJ4 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Ok, thank you all for response. As far as I see things now, the best way to upgrade from one stable release to the next is via source upgrade. Configuration files probably need some attention, because mergemaster cannot be run remotely. Upgrading from one major release to the next (4.x -> 5.x) is practically not possible remotely, or at least _very_ difficult. Upgrade problems like the statd issue will not occur with stable branches. There is no other good way to upgrade remotely, is it? What about old files from the previous release? Will these be deleted properly with source upgrade? I've heard of occasional problems with old libraries lying around. Are there any efforts to improve the software managment in the base system? NetBSD for instance has once started a system-pkgsrc project (but does not seem to continue this), which I think is a great idea. Managing the system software with pkg_add and friends would be nice IMO. /Roman --=-4Y7+DAnn1GY9PxpmazJ4 Content-Type: application/pgp-signature; name=signature.asc Content-Description: Dies ist ein digital signierter Nachrichtenteil -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAxNlJbTKKqwP/8kARAoNgAKCFuS7qwnHzRBgnjn2+3R7cuYIqswCeKDna jaO4qoeyus3vkQBh98hAdzs= =ENVK -----END PGP SIGNATURE----- --=-4Y7+DAnn1GY9PxpmazJ4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1086642506.7492.9.camel>