RE: OpenSSL obstacle to PostgreSQL Installation
In [EMAIL PROTECTED], Tamir Halperin [EMAIL PROTECTED] 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:[EMAIL PROTECTED] 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. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: OpenSSL obstacle to PostgreSQL Installation
I have a few questions and I'll jump right into this. -Original Message- From: Mike Meyer [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 10:50 AM To: Tamir Halperin Cc: [EMAIL PROTECTED] Subject: RE: OpenSSL obstacle to PostgreSQL Installation 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. 1a. As I proceed with the full upgrade how do I confirm that crypto is installed and running properly so that I can remove the symlink and get the system into a configuration that is more supportable and relying more on default settings? 1b. How do I get rid of the symlink? I looked at man ln and it wasn't very clear. I have so much to learn :( 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. You may not know of one but you sure did create one for me here. Thx. I'll download the 4.8 cdimage and burn a cd. 2. I do not know how to do a back up. I hope there's some program in the system that will allow me to simply back up only the system related config files since those are the only thinga that aren't application specific that I've modified from time to time. I can easily get burn those on to a cd as well or copy them as a backup volume to my other machine for later restoration. 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. 3a. An interestingly sounding alternative but I'm not sure what you mean by copy your version back. 3b. What does my version pertain to? Are you limiting that term to my version of the config files in the sense that I restore them back to their original locations and a program called mergmaster automagically updates them all with 4.8 settings where appropriate? 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 4a. Where will I find the file that needs to be referenced in place of the word whatever? If you know the directory the KERNCONF file is stored in, great. But some hints as to the name will go a long way as well if you don't. config file name here 4b. This one eludes me as well. # 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. I'll read up on mergemaster and formulate my next round of questions when I know more about it. mike Thanks again. -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: OpenSSL obstacle to PostgreSQL Installation
In [EMAIL PROTECTED], Tamir Halperin [EMAIL PROTECTED] typed: -Original Message- From: Mike Meyer [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 10:50 AM To: Tamir Halperin Cc: [EMAIL PROTECTED] Subject: RE: OpenSSL obstacle to PostgreSQL Installation 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. 1a. As I proceed with the full upgrade how do I confirm that crypto is installed and running properly so that I can remove the symlink and get the system into a configuration that is more supportable and relying more on default settings? Make sure you select any cryptography distributions that show up. 1b. How do I get rid of the symlink? I looked at man ln and it wasn't very clear. I have so much to learn :( Just rm /usr/lib/libcrypto.so. 2. I do not know how to do a back up. I hope there's some program in the system that will allow me to simply back up only the system related config files since those are the only thinga that aren't application specific that I've modified from time to time. The upgrade process will back up the system related config files for you. Like I said, I'm not sure where it backs them up to, as I haven't done a binary upgrade in a while. I can easily get burn those on to a cd as well or copy them as a backup volume to my other machine for later restoration. 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. 3a. An interestingly sounding alternative but I'm not sure what you mean by copy your version back. 3b. What does my version pertain to? The upgrade process copies all your old system config files to a safe place before it installs the new ones. That's your version of them. Are you limiting that term to my version of the config files in the sense that I restore them back to their original locations and a program called mergmaster automagically updates them all with 4.8 settings where appropriate? Sort of. Mergemaster isn't completely automatic. It will ask you if you want to udpate files, and gives you the option to examine both files and then merge them under your control. If you haven't modified very many of the files, it might be easier to do this the other way around. 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 4a. Where will I find the file that needs to be referenced in place of the word whatever? If you know the directory the KERNCONF file is stored in, great. But some hints as to the name will go a long way as well if you don't. config file name here 4b. This one eludes me as well. Those are the same thing. If you haven't configured a custom kernel, then you can just do make kernel and leave off the KERNCONF= stuff. If you have configured a custom kernel, you should know the name of the kernels config file, and that's the whatever to use. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: OpenSSL obstacle to PostgreSQL Installation
I did do a custom kernel only it wasn't me and the person that did this for me is no longer available to refer the question to. I remember clearly that he was interested in shrinking down the size of the kernel for the sake of saving memory but I don't remember the details of how he achieved this. What are some typical things to look for and where when trying to hunt down a config file for a custom kernel. -Original Message- From: Mike Meyer [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 12:39 PM To: Tamir Halperin Cc: [EMAIL PROTECTED] Subject: RE: OpenSSL obstacle to PostgreSQL Installation In [EMAIL PROTECTED], Tamir Halperin [EMAIL PROTECTED] typed: -Original Message- From: Mike Meyer [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 10:50 AM To: Tamir Halperin Cc: [EMAIL PROTECTED] Subject: RE: OpenSSL obstacle to PostgreSQL Installation 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. 1a. As I proceed with the full upgrade how do I confirm that crypto is installed and running properly so that I can remove the symlink and get the system into a configuration that is more supportable and relying more on default settings? Make sure you select any cryptography distributions that show up. 1b. How do I get rid of the symlink? I looked at man ln and it wasn't very clear. I have so much to learn :( Just rm /usr/lib/libcrypto.so. 2. I do not know how to do a back up. I hope there's some program in the system that will allow me to simply back up only the system related config files since those are the only thinga that aren't application specific that I've modified from time to time. The upgrade process will back up the system related config files for you. Like I said, I'm not sure where it backs them up to, as I haven't done a binary upgrade in a while. I can easily get burn those on to a cd as well or copy them as a backup volume to my other machine for later restoration. 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. 3a. An interestingly sounding alternative but I'm not sure what you mean by copy your version back. 3b. What does my version pertain to? The upgrade process copies all your old system config files to a safe place before it installs the new ones. That's your version of them. Are you limiting that term to my version of the config files in the sense that I restore them back to their original locations and a program called mergmaster automagically updates them all with 4.8 settings where appropriate? Sort of. Mergemaster isn't completely automatic. It will ask you if you want to udpate files, and gives you the option to examine both files and then merge them under your control. If you haven't modified very many of the files, it might be easier to do this the other way around. 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 4a. Where will I find the file that needs to be referenced in place of the word whatever? If you know the directory the KERNCONF file is stored in, great. But some hints as to the name will go a long way as well if you don't. config file name here 4b. This one eludes me as well. Those are the same thing. If you haven't configured a custom kernel, then you can just do make kernel and leave off the KERNCONF= stuff. If you have configured a custom kernel, you should know the name of the kernels config file, and that's the whatever to use. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: OpenSSL obstacle to PostgreSQL Installation
In [EMAIL PROTECTED], Tamir Halperin [EMAIL PROTECTED] typed: I did do a custom kernel only it wasn't me and the person that did this for me is no longer available to refer the question to. I remember clearly that he was interested in shrinking down the size of the kernel for the sake of saving memory but I don't remember the details of how he achieved this. What are some typical things to look for and where when trying to hunt down a config file for a custom kernel. /usr/src/sys/i386/conf. That should have GENERIC and LINT in it. Anything else there is a custom kernel, and can be used as the value of the KERNCONF= parameter to make kernel. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: OpenSSL obstacle to PostgreSQL Installation
In [EMAIL PROTECTED], Tamir Halperin [EMAIL PROTECTED] typed: I'm not able to install PostgreSQL 7.3.2 from ports because I get the following error after having just installed openssl-0.9.7a_2. openssl shows up in /var/db/pkg. When I try to make in /usr/ports/databases/postgresql7 I get the following error: This port requires the OpenSSL library, which is part of the FreeBSD crypto distribution but not installed on your machine. Please see the OpenSSL section in the handbook (at ...) for instructions on how to obtain and install the FreeBSD OpenSSL distribution. *** Error code 1 Stop. You get that message if you are building a port that needs SSL on a recent enough version of FreeBSD, and don't have a /usr/lib/libcrypto.so. The version number doesn't matter. Assuming you don't have libcrypto.so, did you try the handbook and following the directions there for installing the OpenSSL distribution? mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: OpenSSL obstacle to PostgreSQL Installation
oops! Good point about the list. I felt the same way (read below :) ). I don't have an /etc/make.conf but rather an /etc/defaults/make.conf. Even though I don't think you'll find it very interesting, it is attached for your entertainment. uname -a responds with: FreeBSD john.brobus.net 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Tue Jun 11 06:14:12 GMT 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC i386 -Original Message- From: Mike Meyer [mailto:[EMAIL PROTECTED] Sent: Monday, March 24, 2003 12:15 PM To: Tamir Halperin Cc: [EMAIL PROTECTED] Subject: Re: OpenSSL obstacle to PostgreSQL Installation In [EMAIL PROTECTED], Tamir Halperin [EMAIL PROTECTED] typed: I'm not able to install PostgreSQL 7.3.2 from ports because I get the following error after having just installed openssl-0.9.7a_2. openssl shows up in /var/db/pkg. When I try to make in /usr/ports/databases/postgresql7 I get the following error: This port requires the OpenSSL library, which is part of the FreeBSD crypto distribution but not installed on your machine. Please see the OpenSSL section in the handbook (at ...) for instructions on how to obtain and install the FreeBSD OpenSSL distribution. *** Error code 1 Stop. You get that message if you are building a port that needs SSL on a recent enough version of FreeBSD, and don't have a /usr/lib/libcrypto.so. The version number doesn't matter. Assuming you don't have libcrypto.so, did you try the handbook and following the directions there for installing the OpenSSL distribution? mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: OpenSSL obstacle to PostgreSQL Installation
[Context lost to top posting.] In [EMAIL PROTECTED], Tamir Halperin [EMAIL PROTECTED] typed: oops! I don't have an /etc/make.conf but rather an /etc/defaults/make.conf. Even though I don't think you'll find it very interesting, it is attached for your entertainment. It looks like you haven't modified anything in it. Which is good - you should never modify things in /etc/defaults. uname -a responds with: FreeBSD john.brobus.net 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Tue Jun 11 06:14:12 GMT 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC i386 What do you have for /usr/lib/libcrypto*? mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: OpenSSL obstacle to PostgreSQL Installation
Hi Mike, 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:[EMAIL PROTECTED] 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. TH I can't believe it. After two days of scraping around for why it isn't working and one command later it works! TH It's amazing what knowledge will do for a person's outlook on life. TH The above ln command worked and postgresql 7.3.2 is currently installing. DM Anyway, please consider upgrading to 4.8 which should be out DM of door this week. 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? Tamir Halperin. p.s. and thanks again for all the attention. It does a heart good to be cared for by all you guys. -Original Message- From: Mike Meyer [mailto:[EMAIL PROTECTED] Sent: Monday, March 24, 2003 4:45 PM To: Tamir Halperin Cc: [EMAIL PROTECTED] Subject: RE: OpenSSL obstacle to PostgreSQL Installation [Context lost to top posting.] In [EMAIL PROTECTED], Tamir Halperin [EMAIL PROTECTED] typed: oops! I don't have an /etc/make.conf but rather an /etc/defaults/make.conf. Even though I don't think you'll find it very interesting, it is attached for your entertainment. It looks like you haven't modified anything in it. Which is good - you should never modify things in /etc/defaults. uname -a responds with: FreeBSD john.brobus.net 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Tue Jun 11 06:14:12 GMT 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC i386 What do you have for /usr/lib/libcrypto*? mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: OpenSSL obstacle to PostgreSQL Installation
In [EMAIL PROTECTED], Tamir Halperin [EMAIL PROTECTED] typed: Thanks for responding to my request, Mike. I'll privately provide you an update offlist and please feel free to repond to me via the list for the benefit of others. This is a really bad idea - others on the list may have answers I don't. Also, someone later may have this problem, and be looking for the answer in the archives. I've taken this back to the list. TH I'm sure there's a solution to using postgresql 7.3.2 with openssl. I just don't have it. There is. Mine is built using libcrypt with no problems. Though it uses the old version of libcrypt for some reason. so you're basically caught up to date. The other approach I tried to take is to simply upgrade the entire system. I've never done this before and wading through all the documentation I'm told to go to is driving me insane. I simply don't even understand the terminology or concepts involved in the instructions for upgrading. I tried following whichever instructions I sort of understand in /usr/src/UPDATING but I'm not having much luck. I'm at the step where I'm supposed to execute 'make buildkernel KERNCONF=YOUR_KERNEL_HERE' but I have no idea what to put instead of 'YOUR_KERNEL_HERE'. If you've updated the ports tree without updating the system, updating the system may be what you need to do. However, you shouldn't be running into that error unless you are running a version of postgresql late enough to use the old libcrypt. Let's not go down the road of updating everything until we've exhausted some other options. What version of freebsd are you running this on. Also, is there anything strange in your /etc/make.conf? It should be short enough to post the entire thing here. You officially have my plea! And you have mine - please hit carriage return every now and then! You're in danger of creating lines longer than the SMTP spec allows! mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
