mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] avahi: use working defaults for user/group
Date: Thu, 13 Feb 2025 14:40:31 +0100	[thread overview]
Message-ID: <20250213134031.lhjj3xmds3wnr7fy@pengutronix.de> (raw)
In-Reply-To: <Z0l82n6UYtCN44of@pengutronix.de>

On Fri, Nov 29, 2024 at 09:35:38AM +0100, Michael Olbrich wrote:
> On Mon, Nov 11, 2024 at 12:01:22AM +0100, Roland Hieber wrote:
> > As stated by the (slightly outdated) comments, no user or group named
> > "avahi" or "avahi-autoipd" exists in the default /etc/passwd or
> > /etc/group in PTXdist, so Avahi will complain about the missing
> > user/group and refuse to start with the default configuration. Set the
> > default values to the unprivileged "nobody"/"nogroup" instead, which
> > already exist, and remove the outdated comments.
> 
> Nack. These services have separate users for a reason.
> 
> I understand that adding users is currently awkward. I've been thinking
> about better ways to do this for some time. I'm open for ideas about that.

Hmh yes, something like an install_* macro that is called in the targetinstall
stage, and writes the to-be-created users into a file from where the rootfs
package will pick it up later?

 - Roland

-- 
Roland Hieber, Pengutronix e.K.          | rhi@pengutronix.de          |
Steuerwalder Str. 21                     | https://www.pengutronix.de/ |
31137 Hildesheim, Germany                | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686         | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2025-02-13 13:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 23:01 Roland Hieber
2024-11-29  8:35 ` Michael Olbrich
2025-02-13 13:40   ` Roland Hieber [this message]
2025-02-13 20:20     ` Bruno Thomsen

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=20250213134031.lhjj3xmds3wnr7fy@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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