Read the last post in the bug thread I linked. The fix has been merged. Package soon.

@fredbird67: I just tried extrepo to install xlibre, and it didn't work. The install command gave me an error message about an undefined subroutine. I also figured out that I probably need to run 'extrepo enable xlibre' and it added a file to /etc/apt/sources.list.d/ that points to the wrong (unmaintained) xlibre repository.

The correct way to get xlibre in devuan is to follow the instructions here, provided by NexusSfan:
https://xlibre-debian.github.io/

That way you'll get updates as more things get fixed.

I'm glad you got it installed. The netinstall iso gives you some software choices. The live install just gives you whatever is in the iso.

@Camtaf: The live installer does not need internet to work and does not download anything. If you notice that something is missing for it to work, let me know and I'll add it to the next build.

Sometimes the bootloader doesn't install correctly. If you know how to chroot, you could boot the live, chroot into the installed system and install grub and then run update-grub to get a boot menu. I left a few steps out of this.

Easier method might be to get the netinstall iso, boot into Rescue mode from the boot menu, and reinstall the bootloader. Those are all menu choices.

For more detailed instructions, we need to know if you're booting uefi or legacy bios (CSM) and whether or not you have a separate partition for /boot.

This is what I have for programs with logind in the name after a recent upgrade to excalibur. Make sure you have all of these.

$ dpkg -l | grep logind
ii  elogind                                   255.17-2                                     amd64        user, seat and session management daemon
ii  libelogind-compat:amd64                   255.17-2                                     amd64        user, seat and session management library compatibility
ii  libelogind0:amd64                         255.17-2                                     amd64        user, seat and session management library
ii  libpam-elogind:amd64                      255.17-2                                     amd64        elogind PAM module
ii  libpolkit-gobject-elogind-1-0:amd64       126-2devuan1+excalibur1                      amd64        polkit Authorization API

seatd support was added to xlibre a few months ago. I made a freia test live iso with seatd and without elogind or consolekit. Also there's no display manager. Use 'startx' to get a graphical session.
https://get.refracta.org/files/experime … 4_1517.iso
login: user, password: user
root password is root

Here's the full list for autofs. I've only ever used stop|start|restart. :

# service autofs
Usage: /etc/init.d/autofs {start|forcestart|stop|restart|forcerestart|reload|force-reload|status}

There might be commands on the other end, depending on what you're automounting. (e.g. commands for samba or nfs)

You shouldn't need to set the defaults with update-rc.d unless you changed them.

Any packages that require systemd should not show up in our repo. If you run into one, let us know about it.

If you want the missing packages, you need to add non-free-firmware to sources.list and then 'apt update'. You probably don't need firmware-intel-misc, but the -graphics package has firmware for i915. I don't know if it will make it work better.

deb http://deb.devuan.org/merged freia main non-free-firmware

After reading your post I realized that I don't have an excalibur install with a separate /boot partition, but I do have a couple of daedalus installs with boot partitions that are 500M or smaller. I'm not ready to upgrade those, so I did a test in a VM. Results below:

200M /boot was too small. I'm not sure why it failed to boot and dropped me to initramfs prompt. I rebooted with a live iso, went into chroot to reinstall grub, update-grub and then run 'update-initramfs -u -k all'. It ran out of disk space and failed.

360M /boot works. I don't recommend using such a small size, but only because we're getting so many kernel upgrades lately, it's easy to accumulate too many to fit. (I think 300M will hold three kernels)

Disk /dev/sda: 8 GiB, 8589934592 bytes, 16777216 sectors
Disk model: QEMU HARDDISK   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x460d0caf

Device     Boot  Start      End  Sectors  Size Id Type
/dev/sda1         2048   739327   737280  360M 83 Linux
/dev/sda2       739328 16777215 16037888  7.6G 83 Linux

Disk /dev/mapper/root_fs: 7.63 GiB, 8194621440 bytes, 16005120 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Filesystem           Size  Used Avail Use% Mounted on
/dev/mapper/root_fs  7.5G  4.2G  3.0G  59% /
/dev/sda1            328M   65M  242M  21% /boot

Note: The list of banned packages is not the same as the list of forked packages, and there is no intersection of those lists. We fork packages to remove unnecessary dependency on systemd. We ban packages that can't be forked (things that are necessarily dependent on systemd). For example - systemd itself is banned, not forked.

Since user services seem to be in vogue, I'll mention that runit can be used to supervise user services. You can do this without using runit for the init system.
Here's a howto: https://troubleshooters.com/linux/init/ … _runit.htm

I get the same result when I use your command. Remove the '-nic user,model=virtio' and it works.

Note: I did not include the '-drive file=...' part in my test, so I don't know if that would also need to be changed. I use raw disk images and don't use virtio. e.g.  -drive file=${image_file},format=raw