There's about 14 linux systems that don't use systemd and if memory serves those got an article on itsfoss.com. By the way neither slackware nor slint were first recognized among this number when the count was down at 11, but I sent a comment in that may have got published and caused an update. On Wed, 6 Apr 2022, Linux for blind general discussion wrote: > Hi Immo and All, > > Didier here. > > thanks for the heads-up, answer inline. > > Le 06/04/2022 ? 14:50, Linux for blind general discussion a ?crit : > > Hi All! > > > > Immo here. > > > > Sorry for my ignorance and disturbing the usual chatter on the list. > > > > I guess this is at least for Didier. There are also other speaking > > distros out there that systemd people might not be aware of so I > > forwarded the original message here. > > > > Feel free to answer to my message. I'll forward it to systemd-devel > > if needed. > > > > Well, Slint: > 1. is based on Slackware and uses the same layout, so I forward this answer to > its maintainer, Patrick J. Volkerding (he is not subscribed to this list as far > as I know). > 2. as Slackware, Slint does not uses systemd as its init system so far but > includes kind of a compatibility layer, mostly elogind. We also use eudev > instead of udev. > 3. As Slackware, Slint has an "unmerged-usr" layout so far, i.e. bin, sbin and > lib* are not symlinks to their counterparts under /usr. > > This being said I do not know which changes Patrick intends to do for the next > Slackware version on this respect but intend to follow suite with Slint. > > > Distribution maintainers might also want to join systemd-devel if > > not already there. > > What I fail to grasp is the possible consequences of this change for > distributions not using systemd as their init system. Any clue on that is > welcome. If understand well, as long as we do not change our layout we do not > need that our (custom made, not using dracut) initramfs implements the changes > mentioned in https://fedoraproject.org/wiki/Features/UsrMove > > Cheers, > Didier > -- > Didier Spaier > Slint maintainer > didier at slint dot fr > > > -------- Original Message -------- > > Subject: [systemd-devel] Dropping split-usr/unmerged-usr support > > Date: 2022-04-05 23:07 > > From: Luca Boccassi <luca.boccassi@xxxxxxxxx> > > To: systemd-devel@xxxxxxxxxxxxxxxxxxxxx > > > > Hi, > > > > As part of our spring cleaning effort, we are considering when to drop > > support for split/unmerged-usr filesystem layouts. > > > > A build-time warning was added last year: > > > > https://github.com/systemd/systemd/commit/9afd5e7b975e8051c011ff9c07c95e80bd954469 > > > > We are now adding a runtime taint as well. > > > > Which distributions are left running with systemd on a split/unmerged- > > usr system? > > > > (reminder: we refer to a system that boots without a populated /usr as > > split-usr, and a system where bin, sbin and lib* are not symlinks to > > their counterparts under /usr as unmerged-usr) > > > > _______________________________________________ > Blinux-list mailing list > Blinux-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/blinux-list > _______________________________________________ Blinux-list mailing list Blinux-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/blinux-list