From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Kernel modules in initrd
Date: Tue, 27 Feb 2018 21:52:30 +0100 [thread overview]
Message-ID: <20180227215230.44927d44@scratchpost.org> (raw)
In-Reply-To: <20180227200416.6b9dd5e6@scratchpost.org>
On Tue, 27 Feb 2018 20:32:49 +0100
Danny Milosavljevic <dannym@scratchpost.org> wrote:
> > > P.S. How come glibc is in the initrd? Shouldn't guile have statically linked it?
> > > glibc is like 50000 kiB. In that case saving 800 kiB is not really worth it...
> >
> > One of the packages that ends up in the initrd must be dynamically
> > linked. You need to find out which one it is.
>
> It's because of bash-minimal.
And that's because of:
./gnu/store/lksm6f1ahvikxnwkfs34sabbb4f7209p-guile-static-stripped-2.2.3/share/guile/2.2/ice-9/popen.scm: (open-pipe* mode "/gnu/store/icz3hd36aqpjz5slyp4hhr8wsfbgiml1-bash-minimal-4.4.12/bin/bash" "-c" command))
next prev parent reply other threads:[~2018-02-27 19:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 21:17 Kernel modules in initrd Andreas Enge
2018-02-22 21:29 ` Jan Nieuwenhuizen
2018-02-22 21:44 ` Danny Milosavljevic
2018-02-22 21:34 ` Danny Milosavljevic
2018-02-22 21:50 ` [PATCH] linux-initrd: Add ATA and SAS modules to the default set of modules Danny Milosavljevic
2018-02-27 15:03 ` Ludovic Courtès
2018-02-22 21:53 ` Kernel modules in initrd Andreas Enge
2018-02-22 22:01 ` Mark H Weaver
2018-02-23 1:00 ` Danny Milosavljevic
2018-02-23 14:28 ` Danny Milosavljevic
2018-02-23 23:02 ` Andreas Enge
2018-02-25 11:43 ` Danny Milosavljevic
2018-02-26 15:20 ` Ludovic Courtès
2018-02-26 16:26 ` Danny Milosavljevic
2018-02-27 15:02 ` Ludovic Courtès
2018-02-27 19:32 ` Danny Milosavljevic
2018-02-27 20:52 ` Danny Milosavljevic [this message]
2018-02-28 21:49 ` Ludovic Courtès
2018-02-23 22:39 ` Ludovic Courtès
2018-02-24 8:28 ` ng0
2018-02-27 15:04 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180227215230.44927d44@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.