On 26 Jan 2024 09:21 -0500, from mst...@debian.org (Michael Stone):
> In fact
> the trend is more toward ephemeral runtime allocation rather than hardcoding
> persistent IDs as more services/subsystems are designed to run in isolation.
Not only that, but also without persisting data to disk
On Thu, Jan 18, 2024 at 07:31:05AM -0500, Greg Wooledge wrote:
This is one of those "the boat has already left the dock" situations.
If this were going to happen, it would have to have happened in the
early 1990s. There is no feasible way to make it happen now.
It's also a pointless endeavor,
On Thu 18 Jan 2024 at 07:31:05 (-0500), Greg Wooledge wrote:
> On Thu, Jan 18, 2024 at 05:38:37AM -, David Chmelik wrote:
> > Couldn't Debian standardize uid:gid numbers for daemons?
>
> The thing is, Debian has tens of thousands of packages, and any one
> of these p
On Thu, 18 Jan 2024 13:40:01 +0100, Greg Wooledge wrote:
> On Thu, Jan 18, 2024 at 05:38:37AM -, David Chmelik wrote:
>> Couldn't Debian standardize uid:gid numbers for daemons?
>[...] * Every obscure, niche package's users and groups would have to be
>added to every De
On Thu, Jan 18, 2024, 9:15 AM Stefan Monnier
wrote:
> > I haven't tried it but I would assume that if the user exists then the
> > package uses that. So cresting a template /etc/passwd before
> > installing packages would fix this.
>
> That works, indeed. Maybe Someone™ should develop a small
Stefan Monnier wrote:
> > I haven't tried it but I would assume that if the user exists then the
> > package uses that. So cresting a template /etc/passwd before
> > installing packages would fix this.
>
> That works, indeed. Maybe Someone™ should develop a small "UGID server"
> which
> I haven't tried it but I would assume that if the user exists then the
> package uses that. So cresting a template /etc/passwd before
> installing packages would fix this.
That works, indeed. Maybe Someone™ should develop a small "UGID server"
which integrates into Debian's `adduser/addgroup`
> I agree this is annoying, and hardish to fix once servers are deployed.
FWIW, I have "fixed" such things after the fact without too much
trouble by editing the /etc/{passwd,group,...} files and do a recursive
`chown`. I'm sure it can result in a broken system depending on the
details, tho.
Hello,
On Thu, Jan 18, 2024 at 06:23:28AM +, Tim Woodall wrote:
> On Thu, 18 Jan 2024, David Chmelik wrote:
>
> > Couldn't Debian standardize uid:gid numbers for daemons?
[…]
> I haven't tried it but I would assume that if the user exists then the
> package uses that.
Co
On Thu, Jan 18, 2024 at 05:38:37AM -, David Chmelik wrote:
> Couldn't Debian standardize uid:gid numbers for daemons?
The thing is, Debian has tens of thousands of packages, and any one
of these packages is capable of creating new UIDs and/or GIDs if it
feels like doing
On Thu, 18 Jan 2024, David Chmelik wrote:
Couldn't Debian standardize uid:gid numbers for daemons? The oldest--and
only strictly UNIX-like--GNU/Linux (Slackware) does this so if you install
multiple instances and want them the same, you can backup /etc/passwd & /
etc/group from one and
Couldn't Debian standardize uid:gid numbers for daemons? The oldest--and
only strictly UNIX-like--GNU/Linux (Slackware) does this so if you install
multiple instances and want them the same, you can backup /etc/passwd & /
etc/group from one and use them on another (as long as there ar
12 matches
Mail list logo
