Date: Fri, 15 Apr 2016 11:15:36 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: Upgrading from FreeBSD 4.1 Message-ID: <76a9fc3a-e1f4-4599-1173-a928f528fe82@freebsd.org> In-Reply-To: <003401d196ee$258ee680$70acb380$@zamnet.zm> References: <003401d196ee$258ee680$70acb380$@zamnet.zm>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --MjfxXcGPjMNoTCFqDVlTIpTKGNPBITInO Content-Type: multipart/mixed; boundary="QHVcMETv7xqT9U0eS7w5NDt2tEMo9RiSV" From: Matthew Seaman <matthew@freebsd.org> To: freebsd-questions@freebsd.org Message-ID: <76a9fc3a-e1f4-4599-1173-a928f528fe82@freebsd.org> Subject: Re: Upgrading from FreeBSD 4.1 References: <003401d196ee$258ee680$70acb380$@zamnet.zm> In-Reply-To: <003401d196ee$258ee680$70acb380$@zamnet.zm> --QHVcMETv7xqT9U0eS7w5NDt2tEMo9RiSV Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 04/15/16 09:09, Allan Kapoma wrote: > I'm running FreeBSD 4.10 and I want to upgrade the system to a later ve= rsion > of FreeBSD.=20 >=20 > =20 >=20 > However, whenever I run commands to update the system (# freebsd-update= ), or > install portsnap, or install portmanager, or pkg commands, portsnap fet= ch > extract, I'm getting the message that command not found=20 >=20 > =20 >=20 > The my output for uname -a is shown below >=20 > =20 >=20 > relay# uname -a >=20 > FreeBSD relay.zamnet.zm 4.10-RELEASE FreeBSD 4.10-RELEASE #1: Fri Nov 1= 2 > 06:54:4 =20 >=20 > =20 >=20 > I'm asking for assistance on how I can enable the system (FreeBSD 4.10)= to > run these commands and hopefully update my system and packages on it Given that FreeBSD 4.10 is so old -- 4.10-RELEASE was around 9 years ago -- then I'd be concerned about the hardware it's running on. Not just because of Moore's Law, but simply because components that old are probably past the end of their expected lifetimes. Certainly for hard drives -- the churn involved in upgrading the system can quite easily trigger drive failure. If I were you, I'd start with a fresh install of FreeBSD 10.3-RELEASE on at least a new hard drive, but preferably an entirely new server. Then port over all your local settings and software load. This also has the very useful property that your old system can be left running while you do the build, and still be available afterwards if you need to revert back to it. If you can't afford new components or new hardware, whatever you do, don't try and do an in-place upgrade: the partitioning layout needed has changed quite a lot in the past decade, and you'll find that modern FreeBSD needs much more space in the root partition than 4.10 did. You'll end up with a full filesystem and missing important files. In this situation, you would be better off wiping the system and doing a reinstall from scratch. Cheers, Matthew --QHVcMETv7xqT9U0eS7w5NDt2tEMo9RiSV-- --MjfxXcGPjMNoTCFqDVlTIpTKGNPBITInO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJXEL9PAAoJEABRPxDgqeTnntAP+weiQLIK+wRuW5nZMs0fbvU3 cIrgcJ5zx076Gefde9m+uYqI0dU4ay9eUcqE+4pi4exXpn6oQ72sfjDvkdhLfPAX F0L9KuYE5AxCrSp9dlEhH3q1L+mM6GP0YcSCeIHHA97EyZvH9VbI3fr1fZFFmDAV /pSHPWX/IYAdf9sGDgABZ/vWlrohu+pwSU4VQ92pw0jtuq73IlZ0ZsfkG2aHhytj GWvk9OyJUiyRRjdbRqEnFr98tbN7PhgNUOfU8tod6XNcAvfl9PjACY/p4JxDVxhS BN2deHDL2UGeqs4xvBRUnUyqITlvnedKpkfPaykjwdt0jPmhntzfsHChvrT//4Dv 3RUeTVpcfh5WHFrJ8pDQ3VqKwiT52/5idTgyyPoFQEFnsKatWeLK50kWIlugTslg nln302QtSe8jJ7MftBfZDcuYh7q91tjo3cj8znowztM8H/fd2OxCu1QXzkEX07Bv 2pRQeJ4/iNIUgOcw9j1S67EeqhJtStrPGLVG8DYsGPJLguhBXgcY2e5eAUuI7Ugl 504H0CO+h1EY7kE5uu092S66wXVHSzikMQOorIba7/daoOpkhkHYjVJeObvqteHX 4baK4RSNc96/HEDdCqiIHojpQLXFYJH9LTOilbO/GXShYGq87z+uR9X7GnRsfHz6 Z6dtKcg5NL6DDZ/7sZwU =Swbq -----END PGP SIGNATURE----- --MjfxXcGPjMNoTCFqDVlTIpTKGNPBITInO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?76a9fc3a-e1f4-4599-1173-a928f528fe82>