public inbox for kernelnewbies@kernelnewbies.org
 help / color / mirror / Atom feed
From: aurel.pere@gmail.com
To: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: custom compil
Date: Wed, 25 Jan 2023 22:55:08 +0100 (GMT+01:00)	[thread overview]
Message-ID: <b741f8c7-6e9a-4da9-a751-4cf0f9842c77@gmail.com> (raw)
In-Reply-To: <Y82+PW7L2YqRtw2J@mail.google.com>


[-- Attachment #1.1: Type: text/plain, Size: 2739 bytes --]

Hi
I thought it was a mailing list for newbies ans i coulemd find answers or at least links...
Let me rephrase the question: is there a distribution with automated tools to compile a kernel with custom config settings that ils easier and more accessible un particular for automated updates with automatic custom compiling config?
Thanks

22 janv. 2023 23:52:52 Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>:

> On Sun, Jan 22, 2023 at 11:26:40PM +0100, A.Péré wrote:
>> Hi,
>> I would like to compile a kernel for fedora following this security
>> guide ( https://www.ssi.gouv.fr/guide/recommandations-de-securite-relatives-a-un-systeme-gnulinux/
>> v2)
> 
> Hi Aurel, Fedora maintains its own kernel and while it tries to follow
> the kernel upstream, it has minor differences. They do have a mailing
> list for fedora kernels that can be found at https://docs.fedoraproject.org/en-US/quick-docs/kernel/overview/
> should you have specific questions about it.
> 
>> I have some parameters that i have put using an ansible role
>> (https://github.com/robertdebock/ansible-role-kernel).
>> The compilation works but when i reboot i get a black screen so i
>> guess i am not doing it the right way.
>> Ideally I would like to be able to compile new kernel on the fly with
>> my custom .config file for almalinux server and my fedora workstation
>> home pc.
>> I have seen this fedora doc
>> (https://docs.fedoraproject.org/en-US/quick-docs/kernel/build-custom-kernel/)
>> but at the paragraph "Building a Kernel from the Fedora dist-git" it
>> states 3. Make whatever changes or customizations you need, but no
>> information is provided on how to do that.
>> Could you help me in doing this?
>> Thank you
> 
> I must be honest with you that it's very unlikely that they will
> help you if you simply drop ansible playbooks and security best
> practices links. So far, the problem that you described is more related
> to sysadmin stuff IMO.
> 
> My 2 cents for you to do would be:
> 
> 1) use other mediums such as forums on the internet which a more focused
> on that kind of thing.
> 2) try stuff locally, read up on docs of tools you are not familiar
> with yet. With more details like errors I think you will more likely get
> across someone that has faced similar problems and can point you to a
> solution. So far your problem statement is a bit vague and it would be
> hard for anyone willing to help to actually do so.
> 
> Good luck :-)
> 
> thanks!
> 
> - Paulo A.
> 
>> 
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies@kernelnewbies.org
>> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

[-- Attachment #1.2: Type: text/html, Size: 3619 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2023-01-25 21:55 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 [this message]
2023-01-25 22:22     ` Siddh Raman Pant
     [not found]     ` <185eb05138c.7a3744fd121427.2057112906350747697@siddh.me>
2023-01-26  0:13       ` aurel.pere
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=b741f8c7-6e9a-4da9-a751-4cf0f9842c77@gmail.com \
    --to=aurel.pere@gmail.com \
    --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