unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: phodina via <help-guix@gnu.org>
To: help-guix <help-guix@gnu.org>
Subject: How to build ramdisk and minimal roots
Date: Thu, 02 Jun 2022 15:44:54 +0000	[thread overview]
Message-ID: <eaGrB7wzLHLd1sk1oCswNR7mExVD2eSzX1FI1q86jj_R8oqLDK4r4oZFeOA7i2t2RYGxps4AeWqQGMX4PrCPGnauEL3W0qGC7_Ct1cIgEjc=@protonmail.com> (raw)

Hi,

I'm attempting to run Guix on Pinenote - eink tablet running Aarch64 [1].

Here's definition for the kernel based on mainline kernel with patches.

I build the kernel running this command:

guix build -f kernel.scm --target=aarch64-linux-gnu

However, I'm still missing ramdisk and I don't know how to build it. Do I have to come up with the whole system definition or is there way to generate it without one?

Also what's the best way to generate minimal roots, pack it as tarball?

I've run:

guix system image --list-image-types

but none of them is simple tarball. Should I instead pick some dir and run guix init on it and later just put the content into tarball?

(define-module (kernel)
#:use-module (gnu packages)
#:use-module (guix packages)
#:use-module (guix utils)
#:use-module (guix gexp)
#:use-module (srfi srfi-1)
#:use-module (guix download)
#:use-module (guix git-download)
#:use-module (gnu packages linux)
#:use-module ((guix licenses) #:prefix license:))

(define linux-next
(let ((commit "d869c01c005f5ef5e77485409e890d62a4ae353d")
(revision "1"))
(package
(inherit linux-libre-arm64-generic)
(name "linux-next")
(version (git-version "5.17-" revision commit))
(source
(origin
(method url-fetch)
(uri (string-append "https://gitlab.com/pgwipeout/linux-next/-/archive/" commit "/linux-next-" commit ".tar.gz"))
(sha256
(base32
"13mckij4492i0bhgvppxi58wxbgqxai6p08qw269y2k7khvafyqd"))))
(native-inputs
`(("kconfig" ,(local-file "pinenote_defconfig"))
,@(alist-delete "kconfig" (package-native-inputs linux-libre)))))))

[1] https://wiki.pine64.org/wiki/PineNote[2] https://guix.gnu.org/manual/en/html_node/Initial-RAM-Disk.html

----
Petr

                 reply	other threads:[~2022-06-02 15:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='eaGrB7wzLHLd1sk1oCswNR7mExVD2eSzX1FI1q86jj_R8oqLDK4r4oZFeOA7i2t2RYGxps4AeWqQGMX4PrCPGnauEL3W0qGC7_Ct1cIgEjc=@protonmail.com' \
    --to=help-guix@gnu.org \
    --cc=phodina@protonmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).