Login
You're viewing the techdon.dev public feed.

Replies

  • Jun 11, 2025, 9:44 AM

    @AdrianVovk "So what should distros without systemd do?
    First, consider using GNOME with systemd."

    Alpine Linux can not do that because
    systemd explicitly does not support musl, and they have been pretty clear that they never will.

    So the only options we have are re-implementing systemd, or re-implementing glibc. Not only the public APIs but also the internals.

    Very frustrating.

    💬 0🔄 0⭐ 0
  • 💬 2🔄 0⭐ 0
  • Jun 11, 2025, 10:17 AM

    @Foxboron @AdrianVovk I would also like to point out that Adelie Linux devs have been doing impressive work trying to make musl work in upstream systemd.

    The difficulties are not the technical ones.

    💬 1🔄 0⭐ 0
  • Jun 11, 2025, 3:11 PM

    @ncopa @Foxboron @AdrianVovk not just them, but also openembedded folks and people from postmarketOS

    We have a plan, coordination seems to be up in the air though since these three projects aren't communicating.

    There WILL be a shim library for musl in upstream systemd and there WILL be CI jobs validating systemd against musl in upstream systemd.

    It's just a matter of time, but once this is all in place I expect interest to grow and it will be maintained.

    postmarketOS is fully invested in it at this point and I see no reason why we couldn't allocate funding to this effort in the future.

    💬 0🔄 0⭐ 0
  • Jun 11, 2025, 9:41 PM

    @cas @ncopa @Foxboron @AdrianVovk FWIW regarding funding. There are 3000€ on this year's budget for systemd upstreaming that I expect we're able to execute. I also expect it to grow for the next years too, since that's little money, just to get started :)

    💬 0🔄 0⭐ 0
  • dunklecatdunklecat@mas.to
    Jun 11, 2025, 4:49 PM

    @AdrianVovk So you're going to lock everything in a single product. No more GNOME DE, just linux/systemd/gnome/flatpak (GNOME OS) or nothing. What a shame to see open source software locking itself this way.

    💬 0🔄 0⭐ 0
  • Jun 17, 2025, 12:43 AM

    @dunklecat @AdrianVovk we need defined framework and APIs in order to provide a reliable DE and secure environment.

    The actors and demons actually doing the job can change, but it's important to define clearly the ecosystem we expect, otherwise it's impossible to target gnome as a platform.

    💬 0🔄 0⭐ 0
  • Jun 11, 2025, 9:47 PM

    @AdrianVovk Why have a hard dependency for features basically nobody wants or needs? Multi-seat/multi-graphical-session on same host, much less with same user at each seat, it an utterly wonky special case only the most nerdy possible users would even think of. Just make it so folks can turn off support for whatever breaks without systemd dynamically creating fake ghost users as a hack to make that work.

    💬 1🔄 0⭐ 0
  • Jun 12, 2025, 12:35 AM

    @dalias @AdrianVovk I can think of a use: logging in using one session with a new desktop environment to check it's configuration without having to log out of my old desktop environment first. But in that case I absolutely want the new session to be the same UID as the older one because I want to be the same user as far as the system's concerned, not someone else.

    💬 1🔄 0⭐ 0
  • Jun 12, 2025, 12:58 AM

    @tknarr @dalias the sessions are not running under different UIDs. Once you log in you're logged in as yourself. Only the login screen runs as different UIDs

    💬 0🔄 0⭐ 0
  • Jun 12, 2025, 1:09 AM

    @AdrianVovk @tknarr OK, that wasn't clear til now. So basically this is a privsep login screen that's running as an ephemeral user not associated with the actual user logging in, so that it doesn't need to be running as root? And you want them to be different users per login screen so that popping one wouldn't allow attacks on another?

    💬 0🔄 0⭐ 0
  • Jun 12, 2025, 1:10 AM

    @AdrianVovk @tknarr If my understanding is correct, that's completely reasonable, but it should work with static assignment of these UIDs if that's what someone wants, and for the vast vast vast majority of users, there's only a single one (because again, normal people have a single seat, they're not running 1990s style uni thin-client labs or anything).

    💬 0🔄 0⭐ 0
  • Jun 12, 2025, 2:41 AM

    @dalias @tknarr Indeed. That is the workaround I implemented for non-systemd distros, as explained in the blog post. And, again as I explained in the post, the workaround will remain until another unrelated component (accountsservice) is replaced with userdb for unrelated reasons (because it provides us with rich user records, unlike /etc/passwd)

    💬 0🔄 0⭐ 0
  • Jun 12, 2025, 2:55 AM

    @AdrianVovk @tknarr That overall sounds good. Does that mean it's expected to break at some point in the future? Or will you keep support for passwd/shadow for systems that don't want to or can't use the systemd-style accountservice?

    💬 0🔄 0⭐ 0
  • Jun 12, 2025, 3:25 AM

    @dalias @tknarr Yeah it's expected to break at some point in the future, because userdb will be required by accountsservice/its replacement

    userdb isn't incompatible with /etc/passwd or shadow in any way (in fact, to implement it right you're supposed to integrate it with shadow if you have it). It should be possible to implement on any Unix system, I don't think there's anything Linux specific about it (but I'm no expert in non-Linux Unixes)

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Jun 12, 2025, 3:38 AM

    @dalias @tknarr For one, /etc/passwd doesn't have any form of rich information about the user. No profile pictures, no ability to export any kind of user settings to the login screen, etc. It barely has the ability to store a display name (which is actually "GECOS" instead, which is... complicated for historical reasons). userdb is json, so we can add new stuff to it whenever we want instead of going in and implementing weird side databases (which is how shadow and accountsservice happened, btw)

    💬 1🔄 0⭐ 0
  • Jun 12, 2025, 11:34 AM

    @AdrianVovk @dalias Why would that be in a system database though? There's a long-standing convention of storing that under the user's account, usually in dot-files in the user's home directory, .plan and .project for example. .userphoto would be an easy addition. GECOS isn't that complex, it's just a comma-separated list of items and the display name is the first one so trivial to parse out.

    💬 0🔄 0⭐ 0
  • Jun 12, 2025, 11:35 AM

    @AdrianVovk @dalias I can see a use case for userdb only if you want to have a central database of users but don't want to use one of the existing systems like Active Directory or Kerberos+LDAP.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0