From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Kernel modules in initrd
Date: Fri, 23 Feb 2018 23:39:59 +0100 [thread overview]
Message-ID: <87vaen8h4w.fsf@gnu.org> (raw)
In-Reply-To: <87eflck7ko.fsf@netris.org> (Mark H. Weaver's message of "Thu, 22 Feb 2018 17:01:11 -0500")
Hello,
Mark H Weaver <mhw@netris.org> skribis:
> To make this easier, I think the right approach is to include many
> modules like these to our installation image initrd, and then to
> automatically detect which modules are needed for booting. A future
> easy installer could automatically add those modules to the OS config,
> but in the meantime we could simply print a message recommending that
> the user should add the needed modules to their initrd config.
FWIW I have code that I was planning to polish and submit (hopefully
next week) that determines modules needed for a particular device by
walking /sys. In addition, I thought we could make the initrd module
list a first class field of ‘operating-system’. With these two pieces,
‘guix system’ should be able to warn when a module is missing.
Ludo’.
next prev parent reply other threads:[~2018-02-23 22:40 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
2018-02-28 21:49 ` Ludovic Courtès
2018-02-23 22:39 ` Ludovic Courtès [this message]
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=87vaen8h4w.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.