From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: Re: Loading modules built using linux-module-build-system Date: Mon, 21 Oct 2019 20:27:33 +0200 Message-ID: <20191021202733.3c340770@scratchpost.org> References: <877e8snntp.fsf@jlicht.xyz> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/=yEQso/ro/6P75Ddz.vGBwg"; protocol="application/pgp-signature"; micalg=pgp-sha256 Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:53414) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iMcPa-000114-AT for guix-devel@gnu.org; Mon, 21 Oct 2019 14:28:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iMcPZ-0002rE-5F for guix-devel@gnu.org; Mon, 21 Oct 2019 14:28:10 -0400 Received: from dd26836.kasserver.com ([85.13.145.193]:57036) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iMcPY-0002pY-UG for guix-devel@gnu.org; Mon, 21 Oct 2019 14:28:09 -0400 In-Reply-To: <877e8snntp.fsf@jlicht.xyz> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Jelle Licht Cc: guix-devel@gnu.org --Sig_/=yEQso/ro/6P75Ddz.vGBwg Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi, On Tue, 09 Jul 2019 00:50:10 +0200 Jelle Licht wrote: > I have verified this way of loading modules to work, but was wondering > whether we should rather provide a `out-of-tree-kernel-module' service > of sorts to do this. >=20 > To resolve out-of-tree kernel module dependencies, I guess we would need > to construct a union of all outputs so we can pass along one value for > LINUX_MODULE_DIRECTORY that contains all out-of-tree modules that might > be needed for one invocation of modprobe. That sounds like a strange special-casing of out-of-tree modules. What prevents us from presenting the union as /run/current-system/kernel/lib/modules in the first place? That would allow everyone, including all programs on the system and the ini= trd, to use all modules. Them being in-tree or out-of-tree is a technical detail that should be of no technical consequence to anyone. I suggest to add a field to the operating-system declaration that lists all the packages that contain loadable kernel modules. We could also just make operating-system-kernel be a list--which would be the most direct way I guess. After all, "the" kernel consists of all those modules and the zImage--also in RAM in kernel space while using the stuff. That said, extensibility would be nice--if services could request what kernel modules to add to the operating-system. P.S. How's that supposed to work with the Hurd? I'd guess they are even more modular than this. If we add kernel modularity, might as well also take into account the Hurd. --Sig_/=yEQso/ro/6P75Ddz.vGBwg Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl2t+JUACgkQ5xo1VCww uqXUDQf/WquA9phQaqCdTRtmlS3iFMLEJw33ka3Glbk6n/410bvk3oAycly77GsQ LArqkzxjuA0v/w40JOdLbepQ8rUnjpEzWKZGrP5bCe+JSidv3jXbEE8ksklq65z6 MiE8R4aUiE8R6OcVs6Fa/YiBPMxga1MQ6EJHkuOz7NSPqA8ZJ6CHxIPYnkQAkOwn 1pGoTD7jYShP9Ws7+0SaKsFQbz3dHaMwiLpVQrX8mpp0LUUXlhhxno4MPYhVsPDM OyAm5EYi1EH6jdo70PERgOgg7/aglWe0T99ysENLOdFDsM7uJBgvZpDkhqvJtVmd 9G3Jrhbck+XC0qGDttqtC4264Tipcw== =4mkb -----END PGP SIGNATURE----- --Sig_/=yEQso/ro/6P75Ddz.vGBwg--