Kernel Newbies archive mirror
 help / color / mirror / Atom feed
From: "A.Péré" <aurel.pere@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: custom compil
Date: Sun, 22 Jan 2023 23:26:40 +0100	[thread overview]
Message-ID: <CAOs_nBt2K-smnSwttp=WQCEBqZnb4_-pSgGVS=Fv=UdiYO=X-A@mail.gmail.com> (raw)

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)
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

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

             reply	other threads:[~2023-01-22 22:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 22:26 A.Péré [this message]
2023-01-22 22:52 ` custom compil 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
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='CAOs_nBt2K-smnSwttp=WQCEBqZnb4_-pSgGVS=Fv=UdiYO=X-A@mail.gmail.com' \
    --to=aurel.pere@gmail.com \
    --cc=kernelnewbies@kernelnewbies.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).