all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Petter <petter@mykolab.ch>
To: guix-devel@gnu.org
Subject: Re: modprobe on guix
Date: Tue, 22 Sep 2015 10:32:38 +0200	[thread overview]
Message-ID: <87bncuhn15.fsf@x200.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: 87mvwflpn2.fsf@gnu.org

> One solution would be to provide a /etc/environment file containing the
> right value for LINUX_MODULE_DIRECTORY (‘sudo’ honors that, 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

             reply	other threads:[~2015-09-22  8:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22  8:32 Petter [this message]
2015-09-22 12:45 ` modprobe on guix Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2015-09-20 18:55 Petter
2015-09-21 16:10 ` Ludovic Courtès
2015-03-24 22:39 白い熊@相撲道
2015-03-25 12:57 ` Mark H Weaver
2015-03-25 18:22   ` Alex Kost
2015-03-25 21:01     ` Ludovic Courtès
2015-03-26 13:06       ` Alex Kost

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bncuhn15.fsf@x200.i-did-not-set--mail-host-address--so-tickle-me \
    --to=petter@mykolab.ch \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.