Hi,

Hendrik Boom <hendrik@???> writes:

> On Thu, Oct 09, 2025 at 08:44:09PM +0900, Olaf Meeuwissen via Dng wrote:
>> Hi,
>>
>> golinux via Dng <dng@???> writes:
> ...
>> >
>> > If you would like to be crowned the "Devuan Systemd Janitor" and take
>> > on removing all those useless files, please contact the Devuan Dev
>> > Team on our development channels.
>>
>> For a Devuan Systemd Janitor on steroids, you could use dpkg's
>> path-exclude option.
>>
>> echo "path-exclude=*systemd*" > /etc/dpkg/dpkg.cfg.d/exclude-systemd.cfg
>> find / -name '*systemd*' -delete
>
> Isn't there a library with 'systemd' in its name that is there
> just so that other packages that are systemd-capable have
> somewhere to link to so they can run discoer there's no
> systemd here, and work fiin without?

You mean libsystemd, I guess. Yeah, you might need that.

> I might be important no to deete this one.

Like I said,

>> The dpkg manual page warns about the option and advises to use it with
>> caution so if that breaks your system, you get to keep the pieces.

But my main suggestion was that you can use dpkg's path-exclude
mechanism to keep systemd "cruft" off your system if it bothers
you enough to go that distance.

Something like

cat<<EOF > /etc/dpkg/dpkg.cfg.d/exclude-systemd.cfg
/etc/systemd/*
/lib/systemd/*
/usr/lib/systemd/*
/var/lib/systemd/*
EOF

and removing the content in those directories *looks* quite OK on
*my* laptop (running Daedalus). No, I didn't test that.

Use

sudo find / -type d -name '*systemd*'
sudo find / ! -type d -name '*systemd*'

for lists of directories and non-directories to get an idea what
you might want to zap. Check the content of the directories with
something like

sudo find / -type d -name '*systemd*' | xargs find

Use dpkg's path-include to keep things that would otherwise be removed
by a path-exclude (similar to git ignore's !).

Hope that clarifies,
--
Olaf Meeuwissen