From: Jeff Bauer <jeffrubic@gmail.com>
To: Quiliro's lists <kiliro@riseup.net>
Cc: help-guix@gnu.org
Subject: Re: editing /etc/sudoers
Date: Sun, 16 Jun 2019 18:20:54 -0500 [thread overview]
Message-ID: <20190616232054.GA1602@nimrod> (raw)
In-Reply-To: <45f53d38f8dbf54c80bc7e2153785295@riseup.net>
On Sun, Jun 16, 2019 at 04:08:06PM -0700, Quiliro's lists wrote:
> El 2019-06-16 09:30, Jeff Bauer escribió:
> > On Sat, Jun 15, 2019 at 07:27:57PM -0700, Quiliro's lists wrote:
> >> Regarding the EDITOR variable, if Guix is the installer of the needed
> >> editor it is the only situation when this regards to Guix.
> >>
> >> Would you please clarify your issue?
> >
> > Issue clarified up-thread:
> >
> > https://lists.gnu.org/archive/html/help-guix/2019-06/msg00140.html
>
> No you have not. It is not clear wether you are using Guix System
> Distribution or another GNU distribution such as Debian.
Okay, to make it more clear: I was having a problem
trying to use visudo on a native Guix System. The
visudo packaged with the Guix System cannot actually
edit a sudoers file because it relies on /usr/bin/vi,
but it can be used as a command line validation checker.
-Jeff
next prev parent reply other threads:[~2019-06-16 23:21 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 [this message]
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
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=20190616232054.GA1602@nimrod \
--to=jeffrubic@gmail.com \
--cc=help-guix@gnu.org \
--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).