From: aurel.pere@gmail.com
To: Siddh Raman Pant <code@siddh.me>
Cc: paulo miguel almeida <paulo.miguel.almeida.rodenas@gmail.com>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: custom compil
Date: Thu, 26 Jan 2023 01:13:42 +0100 (GMT+01:00) [thread overview]
Message-ID: <a193c037-2306-4e1d-ac5e-a9c388bb7312@gmail.com> (raw)
In-Reply-To: <185eb05138c.7a3744fd121427.2057112906350747697@siddh.me>
[-- Attachment #1.1: Type: text/plain, Size: 1705 bytes --]
Ok thanks for these infos i will check it out
When saying automatic i was referring to kernel updates in package repositories (with apt or dnf) where auto download and install can be configured for security updates...i was thinking about applying config options but i guess they are already compiled?
Isnt there a tool that would download new kernel based on repository security updates and that would compile it with a provided config file?
I can use a bash script or ansible role but i dont see how to keep close to the official kernel distribution updates automatically...
Thanks
25 janv. 2023 23:21:15 Siddh Raman Pant <code@siddh.me>:
> On Thu, 26 Jan 2023 at 03:25:08 +0530, A.Péré wrote:
>> Is there a distribution with automated tools to compile a kernel
>> with custom config settings
>
> Yes, it is your favourite distro, whichever that may be. You just
> need the tools to build, which you may already have, but can be seen
> in docs: https://www.kernel.org/doc/html/latest/process/changes.html
>
>> that ils easier and more accessible
>
> If you want a GUI, use `make xconfig`.
>
>> un particular for automated updates with automatic custom compiling config?
>
> Have your custom config options in a separate file somewhere, and use
> scripts/kconfig/merge_config.sh to merge. Example in a script:
>
> make defconfig
> ./scripts/kconfig/merge_config.sh .config common.config
>
> The script will take care of requisite stuff, which additional options
> to enable, etc.
>
> Or you can have your entire config saved in .config, and just run
> merge_config.sh everytime you pull newer kernel code.
>
> Thanks,
> Siddh
[-- Attachment #1.2: Type: text/html, Size: 2738 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2023-01-26 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 22:26 custom compil A.Péré
2023-01-22 22:52 ` Paulo Miguel Almeida
2023-01-25 21:55 ` aurel.pere
2023-01-25 22:22 ` Siddh Raman Pant
[not found] ` <185eb05138c.7a3744fd121427.2057112906350747697@siddh.me>
2023-01-26 0:13 ` aurel.pere [this message]
2023-01-26 12:28 ` Siddh Raman Pant
2023-01-26 20:49 ` aurel.pere
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=a193c037-2306-4e1d-ac5e-a9c388bb7312@gmail.com \
--to=aurel.pere@gmail.com \
--cc=code@siddh.me \
--cc=kernelnewbies@kernelnewbies.org \
--cc=paulo.miguel.almeida.rodenas@gmail.com \
/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