From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Kernel modules in initrd
Date: Mon, 26 Feb 2018 16:20:08 +0100 [thread overview]
Message-ID: <87y3jfvkuv.fsf@gnu.org> (raw)
In-Reply-To: <20180225124330.2e706537@scratchpost.org> (Danny Milosavljevic's message of "Sun, 25 Feb 2018 12:43:30 +0100")
Hello,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> I've got it to work now. I've got a very minimal static kmod into the initrd and
> that's now only loading modules for which supported hardware is present.
>
> On the other hand, the initrd got 800 kiB larger - I'm not sure why modprobe
> is so big... hmm...
Yeah. If possible, I’d like to keep the initrd pure Scheme, to keep it
smallish.
I suppose the bits I’ve promised to detect necessary modules based on
modules.alias and /sys should be useful here?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-02-26 15:20 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 [this message]
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
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=87y3jfvkuv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dannym@scratchpost.org \
--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 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.