3 ms·
On an MX Linux (non-systemd Debian-derived distro) box I ran ldd on /sbin/ssh and also ran: [EDIT: this string gives cleaner results:] lsof -w -P -T -p $(pg
by cf100clunk 3y ago
On an MX Linux (non-systemd Debian-derived distro) box I ran ldd on /sbin/ssh and also ran:
[EDIT: this string gives cleaner results:]
lsof -w -P -T -p $(pgrep sshd)|grep mem
and saw liblzma in the results of both, so there is some sort of similar trickery going on.
- capitainenemo 3y agoHuh. That's rather surprising. Do you know how MX Linux handles systemd? Devuan does that shimming of upstream. Do they perhaps just try to leave out certain packages? Anyway. I did not see lzma in the results on Devuan running a process check (just in case). I did see it on a Debian.
- cf100clunk 3y agoIt turns out MX uses a package called systemd-shim that seems to be the Debian one: $aptitude show systemd-shim Package: systemd-shim Version: 10-6 State: installed Automatically installed: no Priority: extra Section: admin Maintainer: Debian QA Group <packages@qa.debian.org> Architecture: amd64 Uncompressed Size: 82.9 k Depends: libc6 (>= 2.34), libglib2.0-0 (>= 2.39.4), cgmanager (>= 0.32) Suggests: pm-utils Conflicts: systemd-shim:i386 Breaks: systemd (< 209), systemd:i386 (< 209) Description: shim for systemd This package emulates the systemd function that are required to run the systemd helpers without using the init service