Re: Upgrading very old installation
On 15 July 2011 22:12, Balázs Mátéffy repcs...@gmail.com wrote: On 15 July 2011 22:46, Roland Smith rsm...@xs4all.nl wrote: On Fri, Jul 15, 2011 at 08:20:52AM -0400, Jaime Kikpole wrote: I'm running a FreeBSD 6.x server that hasn't been updated in about 1.5 years. atlas:~uname -mprs FreeBSD 6.4-RELEASE-p8 i386 i386 I've been using the cvsup/make method of upgrades for years and only used freebsd-upgrade once. I'm not sure if either method can handle a 6.x to 8.x upgrade. They are tested for upgrading to the next major version. Who knows if it will work across two major versions? Personally I wouldn't want to be the one ot try it out. :-) I also have a bunch of ports in this server (e.g. apache, postfix, etc.) Once the OS is updated, should I just portupgrade them all? Doesn't work reliably across major version updates. When updating to a newer major version, the best way is to delete all ports (save their config files of course), scrub the /usr/local tree clean and then re-install them. Matthews advice of re-installing 8.2 on a second harddrive is probably the easiest and safest way to go. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) Hi, I would try to update the split mirror of the 6.4 to 8.2, I did manage to update couple of years back from Releng6 to Current 8 :). Did the usual make kernel / world stuff mergemaster prebuild in the middle and mergemaster after the update then I rebuilt all the ports. I recently did a 6.4-STABLE 8.2-RELEASE-p2 migration to another server, but without using only some initial old config files from the old system because I had to build a better environment with other software for the same role (almost the same thing that Matt recommended you). For me this is a longer procedure then updating all the software and checking for maybe now deprecated options and other problems. So I think its down to your level of knowledge and personal preference ( whether you want to check what is to problem in case something goes wrong- I like this because I get to know the system and the inner workings in more detail). I personally don't like freebsd-update, and if your are new to the build from source way, you should really go with building up from scratch, then migrate. In case you want to update have a WORKING backup, and do a test run for the update (restore your 6.4 on a test machine and try to update it) before you bring down the productive system. Good luck! Regards, Balazs. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Also one thing to watch with ports is thing like lang/php tend to jump a point release or a major release. Its kind of anoying in my opinion that lang/php can be php v4, 5.2 or 5.3 depending on what version of the os you run, when there is stall a php52 port in say 8-stable. Makes keeping consistent php versions more difficult. In my experience portmaster is better than portupgrade as it doesnt have to mess around with binary dbs of the ports ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrading very old installation
On 15/07/2011 13:20, Jaime Kikpole wrote: I'm running a FreeBSD 6.x server that hasn't been updated in about 1.5 years. atlas:~uname -mprs FreeBSD 6.4-RELEASE-p8 i386 i386 What is the recommended way to upgrade it to something current? Should I upgrade it to the most recent 6.x and then to 7.x and then to 8.x? Or should I use a more direct route, upgrading it straight to the 8-RELEASE branch? You'll almost certainly find it quicker and less painful to just reinstall using an up to date version of FreeBSD. Personally, I'd go and buy a new hard drive for the machine, install the latest OS and applications on that and then copy over data etc. It helps if you can have both drives mounted in the same machine at once. There are variations on this theme -- for instance if your server has mirrored HDDs then you can split the mirror, re-install on one half, reconcile configurations, data, user accounts between the two halves and ultimately resynch the old drive to the new one. The big advantage of this sort of approach is that you get your new install up and running and tested before you need to commit to the potentially irreversible step of overwriting your last copy of the old one. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Upgrading very old installation
On 7/15/2011 9:38 AM, Matthew Seaman wrote: On 15/07/2011 13:20, Jaime Kikpole wrote: I'm running a FreeBSD 6.x server that hasn't been updated in about 1.5 years. atlas:~uname -mprs FreeBSD 6.4-RELEASE-p8 i386 i386 What is the recommended way to upgrade it to something current? Should I upgrade it to the most recent 6.x and then to 7.x and then to 8.x? Or should I use a more direct route, upgrading it straight to the 8-RELEASE branch? You'll almost certainly find it quicker and less painful to just reinstall using an up to date version of FreeBSD. Personally, I'd go and buy a new hard drive for the machine, install the latest OS and applications on that and then copy over data etc. It helps if you can have both drives mounted in the same machine at once. There are variations on this theme -- for instance if your server has mirrored HDDs then you can split the mirror, re-install on one half, reconcile configurations, data, user accounts between the two halves and ultimately resynch the old drive to the new one. The big advantage of this sort of approach is that you get your new install up and running and tested before you need to commit to the potentially irreversible step of overwriting your last copy of the old one. Cheers, Matthew Excellent advice, Matt. You rock. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrading very old installation
On 15 July 2011 16:25, Steven Friedrich free...@insightbb.com wrote: On 7/15/2011 9:38 AM, Matthew Seaman wrote: On 15/07/2011 13:20, Jaime Kikpole wrote: I'm running a FreeBSD 6.x server that hasn't been updated in about 1.5 years. atlas:~uname -mprs FreeBSD 6.4-RELEASE-p8 i386 i386 What is the recommended way to upgrade it to something current? Should I upgrade it to the most recent 6.x and then to 7.x and then to 8.x? Or should I use a more direct route, upgrading it straight to the 8-RELEASE branch? You'll almost certainly find it quicker and less painful to just reinstall using an up to date version of FreeBSD. Personally, I'd go and buy a new hard drive for the machine, install the latest OS and applications on that and then copy over data etc. It helps if you can have both drives mounted in the same machine at once. There are variations on this theme -- for instance if your server has mirrored HDDs then you can split the mirror, re-install on one half, reconcile configurations, data, user accounts between the two halves and ultimately resynch the old drive to the new one. The big advantage of this sort of approach is that you get your new install up and running and tested before you need to commit to the potentially irreversible step of overwriting your last copy of the old one. Cheers, Matthew Excellent advice, Matt. You rock. __**_ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-** unsubscr...@freebsd.org freebsd-questions-unsubscr...@freebsd.org You need to do your risk analysis to decide what route to take.The safe way is to do the 2nd drive method mentioned previously. If you decide to upgrade I would advise you to do the make world method. Its older and therefore more tested, and as you have said you are more familiar with it. I have done about 40+ upgrades from 6.x to 8.x. I did a step to 7 in the middle, and all worked fine. The only oddity I found was that when I went from 7.x to 8.x dangerously dedicated disks devices were presented differently. In 7.x you had ad0a, ad0b etc under /dev, but you also had ad0s1a, ad0s1b etc as well In 8.x you only had ones of the format ad0a. the oddity was the ad0s1a format ones being present prior to 8 being present, as I wouldn't have expected these. This was only and issue as whoever had built to box i inherited had used the ad0s1a format ones so on rebooting to 8.x we had issues. A quick edit of fstab fixed the issue though. Also make sure you have mergemaster configured proply as it will take a load of work out of the upgrades. Here is my rc for it. You may need to tune it a little cat /etc/mergemaster.rc AUTO_INSTALL=YES AUTO_UPGRADE=YES PRESERVE_FILES=yes PRESERVE_FILES_DIR=/var/mergemaster/preserved-files-`date +%y%m%d-%H%M%S` IGNORE_FILES=/etc/crontab /etc/fstab /etc/group /etc/hosts /etc/inetd.conf /etc/make.conf /etc/master.passwd /etc/motd /etc/newsyslog.conf /etc/ntp.conf /etc/ntp.drift /etc/profile /etc/rc.conf /etc/resolv.conf /etc/services /etc/shells /etc/syslog.conf /etc/ssh/sshd_config /etc/ssh/ssh_host_key /etc/ssh/ssh_host_key.pub /etc/ssh/ssh_host_rsa_key /etc/ssh/ssh_host_rsa_key.pub /etc/passwd /etc/rc.conf.local /etc/zfs/exports /etc//namedb/named.conf /etc/periodic.conf /etc/hosts.allow /etc/hosts /etc/pf.conf /etc/sysctl.conf /etc/make.conf /etc/src.conf /etc/mail/aliases /etc/mail/mailer.conf /etc/remote ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrading very old installation
On Fri, Jul 15, 2011 at 08:20:52AM -0400, Jaime Kikpole wrote: I'm running a FreeBSD 6.x server that hasn't been updated in about 1.5 years. atlas:~uname -mprs FreeBSD 6.4-RELEASE-p8 i386 i386 I've been using the cvsup/make method of upgrades for years and only used freebsd-upgrade once. I'm not sure if either method can handle a 6.x to 8.x upgrade. They are tested for upgrading to the next major version. Who knows if it will work across two major versions? Personally I wouldn't want to be the one ot try it out. :-) I also have a bunch of ports in this server (e.g. apache, postfix, etc.) Once the OS is updated, should I just portupgrade them all? Doesn't work reliably across major version updates. When updating to a newer major version, the best way is to delete all ports (save their config files of course), scrub the /usr/local tree clean and then re-install them. Matthews advice of re-installing 8.2 on a second harddrive is probably the easiest and safest way to go. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpahJmEbMcxn.pgp Description: PGP signature
Re: Upgrading very old installation
On 15 July 2011 22:46, Roland Smith rsm...@xs4all.nl wrote: On Fri, Jul 15, 2011 at 08:20:52AM -0400, Jaime Kikpole wrote: I'm running a FreeBSD 6.x server that hasn't been updated in about 1.5 years. atlas:~uname -mprs FreeBSD 6.4-RELEASE-p8 i386 i386 I've been using the cvsup/make method of upgrades for years and only used freebsd-upgrade once. I'm not sure if either method can handle a 6.x to 8.x upgrade. They are tested for upgrading to the next major version. Who knows if it will work across two major versions? Personally I wouldn't want to be the one ot try it out. :-) I also have a bunch of ports in this server (e.g. apache, postfix, etc.) Once the OS is updated, should I just portupgrade them all? Doesn't work reliably across major version updates. When updating to a newer major version, the best way is to delete all ports (save their config files of course), scrub the /usr/local tree clean and then re-install them. Matthews advice of re-installing 8.2 on a second harddrive is probably the easiest and safest way to go. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) Hi, I would try to update the split mirror of the 6.4 to 8.2, I did manage to update couple of years back from Releng6 to Current 8 :). Did the usual make kernel / world stuff mergemaster prebuild in the middle and mergemaster after the update then I rebuilt all the ports. I recently did a 6.4-STABLE 8.2-RELEASE-p2 migration to another server, but without using only some initial old config files from the old system because I had to build a better environment with other software for the same role (almost the same thing that Matt recommended you). For me this is a longer procedure then updating all the software and checking for maybe now deprecated options and other problems. So I think its down to your level of knowledge and personal preference ( whether you want to check what is to problem in case something goes wrong- I like this because I get to know the system and the inner workings in more detail). I personally don't like freebsd-update, and if your are new to the build from source way, you should really go with building up from scratch, then migrate. In case you want to update have a WORKING backup, and do a test run for the update (restore your 6.4 on a test machine and try to update it) before you bring down the productive system. Good luck! Regards, Balazs. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
