Thank you mate!!

Yep I have used all of them… perhaps I prefer doing a make olddefconfig save 
the generated .config and then clean all and run genkernel with menuconfig and 
load there (from menuconfig) the olddefconfig .config file…

But you always can think that perhaps some parameter of the new kernel as a 
consecuence of a fixed parameter in your .config could end up incorrectly 
configured causing corruptions of some sort or very unexpected and dangerous 
erroneus working mode….

That’s why I asked about your experience in this kind of aspect…

Cheers!
  



=============================

Egoitz Aurrekoetxea

Departamento de sistemas

94 - 420 94 70 | ego...@sarenet.es

S A R E N E T   S.A.U.

Parque Tecnológico. Edificio 103 | 48170 Zamudio (Bizkaia) - www.sarenet.es



Antes de imprimir este correo electrónico piense si es necesario hacerlo.









  

> El 5 dic 2024, a las 16:40, Jean-Francois Maeyhieux <b...@free.fr> escribió:
> 
> Hi,
> 
> as Norman told you, there is already a packaged kernel with all the
> necessary modules to run on any system.
> 
> If you need a stripped down kernel that only supports your hardware for
> example, and you already have a .config from a previous kernel, you
> have several options:
> 
> 1) Manual way:
> - copy .config from old/current kernel into new kernel folder
> - update the kernel configuration either way:
>  1.a) interactively: inside the new kernel folder do "make config"
> which will keep all of the options from the old .config and ask you
> interactively to set the new options (with default value and help using
> the "?" key)
>  1.b) using automatic default options: inside the new kernel folder do
> "make olddefconfig" which will keep all of the options from the old
> .config and set the new options to their recommended (i.e. default)
> values.
> - Then compile the kernel, modules and out-of-tree modules with:
>  make modules_prepare
>  make
>  emerge --ask @module-rebuild
>  make modules_install
>  make install
> - update grub configuration for openrc based system:
>  grub-mkconfig -o /boot/grub/grub.cfg
> 
> See: https://wiki.gentoo.org/wiki/Kernel/Upgrade
> 
> 2) The genkernel way:
> 
> genkernel automates the kernel build process and assembles the
> initramfs. See: https://wiki.gentoo.org/wiki/Genkernel
> 
> Regards,
>    Zentoo
> 
>> Le jeudi 05 décembre 2024 à 10:09 +0100, Egoitz Aurrekoetxea a écrit :
>> Hi mates,
>> 
>> I would love using Gentoo as Desktop and Server OS. I used sometime ago, but 
>> it caused me the fact of not being able to upgrade my systems weekly or 
>> daily, because sometimes you needed to upgrade the kernel and I was not 
>> really sure that the config entered for the kernel (loaded through Genkernel 
>> but with menuconfig and there load .config file) that was written with 
>> previous kernel version building was going to not cause something weird or 
>> bad functioning of newer built kernels with that config.
>> 
>> Does exist a way... where you could emerge world, update all the system, 
>> finally end up by upgrading the kernel and being sure that the old .config 
>> you used through menuconfig (or by any other way of importing) would not 
>> select erroneous parameters in newer kernels?. I though there were some... 
>> lint options for the .cofig?. I think I have used them sometime ago....
>> 
>> So for sumarizing, how do you manage for keep your systems up-to-date using 
>> Gentoo?. How do you manage to keep your kernel upgraded?.
>> 
>> Cheers,
> 

Reply via email to