unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Michael Rohleder <mike@rohleder.de>
To: "AMIR ZAQUAN BIN YAZID / UPM" <198739@student.upm.edu.my>
Cc: help-guix@gnu.org
Subject: Re: Updating Linux Kernel Manually in GUIX system
Date: Thu, 08 Jul 2021 13:54:43 +0200	[thread overview]
Message-ID: <875yxl6mws.fsf@rohleder.de> (raw)
In-Reply-To: <CAGhvSGXt0hMSMi_hNA_Jq=vEwpHWTvKr6kV9K14ZDfFv0xz4bA@mail.gmail.com> (AMIR ZAQUAN BIN YAZID's message of "Thu, 8 Jul 2021 14:45:22 +0800")

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

Hi Amir!

"AMIR ZAQUAN BIN YAZID / UPM" <198739@student.upm.edu.my> writes:
> I would like to ask regarding updating the Linux Kernel manually.
>
> I am trying to update the Linux Kernel for GUIX system manually for an
> assignment. Everything seems fine until I reach the step of copying an
> existing Linux Kernel configuration.
>
> when I input :
>
> $ cp -v /boot/config-$(uname -r) cd verif.config
>
> the result says no such file directory for the current Linux Kernel config
> which is 5.11.15.

From a running guix system you can get the kernel config from
/run/current-system/kernel/.config

>
> In addition,  when I tried to guix install some development tools such as
> libelf and libssl , guix install error : unknown package was obtained.
>

I think, the packages you are looking for are libelf and openssl.


-- 
Es ist besser ein Licht zu entzuenden, als auf die Dunkelheit zu schimpfen.
   Konfuzius

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]

      reply	other threads:[~2021-07-08 11:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08  6:45 Updating Linux Kernel Manually in GUIX system AMIR ZAQUAN BIN YAZID / UPM
2021-07-08 11:54 ` Michael Rohleder [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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=875yxl6mws.fsf@rohleder.de \
    --to=mike@rohleder.de \
    --cc=198739@student.upm.edu.my \
    --cc=help-guix@gnu.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).