From: Jeff Bauer <jeffrubic@gmail.com>
To: John Soo <jsoo1@asu.edu>
Cc: help-guix@gnu.org, Quiliro's lists <kiliro@riseup.net>
Subject: Re: editing /etc/sudoers
Date: Mon, 17 Jun 2019 13:02:30 -0500 [thread overview]
Message-ID: <20190617180230.GI12459@serpent> (raw)
In-Reply-To: <1CADB6BB-4C4E-43C8-BB5C-107D564B2C89@asu.edu>
On Mon, Jun 17, 2019 at 10:03:20AM -0700, John Soo wrote:
> Sorry this is so confusing. Let me know if I’m missed something since
> I’ve been half-following this thread. I think what you may want to do
> is use the sudoers-file field when specifying your operating system
> rather than using visudo to edit the file. This way you will have
> persistent and declarative specification for the sudoers file. The
> sudoers-file field allows you to place an arbitrary file-like object in
> it, so you can put whatever you want to add using visudo there and it
> will work the same. Check the manual for
> reference: [1]https://www.gnu.org/software/guix/manual/en/html_node/ope
> rating_002dsystem-Reference.html#operating_002dsystem-Reference
John,
Correct, I got my local sudoers working a few
days ago, so there's no longer any confusion on
my end (but thanks for your reply).
However, guix's visudo should probably be patched
to allow editing of a *local* ~/etc/sudoers file,
which currently won't work because /usr/bin/vi
appears to be hard-coded.
-Jeff
next prev parent reply other threads:[~2019-06-17 18:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 11:55 editing /etc/sudoers Jeff Bauer
2019-06-14 13:16 ` David Larsson
2019-06-14 13:21 ` Tobias Geerinckx-Rice
2019-06-14 13:58 ` Jeff Bauer
2019-06-16 2:27 ` Quiliro's lists
2019-06-16 14:18 ` Jeff Bauer
2019-06-16 14:30 ` Jeff Bauer
2019-06-16 23:08 ` Quiliro's lists
2019-06-16 23:20 ` Jeff Bauer
2019-06-17 7:17 ` Andreas Enge
2019-06-17 14:34 ` Quiliro's lists
2019-06-17 15:44 ` Jeff Bauer
2019-06-17 17:03 ` John Soo
2019-06-17 18:02 ` Jeff Bauer [this message]
2019-06-17 20:16 ` John Soo
2019-06-17 7:53 ` Hartmut Goebel
2019-06-17 15:48 ` Jeff Bauer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190617180230.GI12459@serpent \
--to=jeffrubic@gmail.com \
--cc=help-guix@gnu.org \
--cc=jsoo1@asu.edu \
--cc=kiliro@riseup.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).