On Wednesday, May 28th, 2025 at 12:46 PM, Lennart Poettering
wrote:
> On Mi, 28.05.25 09:43, Alexander Bokovoy (aboko...@redhat.com) wrote:
>
> > There
> > are few issues with userdb API implementation. For example, there is an
> > assumption only one responder knows the information about the a
On Tuesday, May 27th, 2025 at 11:41 PM, Carlos Rodriguez-Fernandez
wrote:
> I wonder how this is going to play out in containers with user configs if
> "/etc/{passwd,group,shadow,gshadow}" becomes legacy.
Not in containers, just normal "desktop" systems only.
--
__
On Wednesday, May 28th, 2025 at 2:43 AM, Lennart Poettering
wrote:
> systemd-userdbd and systemd-homed are two distinct things. Do not mix
> them up.
I understand.
I meant to point out that systemd-userdbd is the central for querying all users
and groups.
AND that systemd-homed exposes itself
I am extremely sorry if I am posting to the wrong mailing list, kindly point
that out to me if that's the case.
I'll be referring to /etc/{passwd,group,shadow,gshadow} as "legacy file bundle"
or "legacy bundle" or "legacy file(s)"
systemd-userdbd.service is a service included in systemd, which:
I am sorry to repeat it for the 3rd time,
But for a "stupidly minimal" stack, cage, weston etc... all exist with foot,
weston-terminal, etc...
You will be solved of many problems small and big, once the *only* stack is the
wayland stack (maybe different protocols, but the same libraries).
All c
Sorry for poking in, but why have kmscon, a complete re-implementation, run
over then DRM when a generic and well-tested combination of a wayland
compositor and a terminal emulator, like cage+foot, do the work just as well?
Yes, setup is initially difficult. But it might be worth it.
An addition
I would like to be a package maintainer for fedora.
Plz reply and ask for whatever other info you need.
https://bugzilla.redhat.com/show_bug.cgi?id=2350109
My review request
https://copr.fedorainfracloud.org/coprs/pramodvu1502/systemd-cron/
My copr
https://github.com/systemd-cron/systemd-cron
Up
