upgrade a couple of nearly identical machines
I run three machines with FreeBSD-4.11 and lots of the same ports installed. Upgrading these three must be more easy then running portupgrade on every machine again and again, upgrading the same ports multiple times. This is waste of cpu power ;-) Does anybody has suggestions on how to handle this situation in a more practicle way? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11 ++ FreeBSD 5.3 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrade a couple of nearly identical machines
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2005-03-13, Dick Hoogendijk scribbled these curious markings: I run three machines with FreeBSD-4.11 and lots of the same ports installed. Upgrading these three must be more easy then running portupgrade on every machine again and again, upgrading the same ports multiple times. This is waste of cpu power ;-) Make packages of the ports, and then install them on each machine? Use devel/distcc to split up the load for each? Best Regards, Christopher Nehren -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCNJGhk/lo7zvzJioRAqpoAJ9/XfkAxOYBqe/hu+jN3J0nIk4jAgCfSNQh WFbdBVpIKQDcrpJs+zh27y8= =SHZn -END PGP SIGNATURE- -- I abhor a system designed for the user, if that word is a coded pejorative meaning stupid and unsophisticated. -- Ken Thompson If you ask the wrong questions, you get answers like 42 and God. Unix is user friendly. However, it isn't idiot friendly. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrade a couple of nearly identical machines
On Sun, Mar 13, 2005 at 07:57:57PM +0100, Dick Hoogendijk wrote: I run three machines with FreeBSD-4.11 and lots of the same ports installed. Upgrading these three must be more easy then running portupgrade on every machine again and again, upgrading the same ports multiple times. This is waste of cpu power ;-) Does anybody has suggestions on how to handle this situation in a more practicle way? You could use portupgrade to upgrade one machine with the -W option so it won't clean up after itself, then nfs mount the ports directory on another machine and use portupgrade -wWar to upgrade them if I'm not mistaken. If that doesn't work, you could create a binary package of everything installed and copy them over and install them with pkg_add. -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11 ++ FreeBSD 5.3 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: CEE1 AAE2 F66C 59B5 34CA C415 6D35 E847 0118 A3D2 pgpzhGy5whZXp.pgp Description: PGP signature
