From: Meiyo Peng <meiyo.peng@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34005@debbugs.gnu.org
Subject: [bug#34005] [PATCH] system: Add sudoedit to %setuid-programs.
Date: Sat, 12 Jan 2019 20:06:27 +0800 [thread overview]
Message-ID: <87va2uulks.fsf@gmail.com> (raw)
In-Reply-To: <87h8ee6tv3.fsf@gnu.org>
Hi Ludovic,
Ludovic Courtès writes:
> Hi Meiyo,
>
> Meiyo Peng <meiyo.peng@gmail.com> skribis:
>
>> This patch adds sudoedit to %setuid-programs. Although sudoedit is
>> equivalent to "sudo -e" and sudo is already in %setuid-programs, I
>> prefer to type sudoedit in terminal. sudoedit is a common command in
>> Linux distros. I use it frequently. It would be great if guix users
>> are not forced to fallback on "sudo -e".
>
> The problem I see is that on GuixSD /etc/sudoers is not supposed to be
> edited directly. Instead, users are expected to specify ‘sudoers-file’
> in their OS config, which generates a read-only /etc/sudoers.
>
> Whatever changes you make manually to that file are lost upon reboot or
> reconfiguration.
>
> Thus I feel like we should discourage ‘sudo -e’, ’sudoedit’, and
> ‘visudo’ altogether.
>
> WDYT?
I agree we should discourage users to edit files in /etc that are
managed by guix. These files will be overridden upon `guix system
reconfigure`, so user's modification will be lost. They should change
these files in the guix way by using config.scm.
However, sudoedit can also be used to edit files in /media, /mnt, /opt,
/srv and /var. These files require root priviledge to edit and they are
not managed by guix. This is the main reason we need sudoedit.
Oh, I also use sudoedit to edit /etc/config.scm.
So, WDYT?
--
Meiyo Peng
https://www.pengmeiyu.com
next prev parent reply other threads:[~2019-01-12 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 5:22 [bug#34005] [PATCH] system: Add sudoedit to %setuid-programs Meiyo Peng
2019-01-12 10:41 ` Ludovic Courtès
2019-01-12 12:06 ` Meiyo Peng [this message]
2019-01-12 12:28 ` Meiyo Peng
2019-01-12 20:03 ` Efraim Flashner
2019-01-13 20:43 ` bug#34005: " Ludovic Courtès
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=87va2uulks.fsf@gmail.com \
--to=meiyo.peng@gmail.com \
--cc=34005@debbugs.gnu.org \
--cc=ludo@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.