The software has to be portable. If you compile your C/C++ sources, then you don't need to know if you running i386/x86_64/arm/mips or what ever. The headers are linked in such way the software compiles.
All other header files exist because they were implemented a lot of different standards, there are ports from BSD and so on. So many of them are historically based. Where each one comes from and why they are there has many different reasons and will surely blow answers.
And an answer for asm-generic: stackoverflow
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.
Best Answer
UTS_RELEASEincludesEXTRAVERSION. If you changeEXTRAVERSION,UTS_RELEASEwill be updated to reflect that. If you changeUTS_RELEASEininclude/generated/utsrelease.h, the file is liable to be rewritten the next time you build the kernel, which would lose your change. So don't touchUTS_RELEASE, editEXTRAVERSIONif you have to.The kernel supports a local version too, which is defined in the kernel configuration and is designed to be changed in local builds. It is appended to the kernel release. You should probably use that!