I have just spent several hours trying to get plone.org back up. It appears that Plone and FreeBSD are not made for each other. I end up getting core dumps. I applied the 'thread stack' patch. I also tried to use Python2.2.1 w/ chrism_installer branch and I get the same results. I am most likely going to move away from FreeBSD to Linux - which is a shame, one less FreeBSD/Zope/Plone combination running in the wild. I know the iMeme guys have Plone running but I have seen really freakish behavior there as well. So I am giving up. If someone wants to hand hold me - I will try again but in a few minutes I'm moving the Data.fs file to a linux box and trying to get plone.org back up. Notes from my experience: - chrism_installer_branch is *very very* nice - thanks ChrisM. - seemingly large file support is never turned on by default in python tarballs. I think this is a shame. I dont know the reasons but reading the posix large file page is very scary. Zope Corp should always enable large file support on all of their python interpreters. - Its really depressing that Python/FreeBSD/Plone have this problem. iirc yahoo.com runs lots of FreeBSD boxens running python for some of their services. but the fact that I have spent some 3 hours trying to get all of this to work and Plone still causes python to core dump is a huge shame. CMF sites work fine. Plone site crash. I have never seen Plone crash on either win32 or linux. This is FreeBSD problem. please help make Zope/Python/*BSD work together gurus - your our only hope. I remember asking the python maintainer to up the thread stack size in python2.1.2 and his response was something like - if your requiring more than whats allocated you have serious problems. ~runyaga