All those who were encouraged to use Gentoo, they know that this Linux distro that it is highly customizable thanks to that does not use precompiled binaries, With which user has to do system compilation on his own with which it gives it a great advantage over other distributions since it is possible to create a compilation focused on the components of the computer giving it greater fluidity and performance.
Since with Portage, which implements some advanced features such as dependency management, fine tuning of packages to the administrator's liking, OpenBSD-style fake installations, compilation sandboxes, safe uninstallation, system profiles, virtual packages, configuration file management, and multiple slots for different versions of the same package.
But now this can change as Gentoo developers are discussing the possibility of make provision of generic Linux kernel packages that do not require manual configuration during compilation and are similar to the kernel packages provided in traditional binary distributions.
As a example of the problem that arises when it is used manual tuning of kernel parameters practiced in Gentoo, there is a lack of a unified set of default options that ensure operability after the update (When configured manually, if the kernel does not boot or a crash occurs, it is not clear whether the problem is caused by incorrect parameter settings or an error in the kernel itself).
The traditional Gentoo way of getting a kernel is to install the sources, and then configure and build one yourself. For those who didn't want to go through the tedious process of setting it up manually, an alternate route to using genkernel was provided. However, none of those variants was able to actually provide the equivalent of the cores provided by binary distributions.
The developers intend to provide a ready kernel and obviously functional that can be installed with minimal effort (like ebuild, built by analogy with other packages) and the package manager will update it automatically as part of regular system updates.
Currently, the sys-kernel / vanilla-kernel package has already been proposed on the basis from the main kernel sources, supplementing the previously available build script with a typical set of genkernel options.
If I have to justify the change from the old tradition of custom kernels to a universal kernel package, I should start by discussing the reasons why you might want to configure a custom kernel in the first place.
The vanilla-kernel package so far it only involves assembling from source code (proposed in ebuild form), but the possibility of generating binary kernel assemblies is also discussed.
The main counterargument is effort. As mentioned above, I personally got tired of having to manually deal with my kernel. Do the potential gains mentioned outweigh the loss of human time configuring and maintaining a custom kernel?
Among the advantages of manual kernel tuning, the ability to tune performance, remove unnecessary components during compilation, shorten compilation time and reduce kernel size resulting (for example, building a proponent's kernel takes 44MB together with modules, while a universal kernel takes 294MB).
Among the shortcomings, it is observed that a mistake can easily be made during setup, possible problems with the update, intolerance, difficulty diagnosing problems.
The supply of compilations binaries is considered because the universal kernelDue to its size, it compiles for much longer and delivers a finished kernel It can simplify the life of low power system users.
Though this is found as an "idea", Gentoo developers do not rule out the possibility and they are talking about it about it, while on the part of users, opinions are already divided.
Si you want to know more about it, you can check the original note in the following link.