From mboxrd@z Thu Jan 1 00:00:00 1970 From: Petter Subject: Re: modprobe on guix Date: Tue, 22 Sep 2015 10:32:38 +0200 Message-ID: <87bncuhn15.fsf@x200.i-did-not-set--mail-host-address--so-tickle-me> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56913) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZeJ0Q-0003Uf-2A for guix-devel@gnu.org; Tue, 22 Sep 2015 04:32:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZeJ0L-0007HS-2u for guix-devel@gnu.org; Tue, 22 Sep 2015 04:32:53 -0400 Received: from mx01.mykolab.com ([95.128.36.1]:8416 helo=mx-out03.mykolab.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZeJ0K-0007Gn-K4 for guix-devel@gnu.org; Tue, 22 Sep 2015 04:32:48 -0400 Received: from mx04.mykolab.com (mx04.mykolab.com [10.20.7.102]) by mx-out03.mykolab.com (Postfix) with ESMTPS id 22043225BD for ; Tue, 22 Sep 2015 10:32:40 +0200 (CEST) In-Reply-To: 87mvwflpn2.fsf@gnu.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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: guix-devel@gnu.org > One solution would be to provide a /etc/environment file containing the > right value for LINUX_MODULE_DIRECTORY (=E2=80=98sudo=E2=80=99 honors tha= t, according to > sudoers(5).) Yes, this is interesting. When i considered this previously i prematurely put it aside because it requires PAM, and i wrongly concluded our sudo wasn't configured with PAM (based on package definition). On second look, i see PAM is on by default for Linux distributions when building sudo; also running sudo -V as root user confirms this. However, creating /etc/environment and putting stuff there doesn't have any effect for me. But i believe the reason is that a module needs to be added to linux-pam, namely pam_env[1]. I'd like to have a go at this and see if i can make a patch for this. Maybe it makes sense to put /all/ the environment variables, especially for root operations, in /etc/environment? From what i understand variables from outside this file will not be expanded, so if not it would mean duplicating definitions. Also, having this as a just-for-those-sudo-users would be easy for root users to miss updating. Then obviously root logins would have to make use of this file as well, but i'm sure that can be arranged. I'll look more into this. [1] http://www.linux-pam.org/Linux-PAM-html/sag-pam_env.html Petter