*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The BSDs aren't the same as Linux. Linux has a core dev team that develops the kernel, then a separately-developed GNU userland that bolts on top.
The BSDs are developed as a whole system (kernel + userland...so yes, each BSD project has it's own kernel (albeit from a common source some ~15-20 years ago)) and typically do not have GPL code in base (aside from the toolchain, typically), though they can (and do) run GPL code in ports or packages. I know OpenBSD is pretty strict on GPL code not being in the kernel, but I can't speak for Net/Free/Dragonfly/etc...
Edit - it's worth mentioning that there has been a common push in the BSD communities to get away from the GNU toolchain (well, to move *TO* a BSD-licensed toolchain, more accurately), but nothing solid has come of that yet.
Thanks for answering my post. I certainly see where you are coming from. Now I wish I asked a different question, "where does the traditional BSD codebase stop and a project like FreeBSD start.
let me explain myself....
Based on what you have shown me, if we load the Linux Kernel we have nothing. Once we start adding in binaries like cp, ls, pwd .. we are building up a userland. If we have a command line only Debian distro we have a userland. However once we add in gnome, KDE, XFCE etc, are we adding in something on top of the userland? or is there a proper name for the "outer layer" of the userland?
With BSD it sounds like the command line userland is already hardwired in, however once FreeBSD runs KDE, where are we now? Once we are at the KDE level we are running GPL code now right?
If I just stick to the command line userland in BSD, it sounds like I will be learning BSD licensed libraries, right?
The BSD and GPL licences are mutually compatible. One can have in theory a software project with fragments of code contributed by various individuals with different open source licences. In practice this is a bit of a mess. This should clarify the matter better: http://www.gnu.org/licenses/license-...atibleLicenses
Thanks. I have seen this FSF page and do understand the compatibility of the two. It's just that when someone talks about BSD licensed software, it kind of implies that BSD distros are purely licensed as BSD and maybe there are not ?
The BSD developers can only license the software they have written themselves. For all other software they have of course to use the licenses the developers of that software have chosen to use. So integrating KDE into a BSD does not automatically change its license to BSD, in the same way that integrating Firefox in your Linux distro does not automatically change its license to GPL.
Generally, all that is not part of the kernel, regardless if it is the ls command, a DE like Gnome or KDE, or a GUI application like LibreOffice, is part of the userland. There is no such thing as inner or outer userland, only userland (or userspace) and kernelspace.
You are reading a lot more into this than there is.
When you install FreeBSD (I assume the others are the same)
you get the kernel and the shells, and system daemons, and command line programs, like grep,
and the C standard library. So this would be described as the base system.
grep, I see for instance is GNU grep. grep (GNU grep) 2.5.1-FreeBSD
Stuff you add on top may or may not have a BSD license.
If KDE decide tomorrow to have a BSD license then nothing much changes.
No because The BSDs don't include the GNU applications.
Not long ago I have said the same. I am currently playing with NetBSD and it comes with GNU grep and GNU groff by default. There are more GNU applications, I would think, I am just to lazy to explicitly search for them. I am surprised by that myself.
Oh, well i withdraw my statement then. Thanks for sharing Toby. Configuring my mobile broadband under any of the BSDs is rather difficult and because of this i have not properly explored them. Thanks for clearing that up. This is what i get for repeating the dribble i've been fed.