Date: Mon, 18 Nov 2002 00:51:54 +0100 From: rens.emmanuel@wanadoo.fr To: "Gary W. Swearingen" <swear@attbi.com> Cc: FreeBSD-questions@FreeBSD.org Subject: Re: what does "open source" mean ? Message-ID: <3DD82B9A.7020902@wanadoo.fr> References: <20021116010252.97C8937B404@hub.freebsd.org> <3DD6ADA6.9040106@wanadoo.fr> <s7zns7den5.ns7@localhost.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
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 majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DD82B9A.7020902>