Click on "continue to image" to see the image

It displays the memory used for each process running, which can be very useful.

@OP: why not just post the text rather than an image of text?

Like this:

 Private  +   Shared  =  RAM used       Program

216.0 KiB +  71.5 KiB = 287.5 KiB       startx
284.0 KiB + 117.5 KiB = 401.5 KiB       init
312.0 KiB + 147.5 KiB = 459.5 KiB       cron
260.0 KiB + 222.5 KiB = 482.5 KiB       xinit
284.0 KiB + 240.5 KiB = 524.5 KiB       slstatus
364.0 KiB + 186.5 KiB = 550.5 KiB       dbus-launch
616.0 KiB + 134.5 KiB = 750.5 KiB       loksh
580.0 KiB + 671.5 KiB =   1.2 MiB       getty (5)
600.0 KiB + 698.0 KiB =   1.3 MiB       dbus-daemon (2)
  1.0 MiB + 339.5 KiB =   1.4 MiB       login
  1.1 MiB + 433.5 KiB =   1.5 MiB       sudo
  1.7 MiB + 107.5 KiB =   1.8 MiB       elogind-daemon
  1.7 MiB + 186.5 KiB =   1.9 MiB       rsyslogd
  1.3 MiB +   1.3 MiB =   2.6 MiB       dwm
  2.8 MiB + 216.5 KiB =   3.0 MiB       udevd
  3.7 MiB +   1.4 MiB =   5.1 MiB       xterm
 42.5 MiB + 816.5 KiB =  43.3 MiB       Xorg
---------------------------------
                         66.5 MiB
=================================

I win

v60.7.2 of firefox-esr has just been made available in the Devuan ceres repositories:

https://pkginfo.devuan.org/stage/ceres/ … esr-1.html

I presume it will filter down to the other branches soon.

Which filesystem is Devuan installed on?

Do you have the appropriate filesystem tools package installed in the system from which you are trying to mount the Devuan partition?

Have you tried fsck?

It may be best to boot the Devuan ASCII minimal-live.iso image to ensure compatibility:

https://mirror.leaseweb.com/devuan/devu … imal-live/

Why do you care if your ISP can see which packages you are downloading?

Try

wget https://deb.debian.org/debian-security/pool/updates/main/f/firefox-esr/firefox-esr_60.7.1esr-1~deb9u1_amd64.deb
# dpkg -i firefox-esr_60.7.1esr-1~deb9u1_amd64.deb

It should be fine to use the openSUSE Build Service to host Devuan stuff using their Debian VMs, the distributions are binary compatible. It has options for testing/unstable repositories now.

Just be careful about systemd dependencies

The OBS supports Fedora & CentOS as well btw.

Unfortunately sysvinit does not offer true process supervision and so is incapable of keeping track of running services.

Try OpenRC instead, that does offer process supervision.

List running services and their status with

rc-status

Display all available services with

rc-update -v show

No, not at all.

From the official Debian site:

https://backports.debian.org/

And because backports are drawn from testing they are also subject to the same 10-14 day transition delay from sid and are not covered by the Security Team so you may be exposing your system to serious vulnerabilities.

The elogind package was created by the Devuan developers and adopted by Debian.

Thanks Devuan!

It might be worth submitting a bug report to Debian against the buster dbus package complaining that it depends solely on libsystemd0 when it should have libelogind0 as an alternative dependency.

Or tell the init-diversity mailing list and see what they say about it:

http://www.chiark.greenend.org.uk/mailm … -diversity

FWIW I had beowulf running dbus-free under OpenRC, it was lovely

The shim is dead and buried but sysvinit-core is alive & well and receiving updates in Debian:

https://packages.debian.org/experimental/sysvinit-core

The Debian developers have adopted the Devuan elogind package to keep init diversity, as your link explains.

https://packages.debian.org/buster/elogind

I'm sure they would welcome any donations

Well make one then:

cp /etc/conky/conky.conf ~/.conkyrc && editor ~/.conkyrc

Ooops, sorry, that's a dummy package.

Try

# apt reinstall conky-std # or conky-cli or conky-all if you have those version instead

If things still won't work then try deleting ~/.Xauthority and if that doesn't fix it then check for root-owned files in $HOME:

find ~ -user root

Sorry OP, I'm not prepared to help you add MX sources because I don't think it's a good idea.

I also don't think wine-staging will behave any differently.