I thought I'd ask here... I'm currently running FreeBSD 4.10, and would like to upgrade to a 5.x because of the superior jail support. Which version would you recommend for someone who's really interested in jail support, but doesn't like to live dangerously? Of my hardware, the only item of note is that I use FreeBSD 4.10's ehci driver for USB 2.0 devices. One of the notes in /usr/src/UPDATING was that GCC had been upgraded from my current 2.95 to 3.4 and there are known compatibility problems with the ABI (what's an ABI? the .so's?) Will this upgrade force me to recompile all of my existing C++ stuff, e.g. Postgres and PostGIS, or will my existing binaries continue to run? __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail
On Monday 20 September 2004 15:12, Gregor Mosheh wrote:> I thought I'd ask here... > > I'm currently running FreeBSD 4.10, and would like to > upgrade to a 5.x because of the superior jail support. > > Which version would you recommend for someone who's > really interested in jail support, but doesn't like to > live dangerously? Of my hardware, the only item of > note is that I use FreeBSD 4.10's ehci driver for USB > 2.0 devices. > > One of the notes in /usr/src/UPDATING was that GCC had > been upgraded from my current 2.95 to 3.4 and there > are known compatibility problems with the ABI (what's > an ABI? the .so's?) Will this upgrade force me to > recompile all of my existing C++ stuff, e.g. Postgres > and PostGIS, or will my existing binaries continue to > run?You should wait for 5.3-RELEASE. You will have to recompile every application you use. A doc on upgrading from 4.x to 5.x should be along when 5.3 is released. Regards, Brad -- Beware of Programmers who carry screwdrivers. -- Leonard Brandwein
Gregor Mosheh wrote:>I thought I'd ask here... > >I'm currently running FreeBSD 4.10, and would like to >upgrade to a 5.x because of the superior jail support. > >Which version would you recommend for someone who's >really interested in jail support, but doesn't like to >live dangerously? Of my hardware, the only item of >note is that I use FreeBSD 4.10's ehci driver for USB >2.0 devices. > >One of the notes in /usr/src/UPDATING was that GCC had >been upgraded from my current 2.95 to 3.4 and there >are known compatibility problems with the ABI (what's >an ABI? the .so's?) Will this upgrade force me to >recompile all of my existing C++ stuff, e.g. Postgres >and PostGIS, or will my existing binaries continue to >run? > > >I would wait until well after 5.3-RELEASE. There are several bugs in 5.3 that still exist and I don't expect to see them all worked out before the release. There is a USB bug that causes a sig 12 during printing to a USB printer under certain circumstances. EHCI used to force reboots on my machine, but it has been awhile since I checked it out. There are simply a lot of reports of lockups and reboots that would keep me wary for a long time to come [if I had an aversity to risk as you indicate]. Tom Veldhouse -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040921/12a9c71f/signature.bin
Hello Bruce, Thursday, September 23, 2004, 8:54:19 AM, you wrote:>> What about directories that I definitively shouldn't restore, for >> example: >> /usr/include /usr/lib most likely /bin /sbin /usr/bin /usr/sbin /stand >> and so on, maybe that could help me better.> Here's the deal. For any of the systems I maintain, I wouldn't > restore any of these from backups after a source upgrade because in > general, those directories contain *only* files installed from the > base system. But how can I tell how *you* have *your* system set up?Well, I'm avoiding to change anything in system files, and all additional stuff I'm actually putting in /usr/local. I'm interested about directories that are changed by system/system programs - I belive most confusing is /var in theory there shouldn't be anything important there (well except logs), but I already noticed there is mail, crontab jobs, informations what ports were installed even mysql port install database there.>> That step was in source upgrade category, so I assumed it might not >> be correct for binary upgrade.> You *asked* about the source upgrade procedure above.I'm sorry, I see now. I wrote one thing but I was thinking about another. I meant binary upgrade, sorry for the confusion.> For binary upgrades, it's probably best to carefully examine the files > in your backups and merge the changes in by hand. After a binary > install, the old files will be gone, so there won't be anything for > mergemaster to operate on.Yes that's true, but using mergemaster is less work. And I still have old files in backup.> Good candidates for merging are: /etc/passwd, /etc/group, and > /etc/rc.conf. Don't just blindly drop in your backup files.So I see next step - selecting which files from /etc are needed to be restored.>> What about ports, I know that I need to recompile them, but will they >> work for that time? > We believe that most ports will work if you install the compat4x > libraries and don't upgrade anything. But there's a few that *need* > to be upgraded, due to changes in the statfs structure. Also if > you're going to upgrade ports in the future, it's probably safest to > reinstall all ports.I see>> It's not really mission-critical, but it's like that for me :) >> It works as my mail/web server so I want to have shortest downtime >> possible :)> Then you want to take your time and do things carefully so that you > don't have a longer downtime caused by screwing up the upgrade. I've > had this happen more times than I can count (not on FreeBSD, but the > experience applies).Thank you very much for your tips on upgrading. -- Best regards, Dariusz mailto:takeda@takeda.tk CCNA, SCSA, SCNA, LPIC, MCP certified http://www.takeda.tk