From: Thomas Deutschmann <whissi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [PATCH] acct-user.eclass: don't modify existing user by default
Date: Mon, 4 Jan 2021 19:23:42 +0100 [thread overview]
Message-ID: <dd9cbc67-89ab-72da-ae4a-c98b9640ec16@gentoo.org> (raw)
In-Reply-To: <89a1c171-de56-4f9e-af2a-9140d2be3552@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 2005 bytes --]
Hi,
On 2021-01-04 19:07, Michael Orlitzky wrote:
> We could implement this with something like an /etc/users.d directory
> that would be populated with entries by either the admin or package
> manager with CONFIG_PROTECT enabled. Then the system database would be
> updated by running something like "users-update" (cf. env-update). The
> essential problem that we need to work around is that e.g. /etc/passwd
> is "owned" by multiple system packages.
>
> I think this would accomplish what you and Robin are talking about, but
> it wouldn't solve whissi's problem since it's still a Gentoo-specific
> solution.
If you really want to spend so much time on this, feel free to implement
something like this. From my point of view this is wasted time. I really
have no words for anyone believing that there must be a way to deal with
user config. This is a no go for me and most people in my bubble. Once
you have created something, it's user data. If you want to make changes,
tell the user about it but never ever mess with user configs. History is
full of examples when messing with user configs caused real harm.
For example there is a reason why we don't edit /etc files. Instead have
CONFIG_PROTECT and are only providing helpers to update config.
Do I really need to explain what can go wrong when you suddenly change
/home? What will happen to your cron jobs for example?
What will happen when you make changes to groups and reboot?
But as said, if you want to spend so much time on this and create a
complicated solution which will be adding a lot of complexity which I
think isn't worth it, *I* could live with it. It's the same like dealing
with CONFIG_PROTECT already.
People like me could just ignore changed users if changes won't go live
until you run said users-update command or make use of INSTALL_MASK.
--
Regards,
Thomas Deutschmann / Gentoo Linux Developer
fpr: C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2021-01-04 18:23 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 1:35 [gentoo-dev] [PATCH] acct-user.eclass: don't modify existing user by default Thomas Deutschmann
2021-01-04 2:41 ` Mike Gilbert
2021-01-04 3:17 ` Alec Warner
2021-01-04 3:18 ` Michael Orlitzky
2021-01-04 14:46 ` Thomas Deutschmann
2021-01-04 15:24 ` Michael Orlitzky
2021-01-04 15:55 ` David Seifert
2021-01-04 16:18 ` Thomas Deutschmann
2021-01-04 16:28 ` Michał Górny
2021-01-04 16:30 ` Thomas Deutschmann
2021-01-04 16:34 ` Thomas Deutschmann
2021-01-04 16:38 ` Michał Górny
2021-01-04 16:50 ` Thomas Deutschmann
2021-01-04 16:56 ` Michał Górny
2021-01-04 16:56 ` Mike Gilbert
2021-01-04 16:54 ` Mike Gilbert
2021-01-04 7:32 ` Robin H. Johnson
2021-01-04 16:45 ` [gentoo-dev] " James Cloos
2021-01-04 18:07 ` Michael Orlitzky
2021-01-04 18:20 ` Michał Górny
2021-01-04 18:38 ` Michael Orlitzky
2021-01-04 18:23 ` Thomas Deutschmann [this message]
2021-01-04 18:27 ` Michael Orlitzky
2021-01-04 18:32 ` Thomas Deutschmann
2021-01-04 9:23 ` [gentoo-dev] " Michał Górny
2021-01-04 14:05 ` Thomas Deutschmann
2021-01-04 16:10 ` Mike Gilbert
2021-01-04 16:14 ` Michał Górny
2021-01-04 16:20 ` Thomas Deutschmann
2021-01-08 18:11 ` Fabian Groffen
2021-01-08 18:14 ` Michał Górny
2021-01-08 18:23 ` Thomas Deutschmann
2021-01-08 18:32 ` Michał Górny
2021-01-08 15:48 ` Thomas Deutschmann
2021-01-08 16:03 ` Mike Gilbert
2021-01-08 16:29 ` Thomas Deutschmann
2021-01-08 16:50 ` Mike Gilbert
2021-01-08 17:06 ` Mike Gilbert
2021-01-08 18:10 ` Thomas Deutschmann
2021-01-08 18:31 ` Michał Górny
2021-01-08 19:15 ` Mike Gilbert
2021-01-08 17:16 ` Michał Górny
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=dd9cbc67-89ab-72da-ae4a-c98b9640ec16@gentoo.org \
--to=whissi@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox