From owner-freebsd-questions Tue Mar 25 7:50: 6 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17D5A37B401 for ; Tue, 25 Mar 2003 07:50:03 -0800 (PST) Received: from mired.org (ip68-97-54-220.ok.ok.cox.net [68.97.54.220]) by mx1.FreeBSD.org (Postfix) with SMTP id 227A443FA3 for ; Tue, 25 Mar 2003 07:50:02 -0800 (PST) (envelope-from mwm-dated-1049039401.861c27@mired.org) Received: (qmail 4446 invoked from network); 25 Mar 2003 15:50:01 -0000 Received: from localhost.mired.org (HELO guru.mired.org) (127.0.0.1) by localhost.mired.org with SMTP; 25 Mar 2003 15:50:01 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16000.31400.594337.21303@guru.mired.org> Date: Tue, 25 Mar 2003 09:50:00 -0600 To: "Tamir Halperin" Cc: Subject: RE: OpenSSL obstacle to PostgreSQL Installation In-Reply-To: <985DF46E87E0C047A3670048DBCAD0556BB2@andrew.brobus.net> References: <985DF46E87E0C047A3670048DBCAD0556BB2@andrew.brobus.net> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: Mike Meyer X-Delivery-Agent: TMDA/0.71 (Hoop, Jr.) X-Spam-Status: No, hits=-9.2 required=5.0 tests=FROM_ENDS_IN_NUMS,IN_REP_TO,REFERENCES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In <985DF46E87E0C047A3670048DBCAD0556BB2@andrew.brobus.net>, Tamir Halperin typed: > It appears that a symlink solved the problem. I did try someone else's symlink suggestion but it didn't point to the /usr/lib directory like Dmitry's did. > > A brief conversation with Dmitry Morozovsky [mailto:marck@rinet.ru] in the pgsql-admin list produced the following: > DM> So, possibly, quick hack like 'ln -s > DM> /usr/local/lib/libcrypto.so /usr/lib' may > DM> help you. Right. That's a good symlink to do. The question is, why did ports think you should have /usr/lib/libcrypto.so when you didn't have one? Either you didn't install the crypto distribution, or you didn't build it when you upgarded to a system that had it. > He brings up a good point. I'm running something that's over a year behind and I think it would benefit me to be at 4.8 or at least 4.7. > Can you point me to a concise document that discusses the upgrade procedure? I don't know of one. Upgrading a binary distribution is straightforward, though. Boot the 4.8 CDROM, and select "ugprade". That will give you a long warning about how dangerous all this is - which you should ignore, because you've backed up your system prior to doing this. Go through the upgrade procedure, then use the copy of your config files that it saved - I forget where - to modify the new versions that were installed so your config files are up to date. Alternatively for that last step, you can copy the your version back, and run "/usr/sbin/mergemaster" to merge in the config file changes from 4.8. But getting your config files up to date is the only part that's not simple. If you want to do a source upgrade, the handbook covers that in "the cutting edge". But the sequence is: # cvsup # to get new sources. # cd /usr/src # make buildworld # make kernel KERNCONF=whatever # use your kernel config file name here # shutdown -r # reboot new kernel in single user mode. Then, in single user mode # fsck -p # mount -a # cd /usr/src # make installworld # /usr/sbin/mergemaster And again, it should all just work, except for the mergemaster step. http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message