(I’ve already noticed that this question was asked before but I think it has not been answered in a way I’d like to understand the topic.)
What are the conceptual and structural differences between a
- Linux Kernel
- BSD Kernel (let’s say FreeBSD)
While at the end of the day they are both kernels – I would assume that there might be differences in structure, functionality and specialization. In which scenarios would one kind of kernel have an advantage over the other? (Web Server, Database, Computing, etc.)
Are there any joint efforts to concentrate forces for one common kernel or certain modules or would that be pointless anyway?
PS: Different license types or shipping/packaging/maintaining approaches are not of importance in this context. I’m really interested in understanding how they differ on structural, functional/feature level and specialization.
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
1. What are the conceptual and structural differences between a Linux-Kernel and a BSD-kernel?
Regarding architecture and internal structures, there are of course differences on how things are done (ie: lvm vs geom, early and complex jail feature for FreeBSD, …), but overall there are not that much differences between the two:
- BSD* kernel and Linux kernel have both evolved from a purely monolithic approach to something hybrid/modular.
Still, there are fundamental differences in their approach and history:
- BSD-kernel are using BSD licence and Linux-kernel is using GPL licences.
- BSD-kernel are not stand-alone kernels but are developed as being part of a whole. Of course, this is merely a philosophical point of view and not a technical one, but this give system coherence.
- BSD-kernel are developed with a more conservative point-of_view and more concern about staying consistent with their approach than having fancy features.
- Linux-kernel are more about drivers, features, … (the more the better).
As greatly stated somewhere else:
It is Intelligent Design and Order (BSD*) versus Natural Selection and Chaos (GNU/Linux).
2. In which scenarios would one kind of kernel have an advantage over the other?
About their overall structure and concept, while comparing an almost vanilla Linux-kernel and a FreeBSD-kernel, they are more or less of the same general usage level, that is with no particular specialization (not real-time, not highly paralleled, not game oriented, not embedded, …).
Of course there are a few differences here and there, such as native ZFS support or the geom architecture for FreeBSD versus the many drivers or various file-systems for Linux. But nothing some general software such as web servers or databases would really use to make a real difference. Comparisons in these cases would most likely end in some tuning battle between the two, nothing major.
But, some would argue that OpenBSD has a deep and consistent approach to security, while hardened Linux distributions are “just” modified versions of the vanilla Linux-kernel. This might be true for such heavily specialized system, as would Steam-OS be the number one to play games.
3. Are there any joint efforts to concentrate forces for one common kernel or certain modules?
There is no joint effort to concentrate forces for one common kernel, as there are major licences, philosophical or approach issues.
If some real common efforts exist such as OpenZFS, most of the time it is more about drivers and concepts taken or inspired from one another.
Method 2
Partial answer addressing a few of the points
The many options is often perceived as a bad thing when on the outside looking into open source development but think of it as in nature, there are many species (often) of a type of animal, say penguins. There are 17. Each is specialized to a particular set of requirements, so too with open source projects (typically). Natural selection will take care of weeding out the open source that’s less apt over time.
Are there any joint efforts to concentrate forces for one common kernel or certain modules or would that be pointless anyway?
Would be kind of pointless, it’s a duplication of effort at times but people that work on these components are not doing it in a vacuum either. They’ll look around at what other are doing and if there is an approach or algorithm they’re incorporate it when it makes sense to do so.
I cannot talk to the structure differences regarding your other bullets but thought I’d at least address 2 of them.
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0