Bug#947847: please install systemd-sysusers using update-alternatives
On 1/29/20 1:50 PM, Raphael Hertzog wrote:
> On Wed, 29 Jan 2020, Thomas Goirand wrote:
>> echo 'u radvd - "radvd daemon"' | \
>> systemd-sysusers --replace=/usr/lib/sysusers.d/radvd.conf
> Does opensysusers support this use case?
Yes it does.
> There's no need to predict the future, you must analyze the
> current situation and go forward from there.
Of course we are planning for the future. Let's say an important feature
appears to be needed (this is just a point or argumentation at this
time, please everyone: don't add unnecessary FUD), then of course, it's
always possible to fill the gap and implement the missing feature. The
clear goal is for opensysusers to become a full replacement of the
> As for the
> service creating users during boot, you can provide a debconf
> question giving the option to the user to install an override
> of systemd-sysusers.service which actually calls opensysusers.
The intend is for opensysusers to be a full replacement, I don't see why
we should bother users with some annoying debconf prompt that they
probably wont be able to understand without a an extensive knowledge of
> And when we get to the point where the lack of systemd-sysuvers is a
> problem, we can always patch programs to use /bin/create-system-users
> instead of systemd-sysusers.
I'm unsure what your above proposal is, so let's expand a little bit.
Sorry if it appears I'm distorting your words (that's not the intent).
This reasoning can make sense, if we agree that we should use something
else than /bin/systemd-sysusers and standardize on something else like
/bin/sysusers. Then we modify the Debian policy that /bin/sysusers is
*the* way to do things, and using /bin/systemd-sysusers becomes a bug of
severity "serious" (policy violation).
However, imposing everyone (for current or future use of sysusers) to
handle a specific case for opensysusers is IMO *not* the way to go. And
this is the very point of this bug entry.
Thomas Goirand (zigo)