I'm looking into this. Below are some collected md5sums on isolinux.bin that I have in various places. I checked the sha256sums on the netinstall isos and they are correct. Both were downloaded today.  I don't know why i386 and amd64 made at or around the same day are different. The isolinux package is not arch-specific.

ascii-backports (2019-02-06  ~bpo9+2)
ea5013e737ba5ea49161a2b646312276  usr/lib/ISOLINUX/isolinux.bin

ascii (current 3:6.03+dfsg-14.1+deb9u1)
81d876d6234d3ca002390e7cb361bb61  /usr/lib/ISOLINUX/isolinux.bin

ascii (isolinux_3%3a6.03+dfsg-14.1_all.deb)
3e58f3f1a85d430556259f27f3b36d1a  usr/lib/ISOLINUX/isolinux.bin

i386 2.1 netinstall iso
3b36f20bc14cf4ad0f046962c4414221  mnt/isolinux/isolinux.bin

amd64 2.1 netinstall iso
bdad948d65c1dea713e1698d04a4e75d  mnt/isolinux/isolinux.bin

amd64 2.1 desktop-live iso (September 20)
bb8555ec5b6af5bebac5bfc08f88a543  mnt/isolinux/isolinux.bin

i386 2.1 desktop-live iso (September 20)
f03d6ecc57dad4524a0cab76b7afab41  mnt/isolinux/isolinux.bin

in live-sdk, possibly beowulf  (Oct 18)
caaa9f76d534f8c710c78cef00388ed1  /home/phred/my-live-sdk/live-sdk/extra/syslinux/isolinux.bin
caaa9f76d534f8c710c78cef00388ed1  /home/phred/my-live-sdk/live-sdk/tmp/devuan-i386-build/binary/isolinux/isolinux.bin

beowulf
5424e654f2bb81acfb7726631a3a0c1b  /usr/lib/ISOLINUX/isolinux.bin

refractasnapshot-base  (this one is old)
a45f9b17d309273e3efa588611141b43

jessie
35c69b13a8771b012d6e86b323827d78  /usr/lib/ISOLINUX/isolinux.bin

wheezy
6b8de496c485f2a82ca5f51eb59887fd  /usr/lib/syslinux/isolinux.bin

Well, I wasn't thinking of that, but I'm worried about the linux foundation anyway...
https://blog.cleancoder.com/uncle-bob/2 … ation.html

I don't trust them, and I assume that they're up to something. That said, I would expect most if not all devs have a local copy of their git repos. As long as that's the case, MS could burn github to the ground and it would be a minor inconvenience to move stuff to another location.

MS can control who has access to github or not, but if they want to dictate who can contribute to a project, they'll need to fork that project and maintain it themselves. I'd be more worried about which projects MS contributes to.

Yes, you still get Recommends by default.

You're right. The openrc package is not in the CD or DVD. It will only be installed if you selected a mirrorl.

You can still switch to openrc if you have an internet connection. Make sure sources.list points to devuan repos and install openrc. (See https://devuan.org/get-devuan for examples.)

Mine is greyed out in the list, too, and I still have a notification area in the panel. If you see a wicd (network) icon in the panel when the desktop starts, it's in the notification area. If I point the mouse at the correct stop, I can right-click and get the Properties box for the Notification area.

If I remove the notification area, it's no longer greyed out in the list, and I can add it to the panel. Apparently, you can only have one.

Nixer's method still works. I just tried it today on a buster standard-system (no X).

First time, I rebooted before trying to install eudev, and I got the long hang on dbus.
Second time, I instlalled eudev before the reboot, the install failed, I rebooted and did not get the delay. I then installed eudev again, and it succeeded.

On both installs, when I tried to install elogind and libelogind0 it wants to install a bunch of desktop apps. I haven't figured out why that is.

Short version:
- boot buster, install sysvinit-core
- download and install devuan-keyring
- change sources to devuan, update, upgrade
- (optional) install eudev and let it fail. This might save some time on the first reboot.
- reboot and install eudev, remove or purge systemd if it doesn't get removed automatically. (possibly libnss-systemd also)
- (optional) install libelogind0 if you want to replace libsystemd0. Without elogind, it's not pulling in the desktop apps.

Sorry I didn't respond sooner. I passed the message along and we're working on it. Package dependencies will be adjusted to fix this.

You can run reportbug to get a report, but you need to submit the bug by email. For cryptsetup, you'd need to send it to debian's bug list, but I wouldn't bother. They aren't going to fix it. From the bug report you cited:

There are no devuan cryptsetup devs to shame.

I did get someone else to look at this, and we will probably make a package that replaces the functions file similar to the one that mx/antix uses.

Jessie was two years late. Ascii was one year late. If the trend continues, beowulf will be six months late.

We've gained more devs than we've lost in the past year, and we've had collaboration between debian and devuan devs. We are very much alive.

I get a notification icon in lxpanel. I can't tell what it is - maybe a bell - it's light on lighter background. If I use dialog-warning, then I get the warning icon, which is easy to recognize. It just works. I don't know why. The only new process that shows up is the yad command. Using this iso: https://get.refracta.org/files/experime … -04-16.iso

UPDATE: If I run the same command on my ascii/xfce with dbus, I get the icon in the systray and no additional instances of dbus in ps output. If I run strace on that command, the string 'dbus' does not appear in the output.