Re: So How Hard Is Moving From 6.3 To 7.0?
On Monday 03 March 2008, Mark Ovens wrote: Which leads me to ask if there are likely to be any issues with dual-booting 6.3-STABLE (as of ~1 month ago) and 7.0-RELEASE? I vaguely recall from way back there being issues with dual-booting multiple versions of FreeBSD. That's what I'm currently doing. No problems ... yet. I've only been running 7.0 alongside 6.3 for a couple of days so far but I've previously had 6.2 and 6.3 happily living side by side for some time without problems. Maybe that was when trying to install both in the same slice? Mine will be installed on separate hard disks. I'm using 2 different slices on the same drive. The only thing I could think may possibly be an issue is the FreeBSD Boot Manager. I'm using grub so perhaps I'm a bit safer in that respect. -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: So How Hard Is Moving From 6.3 To 7.0?
This post hasn't appeared on the list after almost 24 hours so I'm re-posting. Apologies if it appears twice. It seems that about 50% of the posts I make to the lists (-questions and -ports) never show up. Matthew Seaman wrote: I've been doing a bunch of 6.x - 7.0 upgrades recently. Here's a few hints I've picked up along the way: [snip the gory details] Thanks for that Matthew, it confirms that I've made the right decision to do a completely clean install :-) Which leads me to ask if there are likely to be any issues with dual-booting 6.3-STABLE (as of ~1 month ago) and 7.0-RELEASE? I vaguely recall from way back there being issues with dual-booting multiple versions of FreeBSD. Maybe that was when trying to install both in the same slice? Mine will be installed on separate hard disks. The only thing I could think may possibly be an issue is the FreeBSD Boot Manager. The current setup uses the FBSD BM to boot FBSD and Ubuntu on separate disks - it's the Ubuntu disk that I will be zapping to install 7 - is there anything to watch out for (apart from the obvious stupidity of selecting the wrong disk to newfs ;-) ) Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: So How Hard Is Moving From 6.3 To 7.0?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Daneliuk wrote: | I have a stable 6.3 production server. I would stop right there. Question is why would you change something that simply works? - -- Best regards, Bogdan Culibrk [EMAIL PROTECTED] http://default.co.yu/~bc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfKic4ACgkQo6C4vAhYtCBqKwCeOCybASwKMu4HV7oTeJRmaeUa eiEAnjyKaPVDYXv/aiNIqeQQx+bbbhtO =Fxf9 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: So How Hard Is Moving From 6.3 To 7.0?
Tim Daneliuk wrote: I have a stable 6.3 production server. If I buildworld/kernel for 7.0, install them, and reboot, will everything pretty much work the same as it did under 6.3, or have file locations, userland configuration, etc. changed? Will my 6.3 binaries run unchanged on 7.0 as well? I've been doing a bunch of 6.x - 7.0 upgrades recently. Here's a few hints I've picked up along the way: *) The base system update from 6.x to 7.0 can be done by following the usual 'make buildworld buildkernel ; make installkernel ... ' procedure as shown in the handbook and also described in /usr/src/UPDATING. Because you're doing a major version number update, following the strict procedure is even more important than usual. If you have servers in a remote facility, going on-site or having remote console access is strongly advisable. *) The mergemaster steps are important. You will definitely need to run 'mergemaster -p' before doing the buildworld part as there's a new standard 'ftp' group. The mergemaster step after installation is going to prompt you to delete, merge or replace quite a large number of files -- certainly affecting most of the contents of /etc/mtree, /etc/periodic/ and /etc/rc.d/ plus lots of bluetooth and openbsm bits. This is kind of tedious, and usually it requires bouncing on the 'i' key to replace the old default version of the file with the new one, but you do need to take care with this step as mistakes here can have a horribly negative impact on your machine. *) Be careful of the last step in the OS upgrade procedure. 'make delete-old-libs' will render all of your 6.x compiled software inoperable. I find it best to simply delay that step until after all of the ported software has been recompiled under 7.0. Alternatively, you can install the misc/compat6x port, but you will still need to 'make delete-old-libs' and restart everything (for which the simplest method is to reboot once more). *) It may seem like an enormous burden, but you really do need to recompile every port you have installed once you're running 7.0 In general, software compiled under 6.x will run perfectly fine under 7.0 (so long as libc.so.6 etc. are present and visible to ld-elf.so.1) -- but you will not be able to update it or install anything that depends on dynamic loading into another application without a great deal of grief. (Eg. any php5 modules have to be linked against the same shlibs as the core php binary, and also if you're using mod_php5, against the same shlibs as the apache process that is loaded into). Not doing this is to trade off a few hours of watching compiler output scrolling up your screen for days of stress and frustration at some indeterminate future point. *) The point about not mixing software loadable objects compiled against different versions of libc.so et al also applies *while* you are updating all your ports. Certain software packages will cease to operate during this procedure. Others will carry on just fine. If you're upgrading a system where avoiding service downtime is critical, then, if you can swing it, doing a practice run on a similarly configured scratch box is a good idea. Also good is to build offline or otherwise obtain pkgs of all the software you need to update on the critical server. *) Unfortunately, one of the software packages affected by the above considerations is portupgrade(1) -- it is quite likely to blow up in your face if you just naively run 'portupgrade -fa'. The best way of getting round this is to first delete portupgrade and critical dependencies using the OS supplied tools (pkg_delete) and then re-install from scratch. eg, something like this: # pkg_info -rx portupgrade (to see what portupgrade depends on) # pkg_delete -f ruby-1.8.6.111_1,1 ruby18-bdb44-0.6.2 db44-4.4.20.4 portupgrade-devel-2.4.3 openssl-0.9.8g perl-5.8.8_1 # cd /usr/ports/ports-mgmt/portupgrade-devel # make install (you may or may not depend on the ports version of OpenSSL, and the version numbers of other packages are likely to be different. Also, I'm using portupgrade-devel here -- plain portupgrade is also likely to be seen in the wild) Once you've done that, you will be able to proceed with 'portupgrade -fa' for the rest of your software base and it should run smoothly. Of course, users of portmaster(1) have a much easier time here -- it's a shell script and only depends on facilities provided by the core OS. *) If your upgrade doesn't run entirely smoothly or you have to restart it for some other reason, then you can use a command line like this
Re: So How Hard Is Moving From 6.3 To 7.0?
Would tend to agree. I just lost a machines hdd so it's a good opportunity to build with latest release but otherwise, i have still have a 6.0 box running strong and executing tasks which it was built for. No plans to upgrade. ezat Bogdan Ćulibrk wrote: ---= --BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Daneliuk wrote: | I have a stable 6.3 production server. I would stop right there. Question is why would you change something that simply works? - -- Best regards, Bogdan Culibrk [1]bc= @default.co.yu [2]http://default.co.yu/~bc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfKic4ACgkQo6C4vAhYtCBqKwCeOCybASwKMu4HV7oTeJRmaeUa eiEAnjyKaPVDYXv/aiNIqeQQx+bbbhtO =Fxf9 -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list [4]http://lists.freebsd.org/mailman/listinfo/= freebsd-questions To unsubscribe, send any mail to [5][EMAIL PROTECTED] References 1. 3Dmailto:[EMAIL PROTECTED] 2. 3Dhttp://defa=/ 3. 3Dmailto:[EMAIL PROTECTED] 4. 3Dhttp://lists.freebsd.org/mailm 5. 3Dmailto:freebsd-questions-unsub___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: So How Hard Is Moving From 6.3 To 7.0?
At 05:25 AM 3/2/2008, Ezat - Ezatech wrote: Would tend to agree. I just lost a machines hdd so it's a good opportunity to build with latest release but otherwise, i have still have a 6.0 box running strong and executing tasks which it was built for. No plans to upgrade. ezat Bogdan Äulibrk wrote: ---= --BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Daneliuk wrote: | I have a stable 6.3 production server. I would stop right there. Question is why would you change something that simply works? - -- Best regards, Bogdan Culibrk Why upgrade? In my case it was that performance would be so much better under 7 than under 6.X. It is inevitable that systems need to be upgraded as versions become EOL (end of life and no longer supported) or replaced. In my case I run FreeBSD on servers which have a much longer life than client desktops or laptops. For those that have been doing FreeBSD a while, as I have since 1.X. Each upgrade has its problems. It just takes some patience and ingenuity to work around them. These mailing lists with the large community help a great deal. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: So How Hard Is Moving From 6.3 To 7.0?
At 07:12 PM 2/1/2008, Tim Daneliuk wrote: I have a stable 6.3 production server. If I buildworld/kernel for 7.0, install them, and reboot, will everything pretty much work the same as it did under 6.3, or have file locations, userland configuration, etc. changed? Will my 6.3 binaries run unchanged on 7.0 as well? TIA, -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ Tim, I am still working on my first server migration. I followed the instructions in /usr/src/UPDATING, but still had problems. I also did a portupgrade -faP to make the ports as per the release notes. Unfortunately not all worked after that. I had issues with apache22 and clamav, so I rebuilt and reinstalled both of those ports. I still don't have xorg and gnome working. So needless to say this is a much longer update process than previous versions. I did NOT try the binary update from CD or the new binary update utility. I believe most of the issues I have had are because of changes in the libraries specifically to the threads. Oh, I started my update on Friday Morning. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: So How Hard Is Moving From 6.3 To 7.0?
On Feb 1, 2008, at 8:12 PM, Tim Daneliuk wrote: I have a stable 6.3 production server. If I buildworld/kernel for 7.0, install them, and reboot, will everything pretty much work the same as it did under 6.3, or have file locations, userland configuration, etc. changed? Will my 6.3 binaries run unchanged on 7.0 as well? TIA, You will want to check /usr/src/UPDATING and /usr/ports/UPDATING for changes before doing any kind of update. -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
