The reactions to systemd-homed have predictably been, "soon there's going to be a word processor in #systemd", without these people realizing that:

1.) systemd is NOT a single binary, it's a project, an ecosystem of utilities. That's like saying to GNU; Why is there wget? I want GNU to compile stuff with GCC, why is GNU nano a thing?

Of course the goal of the GNU Project is to produce everything needed to have a libre OS - the goal of systemd is to produce everything needed to manage this OS.

systemd is not an init system, it's a system manager designed to be useful way beyond simply bringing the system up.

2.) Linux home directory handling is currently a mess. Any random app can ignore XDG conventions, making it hard to be sure that a simple rsync of home is sufficient i.e. it would be working as expected if you were forced to nuke your system. From my experience, it doesn't work particularly well for backing up the configs of many programs as they write to places like /etc

Show thread
Follow

@MatejLach just to clarify, the homed project doesn't seem to do anything about enforcing XDG conventions or improving the current situation. I think you shouldn't conflate the two.

@mariusor Well, it does seem to want to make it so that apps that don't have to wouldn't write all over the place. Initially this is primarily aimed at making home directories portable by apps not writing much outside of it. Strict XDG enforcement seems like the next logical step.

Sign in to participate in the conversation
\m/ Metalhead.club \m/

Metalhead.club is a Mastodon instance hosted in Germany and powered by 100% green energy.