On Mo, 18.09.23 17:47, Nils Kattenbeck (nilskemail@xxxxxxxxx) wrote: > Hi, > > /usr/lib/systemd/ is indeed the place for internal binaries with > > unstable interfaces. But it's also the place where we put binaries > > that we don't typically expect users to call, because they are > > generally called via some well define .service unit or so only. > > > > systemd-cryptsetup is one of the latter, we'd expect people to use > > this via crypttab mostly. However, the interface is nonetheless > > stable, it is a long-time part of systemd and so far we never broke > > interface and I see no reason we ever would. In fact it might be a > > candidate to move over to /usr/bin to make official, if there's > > sufficient request for that. (such a request should be made via github > > issue tracker) > > > > Why was the decision taken to put these into /usr/lib/systemd instead of > /usr/libexec/systemd/? That's a Fedoraism. Why would one put something there? /usr/lib/ is where private arch-dependent package stuff goes. What's the rationale for /usr/libexec/ though? Lennart -- Lennart Poettering, Berlin