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:49:47 +0200 Message-ID: <20191021204857.5dff6e9b@scratchpost.org> References: <877e8snntp.fsf@jlicht.xyz> <20191021202733.3c340770@scratchpost.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/6w49X5yehTAkhidNdpWI.x7"; protocol="application/pgp-signature"; micalg=pgp-sha256 Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:56119) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iMckf-000861-Nt for guix-devel@gnu.org; Mon, 21 Oct 2019 14:49:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iMcke-00028R-Ix for guix-devel@gnu.org; Mon, 21 Oct 2019 14:49:57 -0400 Received: from dd26836.kasserver.com ([85.13.145.193]:59070) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iMcke-00026g-CW for guix-devel@gnu.org; Mon, 21 Oct 2019 14:49:56 -0400 In-Reply-To: <20191021202733.3c340770@scratchpost.org> 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_/6w49X5yehTAkhidNdpWI.x7 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I just thought of a better way. Represent the Linux kernel (including out-of-tree-modules) as a profile, most probably just the system profile (which already exists--extend it). A user package (for example if referred to by a system service) would propagate-input the kernel module package it requires. That would also make sure that conflicts are handled (otherwise they'd be "handled" by the kernel doing strange stuff at runtime depending on which package's "foo.ko" got modprobed first if there are multiple files with the same name "foo.ko" in different packages). The union to be presented as /run/current-system/kernel/lib/modules would be all the packages of the system profile which have a /lib/modules/ directory in their derivations. It would all automagically work, provided that we modify Guix system so that whoever populates /run/current-system/kernel/lib/modules does the union. The limitation of it not be possible for a regular user to add kernel modules is OK I think. That's where I draw the line--a normal profile has no business adding Linux kernel modules to kernel space in the first place. Not sure how the interactions with Guix on a foreign distribution would be, though. Do those even use the same Guile modules touched here? --Sig_/6w49X5yehTAkhidNdpWI.x7 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl2t/csACgkQ5xo1VCww uqV/Mwf/TX0P7sXmF7w2gbbGW3nITH1zpfI8ZbvcxY7uW+XwtA636oXVbPItj0Zz 88OXyO8K045b2NmRUiZP4tnVidEVAm2zrR4NQnZKLb3Z+T8ROBvCbrVX2AU6NLEI xtE5oNv7b2e/fHHmXlZkgMSumgWAt/otCnrCP6z3f3/diYlNmg3lKUrJ769SDNOj 8JwgGyvxrh/eXC3vo2RjJ9QVjzE+npiYYSzDDAffrrom/WVjKgJQk6g2tQN0xO1o Tpfanyu75wo10PP5q5qF1iS+q+t5g3fdbAZB/hHX1NvnmpAF+DehEwOdm8fUOUfl BSgMoGxkEi3IqtpYZeAhoZnbUqAFKQ== =iUnf -----END PGP SIGNATURE----- --Sig_/6w49X5yehTAkhidNdpWI.x7--