Re: preparing for an upgrade
On Mon, Nov 24, 2008 at 10:00 AM, Kelly Martin [EMAIL PROTECTED] wrote: This weekend I finally got around to trying freebsd-update on 6.2. It is there and works, but it would only update me to 6.2-RELEASE-p11. It told me 6.2 was past its end-of-life date (which I already knew). There was no obvious way to upgrade to 6.3 binaries. I checked the man page and the configuration file too. Maybe the newer version of freebsd-update allows upgrades between point versions? (ie., 6.3 - 6.4 ?) Well, I found the answer myself by comparing freebsd-update on FreeBSD 6.2 and 6.3. The version on 6.3 adds the -r newrelease option, which doesn't exist on 6.2... so it looks like moving up a point release using this tool is first possible with FreeBDD 6.3 - 6.4. I know 6.2 isn't supported anymore, but it works fine for me. kelly ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: preparing for an upgrade
On Tue, Nov 18, 2008 at 9:07 PM, andrew clarke [EMAIL PROTECTED] wrote: On Tue 2008-11-18 16:47:20 UTC-0700, Kelly Martin ([EMAIL PROTECTED]) wrote: With the release of FreeBSD 6.4 imminent, I'd like to prepare for an upgrade from FreeBSD 6.2 - 6.4. Have you considered using freebsd-update? From memory, it supports 6.2. This weekend I finally got around to trying freebsd-update on 6.2. It is there and works, but it would only update me to 6.2-RELEASE-p11. It told me 6.2 was past its end-of-life date (which I already knew). There was no obvious way to upgrade to 6.3 binaries. I checked the man page and the configuration file too. Maybe the newer version of freebsd-update allows upgrades between point versions? (ie., 6.3 - 6.4 ?) I'm a little confused about different versions of the ports tree. What I mean is, I keep updating my FreeBSD 6.2 ports tree and have never had any problems... it just works. I'm assuming the 6.4 ports tree is a little different and specific to 6.4? No, there is only one ports tree shared between all FreeBSD versions. If you already have an updated ports tree with a 6.2 installation, you can keep using that with 6.4 (or even 7.x). Thanks very much to you and others for putting me on track about how the ports tree works! kelly ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
preparing for an upgrade
With the release of FreeBSD 6.4 imminent, I'd like to prepare for an upgrade from FreeBSD 6.2 - 6.4. Please excuse my ignorance but in my mind here's what I plan to do when it's available: 1. install / run the upgrade script using CD-ROM media to a 6.4 GENERIC kernel, reboot 2. customize the kernel to my hardware (like I did in 6.2), reboot 3. portsnap fetch update (to get the latest ports tree for 6.4) 4. portupgrade -ai (to upgrade any outdated ports) Will this work? I'm a little confused about different versions of the ports tree. What I mean is, I keep updating my FreeBSD 6.2 ports tree and have never had any problems... it just works. I'm assuming the 6.4 ports tree is a little different and specific to 6.4? The port system is **so much better** than using ports on my OpenBSD systems! thanks, kelly ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: preparing for an upgrade
On Tue, Nov 18, 2008 at 6:47 PM, Kelly Martin [EMAIL PROTECTED] wrote: With the release of FreeBSD 6.4 imminent, I'd like to prepare for an upgrade from FreeBSD 6.2 - 6.4. Please excuse my ignorance but in my mind here's what I plan to do when it's available: 1. install / run the upgrade script using CD-ROM media to a 6.4 GENERIC kernel, reboot 2. customize the kernel to my hardware (like I did in 6.2), reboot 3. portsnap fetch update (to get the latest ports tree for 6.4) 4. portupgrade -ai (to upgrade any outdated ports) Will this work? I'm a little confused about different versions of the ports tree. What I mean is, I keep updating my FreeBSD 6.2 ports tree and have never had any problems... it just works. I'm assuming the 6.4 ports tree is a little different and specific to 6.4? The port system is **so much better** than using ports on my OpenBSD systems! thanks, kelly ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] no ports doesn't go to a certain release, once a FreeBSD version is no longer support you can bet that some ports will not work correctly on that version. for example the ports you have now is the same as on 7.x ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: preparing for an upgrade
On Tue 2008-11-18 16:47:20 UTC-0700, Kelly Martin ([EMAIL PROTECTED]) wrote: With the release of FreeBSD 6.4 imminent, I'd like to prepare for an upgrade from FreeBSD 6.2 - 6.4. Have you considered using freebsd-update? From memory, it supports 6.2. Please excuse my ignorance but in my mind here's what I plan to do when it's available: 1. install / run the upgrade script using CD-ROM media to a 6.4 GENERIC kernel, reboot 2. customize the kernel to my hardware (like I did in 6.2), reboot 3. portsnap fetch update (to get the latest ports tree for 6.4) 4. portupgrade -ai (to upgrade any outdated ports) I don't think there will be any need to rebuild your ports after upgrading from 6.2 to 6.4. (The situation is different if you were going from 6.2 to 7.1 though.) Will this work? I'm a little confused about different versions of the ports tree. What I mean is, I keep updating my FreeBSD 6.2 ports tree and have never had any problems... it just works. I'm assuming the 6.4 ports tree is a little different and specific to 6.4? No, there is only one ports tree shared between all FreeBSD versions. If you already have an updated ports tree with a 6.2 installation, you can keep using that with 6.4 (or even 7.x). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: preparing for an upgrade
On Wed, Nov 19, 2008 at 03:07:32PM +1100, andrew clarke wrote: On Tue 2008-11-18 16:47:20 UTC-0700, Kelly Martin ([EMAIL PROTECTED]) wrote: With the release of FreeBSD 6.4 imminent, I'd like to prepare for an upgrade from FreeBSD 6.2 - 6.4. Have you considered using freebsd-update? From memory, it supports 6.2. Please excuse my ignorance but in my mind here's what I plan to do when it's available: 1. install / run the upgrade script using CD-ROM media to a 6.4 GENERIC kernel, reboot 2. customize the kernel to my hardware (like I did in 6.2), reboot 3. portsnap fetch update (to get the latest ports tree for 6.4) 4. portupgrade -ai (to upgrade any outdated ports) I don't think there will be any need to rebuild your ports after upgrading from 6.2 to 6.4. (The situation is different if you were going from 6.2 to 7.1 though.) Threading library changes are a good reason to rebuild your ports in this case. I'm a little confused about different versions of the ports tree. What I mean is, I keep updating my FreeBSD 6.2 ports tree and have never had any problems... it just works. I'm assuming the 6.4 ports tree is a little different and specific to 6.4? No, there is only one ports tree shared between all FreeBSD versions. If you already have an updated ports tree with a 6.2 installation, you can keep using that with 6.4 (or even 7.x). You can only use it on 7.x if you add compatibility libraries and ensure your kernel has COMPAT_FREEBSD6 in it. These libraries have given some users trouble in the past; you will find most people advocate rebuilding all ports from scratch (pkg_delete -af please) when upgrading between major FreeBSD versions (e.g. 6.x - 7.x). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: preparing for an upgrade
On 11/18/08 21:43, Jeremy Chadwick wrote: [...] You can only use it on 7.x if you add compatibility libraries and ensure your kernel has COMPAT_FREEBSD6 in it. These libraries have given some users trouble in the past; you will find most people advocate rebuilding all ports from scratch (pkg_delete -af please) when upgrading between major FreeBSD versions (e.g. 6.x - 7.x). Is there a particular reason that you recommend using pkg_delete? I just did 'portupgrade -aRf' for my 6.2 - 7.0 upgrades. -- Benjamin Lee http://www.b1c1l1.com/ signature.asc Description: OpenPGP digital signature
Re: preparing for an upgrade
On Tue, Nov 18, 2008 at 10:13:50PM -0800, Benjamin Lee wrote: On 11/18/08 21:43, Jeremy Chadwick wrote: [...] You can only use it on 7.x if you add compatibility libraries and ensure your kernel has COMPAT_FREEBSD6 in it. These libraries have given some users trouble in the past; you will find most people advocate rebuilding all ports from scratch (pkg_delete -af please) when upgrading between major FreeBSD versions (e.g. 6.x - 7.x). Is there a particular reason that you recommend using pkg_delete? I just did 'portupgrade -aRf' for my 6.2 - 7.0 upgrades. icarus# make all-depends-list /usr/ports/lang/ruby18 /usr/ports/databases/ruby-bdb /usr/ports/databases/db42 /usr/ports/devel/libtool15 So when upgrading your ports, you use... a port? That relies on a other ports of complex nature (a language and Oracle/Sleepycat DB)? Yeah, I'll pass. For example, if you use the base system pkg_* tools and portupgrade, they can get out of sync -- totally rad! I do not use portupgrade for a lot of reasons. All you have to do is examine the freebsd-* mailing lists (mainly -ports and -questions) for problems involving portupgrade. I believe the average is 1 a week? If the tool gets the job done for you, use it; I support that right above all else. But as for me, I'm incredibly anal when it comes to UNIX, and I strongly believe in the KISS concept. The only third-party tool I'd trust for managing ports would be portmaster, because it's a standalone tool with no dependencies, written in sh, and written by Doug Barton. That's all I have to say. I won't reply from this point on. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
