From: raingloom <raingloom@riseup.net>
To: guix-devel@gnu.org
Subject: Re: initrd: why do we need static linking?
Date: Tue, 5 May 2020 21:59:48 +0200 [thread overview]
Message-ID: <20200505215948.3b2c1e2a@riseup.net> (raw)
In-Reply-To: <87h7wun2ua.fsf@gnu.org>
On Tue, 05 May 2020 11:33:17 +0200
Ludovic Courtès <ludo@gnu.org> wrote:
> Hi,
>
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
> > why do we need to link packages statically to include them in the
> > initrd? Can’t we just copy the package closure into the initrd?
>
> You can refer to any package in the initrd gexp and its whole closure
> is automatically included in the initrd.
>
> However, to minimize the size of the initrd (it must fit in memory,
> uncompressed), we typically use stripped statically-linked packages.
>
> HTH!
>
> Ludo’.
>
It'd actually be nice if static linking could be used in places other
than the initrd. I'm experimenting with some old resource constrained
machines, and it made me realize just how much space even a basic `guix
pull` can take up.
next prev parent reply other threads:[~2020-05-05 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 6:34 initrd: why do we need static linking? Ricardo Wurmus
2020-05-05 9:33 ` Ludovic Courtès
2020-05-05 19:59 ` raingloom [this message]
2020-05-06 14:13 ` Ludovic Courtès
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=20200505215948.3b2c1e2a@riseup.net \
--to=raingloom@riseup.net \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).