From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Packaging CDEmu and VHBA kernel module Date: Tue, 12 Feb 2019 23:48:08 +0100 Message-ID: <87o97g1v4n.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:56759) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gth1B-00082W-BA for guix-devel@gnu.org; Tue, 12 Feb 2019 17:59:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gtgqb-0003mc-6w for guix-devel@gnu.org; Tue, 12 Feb 2019 17:48:14 -0500 Received: from relay7-d.mail.gandi.net ([217.70.183.200]:48555) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gtgqb-0003jK-0V for guix-devel@gnu.org; Tue, 12 Feb 2019 17:48:13 -0500 Received: from bababa (lfbn-1-12225-33.w90-92.abo.wanadoo.fr [90.92.41.33]) (Authenticated sender: mail@ambrevar.xyz) by relay7-d.mail.gandi.net (Postfix) with ESMTPSA id 0C13A20002 for ; Tue, 12 Feb 2019 22:48:08 +0000 (UTC) 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: guix-devel --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi! I'm down to packaging CDEmu (https://cdemu.sourceforge.io/about/vhba/) which depends on its own kernel module, VHBA (https://cdemu.sourceforge.io/about/vhba/). I wonder how we are supposed to package this in Guix. =2D Where to store the kernel module? =2D VHBA's documentation recommends setting up some Udev rule. Does it mean that it's up to the user to configure those rules so that they have access to VHBA and thus CDEmu? From=20the documentation: =2D-8<---------------cut here---------------start------------->8--- VHBA module provides the control character device via which communication b= etween userspace and kernelspace is done. This requires both read and write= permissions on the character device for the user running the CDEmu daemon. Typically, the read-write permissions on the /dev/vhba_ctl are achieved by = using udev's "uaccess" tag, by creating the following udev rule: KERNEL=3D=3D"vhba_ctl", SUBSYSTEM=3D=3D"misc", TAG+=3D"uaccess" The rule should be stored in a .rule file in either /lib/udev/rules.d or /e= tc/udev/rules.d directory. For the "uaccess" tag to be applied properly, th= e rule must be executed before the uaccess rule. Therefore, if the uaccess = rule is contained by /lib/udev/rules.d/70-uaccess.rules, the rule above mus= t be stored in a file with number smaller than 70. =2D-8<---------------cut here---------------end--------------->8--- Insights? =2D- Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAlxjTSgACgkQm9z0l6S7 zH8otAf/TeX0OmvrAy4K3V1h9XVjKL1acwVs02jBF6mmEN9IosbL4CnMmu0jjuOo 6JVDYRB0ZPk8vxZgSfDt05jtBl94tFO0Bkz/S5kQ3ANqe9Z/RmIAU5TapGFUe2Kw E7BMP2T/u8FAcw1TqWo9E0b9cTQ4z+xqOgdNq0bD2j2ugz2nDHX6YWKS8U2PWYZi 6SKJb1HEf9/14hDoltmZehWPmmxc5mJigRnkOBBKeObiXX41sdKcymkNQq3tgH0Y sBx0EzndtFjA7m8zAd97m3T8Afzhfz+yWTWuWm7qnAd2MjkMLSmH+uEck1hO/DVg vi0z0mRRmqJ2Haz+5MUWp90bUCEMMw== =JM7H -----END PGP SIGNATURE----- --=-=-=--