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: Tue, 27 Feb 2018 16:04:01 +0100
Message-ID: <87vaei1nku.fsf@gnu.org>
References: <20180222211707.GB9758@jurong> <87eflck7ko.fsf@netris.org>
	<87vaen8h4w.fsf@gnu.org> <20180224082812.5ubmg642qe4mm7dd@abyayala>
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]:34125)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1eqgnY-0000cC-Jf
	for guix-devel@gnu.org; Tue, 27 Feb 2018 10:04:12 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1eqgnU-0006lZ-DW
	for guix-devel@gnu.org; Tue, 27 Feb 2018 10:04:08 -0500
Received: from hera.aquilenet.fr ([185.233.100.1]:47320)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <ludo@gnu.org>) id 1eqgnU-0006kw-6K
	for guix-devel@gnu.org; Tue, 27 Feb 2018 10:04:04 -0500
In-Reply-To: <20180224082812.5ubmg642qe4mm7dd@abyayala> (ng0@crash.cx's
	message of "Sat, 24 Feb 2018 08:28:12 +0000")
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,

ng0 <ng0@crash.cx> skribis:

> Ludovic Court=C3=A8s transcribed 0.8K bytes:
>> Hello,
>>=20
>> Mark H Weaver <mhw@netris.org> skribis:
>>=20
>> > 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.
>>=20
>> 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 th=
ese two pieces,
>> =E2=80=98guix system=E2=80=99 should be able to warn when a module is mi=
ssing.
>>=20
>> Ludo=E2=80=99.
>
> I'm willing to test those, it's probably less time consuming than figurin=
g out
> the corretc modules the Hetzner CLoud instance needs.

I=E2=80=99ve posted the patch series here:

  https://bugs.gnu.org/30629

Feedback welcome!

Ludo=E2=80=99.