To: fretzer
I thought the idea, at least with UNIX, was to have a relatively small, tight kernel that limited itself to critical functions and that everything else was managed by libraries which could be standardized or optimized for specific platforms.
It seems like more and more code that was in libraries is now in the kernel.
To: who_would_fardels_bear
The kernel manages the hardware at a low-level. There are thousands of possible HW optional bits out there, and the kernel your distribution installs has to have at least pluggable-module support for all of them.
However, you can build your own kernel that includes only support for HW that is actually on your computer, and it will be quite a bit smaller.
23 posted on
06/09/2024 9:45:22 AM PDT by
Campion
(Everything is a grace, everything is the direct effect of our Father's love - Little Flower)
To: who_would_fardels_bear
Linux (meaning “the kernel”) ships with the software drivers for hardware, so it is quite big. But that philosophy is a solid way around the chaos of Microsoft’s chaotic approach (Where do you want to try to find a driver? Hunh? Where is it? HUNH??) And it also explains why GNU/Linux plays so well with older hardware, because the older drivers remain included.
41 posted on
06/09/2024 11:44:07 AM PDT by
Montana_Sam
(Truth lives.)
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson