[leaf-devel] RE: Bering - included libraries
Hello all, I wrote my last message in a fit of excitement. After rereading it, an activity that didn't take long, I decided to respond to myself and add a bit more detail. I am in the process of building a zebra package based on the newer 0.93b code. I started with reading David's Developer Guide and the Developer FAQ's. I have also installed both, zebra.lrp based on zebra-0.91 built by Andrew Hoying and David Douthitt's zebra.lrp based on zebra-0.92. Just to get an idea of how those before me had done it. The main problem that I have run into is that both of these packages require the libraries; libm, libcrypt, and libresolv. On oxygen this is not a problem since libcrypt and libresolv are included in the base distro. You just add libm.lrp and you are good to go. I, however, am not working with oxygen. I am using Bering_1.0-rc3 which does not have libcrypt and I am not sure about libresolv, I haven't been able to get past libcrypt. Also, I have not been able to find any .lrp files for libcrypt or libresolv. If anyone can help out with letting me know which libraries are already included in rc3 it would be very helpful. If anyone can tell me how to find this information myself that would be even better. I have spent hours google searching on this topic and run out of ideas on what to search for. It would also be nice to know what is expected along these lines from rc4. Once again, thanks in advance, Eric -Original Message- From: Eric B Kiser [mailto:[EMAIL PROTECTED]] Sent: Friday, September 20, 2002 1:16 PM To: [EMAIL PROTECTED] Subject: Bering - included libraries Howdy all, Can someone tell me how I can find out what libraries are included with Bering? Thanks in advance, Eric --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] RE: Bering - included libraries
Hello Eric , The libraries that are included in a standard Bering rc3 are : # ls -1 ld-2.0.7.so ld-linux.so.2 libc-2.0.7.so libc.so.6 libcrypt-2.0.7.so libcrypt.so.1 libdl-2.0.7.so libdl.so.2 libnss_dns-2.0.7.so libnss_dns.so.1 libnss_files-2.0.7.so libnss_files.so.1 libresolv-2.0.7.so libresolv.so.2 libss.so.2 libss.so.2.0 libutil-2.0.7.so libutil.so.1 so libcrypt and libresolv are there. I just hope that there are no version problems. libm is not but there is a lrp (needed for ipsec for example) The solution to find out which are included (#ls ;) ) I wrote my last message in a fit of excitement. After rereading it, an activity that didn't take long, I decided to respond to myself and add a bit more detail. I am in the process of building a zebra package based on the newer 0.93b code. I started with reading David's Developer Guide and the Developer FAQ's. I have also installed both, zebra.lrp based on zebra-0.91 built by Andrew Hoying and David Douthitt's zebra.lrp based on zebra-0.92. Just to get an idea of how those before me had done it. The main problem that I have run into is that both of these packages require the libraries; libm, libcrypt, and libresolv. On oxygen this is not a problem since libcrypt and libresolv are included in the base distro. You just add libm.lrp and you are good to go. I, however, am not working with oxygen. I am using Bering_1.0-rc3 which does not have libcrypt and I am not sure about libresolv, I haven't been able to get past libcrypt. Also, I have not been able to find any .lrp files for libcrypt or libresolv. If anyone can help out with letting me know which libraries are already included in rc3 it would be very helpful. If anyone can tell me how to find this information myself that would be even better. I have spent hours google searching on this topic and run out of ideas on what to search for. It would also be nice to know what is expected along these lines from rc4. As it looks now there will be no great change in library content . Once again, thanks in advance, Eric Regards Eric Wolzak member of the Bering Crew --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
RE: [leaf-devel] RE: Bering - included libraries
Hi Eric, You must mean inside that really obvious directory named /lib. Urgh, it is now probably a moot point to mention that I am a newbie. Your patience is appreciated. Here is where I am now. I execute the command #zebra -d to start the zebra process running as a daemon and I get the following message back. zebra: error in loading shared libraries libcrypto.so.2: cannot open shared object file: No such file or directory Here is specifically what I am running. Bering_1.0-rc3 UML kernel 2.4.18-21 zebra 0.92 packaged by David Douthitt also zebra 0.91a packaged by Andrew Hoying Is libcrypto.so.2 part of libcrypt-2.0.7.so or libcrypt.so.1 or is it something completely different? Thanks for any help that you can offer. Eric [Kiser] -Original Message- From: Eric Wolzak [mailto:[EMAIL PROTECTED]] Sent: Saturday, September 21, 2002 4:08 PM To: Eric B Kiser; [EMAIL PROTECTED] Subject: Re: [leaf-devel] RE: Bering - included libraries Hello Eric , The libraries that are included in a standard Bering rc3 are : # ls -1 ld-2.0.7.so ld-linux.so.2 libc-2.0.7.so libc.so.6 libcrypt-2.0.7.so libcrypt.so.1 libdl-2.0.7.so libdl.so.2 libnss_dns-2.0.7.so libnss_dns.so.1 libnss_files-2.0.7.so libnss_files.so.1 libresolv-2.0.7.so libresolv.so.2 libss.so.2 libss.so.2.0 libutil-2.0.7.so libutil.so.1 so libcrypt and libresolv are there. I just hope that there are no version problems. libm is not but there is a lrp (needed for ipsec for example) The solution to find out which are included (#ls ;) ) I wrote my last message in a fit of excitement. After rereading it, an activity that didn't take long, I decided to respond to myself and add a bit more detail. I am in the process of building a zebra package based on the newer 0.93b code. I started with reading David's Developer Guide and the Developer FAQ's. I have also installed both, zebra.lrp based on zebra-0.91 built by Andrew Hoying and David Douthitt's zebra.lrp based on zebra-0.92. Just to get an idea of how those before me had done it. The main problem that I have run into is that both of these packages require the libraries; libm, libcrypt, and libresolv. On oxygen this is not a problem since libcrypt and libresolv are included in the base distro. You just add libm.lrp and you are good to go. I, however, am not working with oxygen. I am using Bering_1.0-rc3 which does not have libcrypt and I am not sure about libresolv, I haven't been able to get past libcrypt. Also, I have not been able to find any .lrp files for libcrypt or libresolv. If anyone can help out with letting me know which libraries are already included in rc3 it would be very helpful. If anyone can tell me how to find this information myself that would be even better. I have spent hours google searching on this topic and run out of ideas on what to search for. It would also be nice to know what is expected along these lines from rc4. As it looks now there will be no great change in library content . Once again, thanks in advance, Eric Regards Eric Wolzak member of the Bering Crew --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] RE: Bering - included libraries
Eric B Kiser wrote: You must mean inside that really obvious directory named /lib. Urgh, it is now probably a moot point to mention that I am a newbie. Your patience is appreciated. Here is where I am now. I execute the command #zebra -d to start the zebra process running as a daemon and I get the following message back. zebra: error in loading shared libraries libcrypto.so.2: cannot open shared object file: No such file or directory snip / There is a very real difference between these two (2) libraries: libcrypt libcrypto The latter is part and parcel of openssl; perhaps, also some other libraries. How are you compiling zebra? On what describe system? With what libraries? You probably need to do what we have done for openssh, which is to statically link libcrypto during openssh compile . . . -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] RE: Bering - included libraries
On 2002.09.21_21:17:51_+, Eric B Kiser wrote: Hi Eric, Hi Eric, You must mean inside that really obvious directory named /lib. Urgh, it is now probably a moot point to mention that I am a newbie. Your patience is appreciated. Yes, the /lib directory contains libraries. Some libs are in /usr/lib. Here is where I am now. I execute the command #zebra -d to start the zebra process running as a daemon and I get the following message back. zebra: error in loading shared libraries libcrypto.so.2: cannot open shared object file: No such file or directory libcrypto and libcrypt are totally different things. libcrypt is from glibc, while libcrypto is installed from OpenSSL. libssl.lrp which includes libcrypto is available here: http://leaf-project.org/devel/ddouthitt/packages/libssl.lrp When installed, the files will be in /usr/lib. Here is specifically what I am running. Bering_1.0-rc3 UML kernel 2.4.18-21 zebra 0.92 packaged by David Douthitt also zebra 0.91a packaged by Andrew Hoying Is libcrypto.so.2 part of libcrypt-2.0.7.so or libcrypt.so.1 or is it something completely different? See my answer above. Thanks for any help that you can offer. You're welcome. Eric [Kiser] -- H. D. Lee --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
RE: [leaf-devel] RE: Bering - included libraries
Hi Michael, I am using David's zebra.lrp package and trying to get it to run on Bering_1.0-rc3. I wanted to check out what he did before I got started on mine. I will, however, be using UML_slink to do my compiling. You bring up an interesting question regarding ssh having the libraries statically linked. I expect to have both ssh and zebra running on the same system. Would it be better to use the libssl as suggested by H. D. Lee. That is, assuming that there is an ssh.lrp without libcrypto statically linked. Strictly for the purpose of conserving space. Along this same line of thought, does anyone know whether it would cause problems to use ssh.lrp with the statically linked libcrypto on the same system as using libssl.lrp. I am in unfamiliar terrain here so any help is appreciated. Many thanks to both of you, Eric [Kiser] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michael D. Schleif Sent: Saturday, September 21, 2002 9:49 PM Cc: [EMAIL PROTECTED] Subject: Re: [leaf-devel] RE: Bering - included libraries Eric B Kiser wrote: You must mean inside that really obvious directory named /lib. Urgh, it is now probably a moot point to mention that I am a newbie. Your patience is appreciated. Here is where I am now. I execute the command #zebra -d to start the zebra process running as a daemon and I get the following message back. zebra: error in loading shared libraries libcrypto.so.2: cannot open shared object file: No such file or directory snip / There is a very real difference between these two (2) libraries: libcrypt libcrypto The latter is part and parcel of openssl; perhaps, also some other libraries. How are you compiling zebra? On what describe system? With what libraries? You probably need to do what we have done for openssh, which is to statically link libcrypto during openssh compile . . . -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] RE: Bering - included libraries
Eric B Kiser wrote: I am using David's zebra.lrp package and trying to get it to run on Bering_1.0-rc3. I wanted to check out what he did before I got started on mine. I will, however, be using UML_slink to do my compiling. You bring up an interesting question regarding ssh having the libraries statically linked. I expect to have both ssh and zebra running on the same system. Would it be better to use the libssl as suggested by H. D. Lee. That is, assuming that there is an ssh.lrp without libcrypto statically linked. Strictly for the purpose of conserving space. I do not know which version is David's libssl.lrp -- it is big. I am sure that it is several versions behind the most current openssl-0.9.6g, which I use in my openssh packages. As you know, the recent linux worm hoopla is aided and abetted by older versions of openssl. How much of this affects zebra, I do not know. Due to the enormous size of openssl, and also to the limited need for it across a wide gamut of leaf packages, static linking openssl libraries into other packages appears to be the norm. Everytime that I have poo-poo'd size constraints -- I use dcd -- I am reminded that a large portion of our audience is constrained by floppy sizes. Everything developed for this project is based on well thought out trade offs. Zebra will be no different. Along this same line of thought, does anyone know whether it would cause problems to use ssh.lrp with the statically linked libcrypto on the same system as using libssl.lrp. I am in unfamiliar terrain here so any help is appreciated. No problem. I have been meaning to do the zebra thingy for over a year. Obviously, the need has not been great enough to coax me into it. I wish you good fortune in this endeavor and am anxious to play with the results. If I can help, please, let me know . . . snip / -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
RE: [leaf-devel] RE: Bering - included libraries
[snip] I wish you good fortune in this endeavor and am anxious to play with the results. If I can help, please, let me know . . . [/snip] You have already been of tremendous assistance. Many thank yous. Eric -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michael D. Schleif Sent: Sunday, September 22, 2002 12:09 AM Cc: [EMAIL PROTECTED] Subject: Re: [leaf-devel] RE: Bering - included libraries Eric B Kiser wrote: I am using David's zebra.lrp package and trying to get it to run on Bering_1.0-rc3. I wanted to check out what he did before I got started on mine. I will, however, be using UML_slink to do my compiling. You bring up an interesting question regarding ssh having the libraries statically linked. I expect to have both ssh and zebra running on the same system. Would it be better to use the libssl as suggested by H. D. Lee. That is, assuming that there is an ssh.lrp without libcrypto statically linked. Strictly for the purpose of conserving space. I do not know which version is David's libssl.lrp -- it is big. I am sure that it is several versions behind the most current openssl-0.9.6g, which I use in my openssh packages. As you know, the recent linux worm hoopla is aided and abetted by older versions of openssl. How much of this affects zebra, I do not know. Due to the enormous size of openssl, and also to the limited need for it across a wide gamut of leaf packages, static linking openssl libraries into other packages appears to be the norm. Everytime that I have poo-poo'd size constraints -- I use dcd -- I am reminded that a large portion of our audience is constrained by floppy sizes. Everything developed for this project is based on well thought out trade offs. Zebra will be no different. Along this same line of thought, does anyone know whether it would cause problems to use ssh.lrp with the statically linked libcrypto on the same system as using libssl.lrp. I am in unfamiliar terrain here so any help is appreciated. No problem. I have been meaning to do the zebra thingy for over a year. Obviously, the need has not been great enough to coax me into it. I wish you good fortune in this endeavor and am anxious to play with the results. If I can help, please, let me know . . . snip / -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] RE: Bering - included libraries
On Sunday 22 September 2002 00:47, Eric B Kiser wrote: It seems that I am beginning to catch on. Zebra is looking for a newer version of libcrypto than what is being provided by libssl.lrp. So, that leaves me with two options; [1] build an updated libssl.lrp [2] compile my zebra package with libcrypto statically linked Michael suggested number [2], would anyone else care to voice an opinion on this? Does anyone else even see the need to have an updated libssl package? Just trying to gain a consensus and possibly some guidance before moving forward. Personally, I would like to eventually see ssh and zebra not using statically linked libraries. That is, of course, unless I can show that using the static libraries on zebra and ssl work out to take up less space than zebra+ssh+ssl packages. I would agree that option [2] would likely be the better of the two choices. You are about as far along with a Zebra/LEAF disk as I was when thinking about something similar several months ago. I know that Zebra isn't going to fit on a floppy, but SSL is a huge package that could present problems as well as benefits in the long run. Statically linking the library simply limits the drawbacks to including the entire library. It will work either way, but I would suggest drawing off of WISP-DIST architecture, since you are going to end up with a non-floppy image. This architecture adds several safety features not available with other current LEAF variants. The bright side is that your probably not going to have to worry about firewalling anything, just securing the router! ;-) -- ~Lynn Avants aka Guitarlynn guitarlynn at users.sourceforge.net http://leaf.sourceforge.net If linux isn't the answer, you've probably got the wrong question! --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] RE: Bering - included libraries
On 2002.09.22_01:09:25_+, guitarlynn wrote: [1] build an updated libssl.lrp [2] compile my zebra package with libcrypto statically linked I would agree that option [2] would likely be the better of the two choices. You are about as far along with a Zebra/LEAF disk as I was when thinking about something similar several months ago. I know that Zebra isn't going to fit on a floppy, but SSL is a huge package that could present problems as well as benefits in the long run. Statically linking the library simply limits the drawbacks to including the entire library. I second that. libssl.lrp itself is 398007 bytes, and about 1 megabyte uncompressed. Unless there are a lot of apps you intend to install use the library, I can only see a few points on installing the whole huge package. A few points I meant here, and may be what Lynn referred to as benefits, are availability of the library in the future and sharability. -- H. D. Lee --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
