From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: Kernel modules in initrd
Date: Fri, 23 Feb 2018 23:39:59 +0100
Message-ID: <87vaen8h4w.fsf@gnu.org>
References: <20180222211707.GB9758@jurong> <87eflck7ko.fsf@netris.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42091)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1epM0a-0006IG-K2
	for guix-devel@gnu.org; Fri, 23 Feb 2018 17:40:05 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1epM0Z-0005uw-Kl
	for guix-devel@gnu.org; Fri, 23 Feb 2018 17:40:04 -0500
Received: from hera.aquilenet.fr ([2a0c:e300::1]:38092)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ludo@gnu.org>) id 1epM0Z-0005tN-Cy
	for guix-devel@gnu.org; Fri, 23 Feb 2018 17:40:03 -0500
In-Reply-To: <87eflck7ko.fsf@netris.org> (Mark H. Weaver's message of "Thu, 22
	Feb 2018 17:01:11 -0500")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org

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 =E2=80=98operating-system=E2=80=99.  With these=
 two pieces,
=E2=80=98guix system=E2=80=99 should be able to warn when a module is missi=
ng.

Ludo=E2=80=99.