From: John Soo <jsoo1@asu.edu>
To: Jeff Bauer <jeffrubic@gmail.com>
Cc: help-guix@gnu.org, Quiliro's lists <kiliro@riseup.net>
Subject: Re: editing /etc/sudoers
Date: Mon, 17 Jun 2019 13:16:50 -0700 [thread overview]
Message-ID: <6D150B0A-8904-4E3F-9A87-2735097570E1@asu.edu> (raw)
In-Reply-To: <20190617180230.GI12459@serpent>
Thanks Jeff,
Sounds good. Do you think this thread is effectively solved, then? You might consider opening a bug report for visudo.
- John
> On Jun 17, 2019, at 11:02 AM, Jeff Bauer <jeffrubic@gmail.com> wrote:
>
>> 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 20:16 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
2019-06-17 20:16 ` John Soo [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6D150B0A-8904-4E3F-9A87-2735097570E1@asu.edu \
--to=jsoo1@asu.edu \
--cc=help-guix@gnu.org \
--cc=jeffrubic@gmail.com \
--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.
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.