Re: what does open source mean ?
[EMAIL PROTECTED] wrote: hi, it's a pretty basic question I'm asking but I'd like to learn more about FreeBSD and Unix systems. For example I couldn't find how to recompile just one part of the base system (say ee for instance). Also when looking at the libraries I see lots of different suffixes which do not evoque anything to me (what are .so, .h, files and so on). What is the architecture of the system, how each and every part stick on the whole ? Could anyone tell me where to find information (readable for non specialist) about this kind of questions - implying more than howto knowledge? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message For the first I think it's recommented reading the FreeBSD handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ This is - even if you know it all - it's important to know the nomenclature which is used here. At next it may useful to read The Design and Implementation of the 4.4BSD Operating System: http://www.freebsd.org/doc/en_US.ISO8859-1/books/design-44bsd/ If this doesn't help at all, please ask again. Cheers, Jens -- L i W W W i Jens Rehsack LW W W L i W W W W i nnnLiWing IT-Services L iW W W Wi n n g g i W W i n n g gFriesenstraße 2 06112 Halle g g g Tel.: +49 - 3 45 - 5 17 05 91ggg e-Mail: [EMAIL PROTECTED] Fax: +49 - 3 45 - 5 17 05 92http://www.liwing.de/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: what does open source mean ?
[EMAIL PROTECTED] writes: it's a pretty basic question I'm asking but I'd like to learn more about FreeBSD and Unix systems. There are several definitions of open source. Assuming understanding of the word source, I like software for which the source code is available for reading at no cost beyond communication costs. It is almost always proprietary, requiring payments of licensing fees or other considerations for certain uses or being restricted from certain uses altogether. It almost always may be republished as-is without payment. Many people (often those who write it as Open Source) like to add the proviso that the source be licensed for execution (after translation), derivation, and publishing of derivatives, for no payment other than the cross-licensing of the deriver's copyrights under similar terms. Not all Unix systems are open source. IBM and HP (and some others ) are still supporting their Unix systems, but I think they're hoping to phase them out. Sun Microsystems is the main player, these days. For example I couldn't find how to recompile just one part of the base system (say ee for instance). I install the complete sources (using cvsup as documented in the FreeBSD Handbook), then find the directory with the source code ( eg, locate -i ee.c found it in /usr/src/usr.bin/ee/), enter that directory, change the code, and run make. IIRC, it may be then be installed with make install. Also when looking at the libraries I see lots of different suffixes which do not evoque anything to me (what are .so, .h, files and so on). I'm afraid you'll just have to pick them up as you go or ask about a few at a time. .so is Shared Object (code libary) (like DLL?); .h is include header files for C/C++ code; That is the architecture of the system, how each and every part stick on the whole ? Could anyone tell me where to find information (readable for non specialist) about this kind of questions - implying more than howto knowledge? Any WWW searcher will find lots of info at all levels; here's one intro http://www.ntlug.org/~cbbrowne/unix.html Be sure to spend a few hours exploring www.freebsd.org if you're going to try FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: what does open source mean ?
Many thanks for this insight, I know that many web sites provide informations , but toomuch information does not always help knowledge . I was hoping to get documentation on FreeBSD, as well made as the Handbook, but on the theorical side. For ee, since my first message I found by myself (!) the location of the source. I was thinking of recompiling it since I had problems when using ee from the console, and with sysinstall too. I've seen a question in this list about similar problems with pine. I suppose they both could be related to vi - so I'm impatient to read an answer to this question too. For the suffixes I found a Linux man entry that describes all the suffixes at http://www.rt.com/man/suffixes.7.html. I'll try your bookmarks right now ! Best regards Gary W. Swearingen wrote: There are several definitions of open source. Assuming understanding of the word source, I like software for which the source code is available for reading at no cost beyond communication costs. It is almost always proprietary, requiring payments of licensing fees or other considerations for certain uses or being restricted from certain uses altogether. It almost always may be republished as-is without payment. Many people (often those who write it as Open Source) like to add the proviso that the source be licensed for execution (after translation), derivation, and publishing of derivatives, for no payment other than the cross-licensing of the deriver's copyrights under similar terms. Not all Unix systems are open source. IBM and HP (and some others ) are still supporting their Unix systems, but I think they're hoping to phase them out. Sun Microsystems is the main player, these days. I install the complete sources (using cvsup as documented in the FreeBSD Handbook), then find the directory with the source code ( eg, locate -i ee.c found it in /usr/src/usr.bin/ee/), enter that directory, change the code, and run make. IIRC, it may be then be installed with make install. I'm afraid you'll just have to pick them up as you go or ask about a few at a time. .so is Shared Object (code libary) (like DLL?); .h is include header files for C/C++ code; Any WWW searcher will find lots of info at all levels; here's one intro http://www.ntlug.org/~cbbrowne/unix.html Be sure to spend a few hours exploring www.freebsd.org if you're going to try FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
