public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: "egoitz@sarenet.es" <egoitz@sarenet.es>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] Using Gentoo as server and desktop
Date: Sat, 7 Dec 2024 03:19:44 +0100	[thread overview]
Message-ID: <EA0ACEAD-681A-4B98-B550-1D03A9680A97@sarenet.es> (raw)
In-Reply-To: <8429253590dd4157fd032b063bcf92a9365be14d.camel@free.fr>

[-- Attachment #1: Type: text/plain, Size: 4650 bytes --]


  Thank you so much mate.

This kind of shared experience was what I was looking to hear to know… to see them…

Cheers!



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

Egoitz Aurrekoetxea

Departamento de sistemas

94 - 420 94 70 | egoitz@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 6 dic 2024, a las 13:43, Jean-Francois Maeyhieux <b4b1@free.fr> escribió:
> 
> 
> The defaults selected by olddefconfig should be safe.
> At worst, it will add support for things you don't need.
> 
> Personally, I have been maintaining my own kernel configuration for 20
> years, using oldconfig and selecting all new options myself. I deselect
> experimental ones and most device related ones (as I already have
> support for the devices I use). For everything else I look on the web
> about it, it's a way to know what you're doing and to learn a lot about
> what the kernel support through time.
> 
> I'm certainly a config kernel integrist :)
> 
>> Le jeudi 05 décembre 2024 à 22:28 +0100, egoitz@sarenet.es a écrit :
>> 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!
>>   
>> 
>> firma_saremail
>> 
>> 
>>   
>> 
>>>> El 5 dic 2024, a las 16:40, Jean-Francois Maeyhieux <b4b1@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,
>>> 
> 

[-- Attachment #2: Type: text/html, Size: 13692 bytes --]

      reply	other threads:[~2024-12-07  2:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05  9:09 [gentoo-server] Using Gentoo as server and desktop Egoitz Aurrekoetxea
2024-12-05  9:24 ` Norman Rieß
2024-12-05 15:40 ` Jean-Francois Maeyhieux
2024-12-05 21:28   ` egoitz
2024-12-06 12:43     ` Jean-Francois Maeyhieux
2024-12-07  2:19       ` egoitz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=EA0ACEAD-681A-4B98-B550-1D03A9680A97@sarenet.es \
    --to=egoitz@sarenet.es \
    --cc=gentoo-server@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox