One more...   I dd'd a desktop installer iso to the second partition. It finds the cdrom and unlike the netinstall iso it offers to set up wlan0 in addition to the non-functional eth0 on the laptop. A bonus for those without ethernet ports.

Also, the destkop installer iso does copy correctly to the first (fat32) partition if you use the ISO_1 option, because it unpacks the iso file and no single file is bigger than 4GB. But you still have to mount it manually.

It should have been obvious to me that the desktop installer iso is bigger than the 4GB size limit of fat32 filesystems. There's a way around that - put the iso on a second partition that's formatted as ext. I used ext4 for my test.

For a live-iso, use ISO_2 from the refracta2usb menu. That will use the findiso option. When it copies the iso, it will not copy the whole thing and might even fail. You can delete that copy of the iso.

Copy the (good) iso to a directory on the second partition that's named the same as the directory just made on the first partition.

Boot menu entries should look something like this.

label big-iso
    menu label big-iso
    kernel /big-iso/vmlinuz
    append initrd=/big-iso/initrd.img boot=live findiso=/big-iso/my_big_live.iso

menuentry "big-iso " {
    set gfxpayload=keep
    linux /big-iso/vmlinuz boot=live findiso=/big-iso/my_big_live.iso
    initrd /big-iso/initrd.img
}

For an installer iso, you can leave out the "boot=live findiso=<whatever>"
The installer will start and will fail when it tries to find the cdrom
Drop to a shell and mount it manually.

mount -t ext4 /dev/sdb2 /mnt
mount -oloop,ro /mnt/big-installer-iso/devuan_<whatever>.iso /cdrom
exit

And let the installer find the installation media.

Wow, that works. I didn't change anything in the existing setup, but I did dd the iso to the second partition. Same boot menu entry works and it made it past the point where it detects the installation media.

bai4Iej2need,

I think we're using the wrong terminal. I just tried it with xterm and it works. Does not matter if I use startx for openbox or openbox-session or if I use lightdm to start a full xfce destkop. Wall is happy to talk to xterm but does not work with xfce-terminal or qterminal. I didn't try any others.

I often see packages in the autoremove list that I want to keep. Almost always, they are just remnants of old versions that can be removed. Take note of what's there, and if it really removes what you want to keep, reinstall those packages.

Your cpu is not too new for the kernels in excalibur. I couldn't find a clear answer on the graphics card.
Exactly how did you prepare the usb stick?

You could try the iso in the thread that ovi linked or try the desktop-live iso to see if that boots correctly.

New hardware can be a problem if it's too new for the kernel. Which model cpu, motherboard and graphics card do you have? You might need to use a kernel from excalibur-backports.

I can do it this way, but I don't know if it has what you need.
https://dev1galaxy.org/viewtopic.php?id=7084

https://imgur.com/a/vszdXo5

Looks like you need to install libreoffice-gnome and do not exclude Recommends to get libreoffice-gtk3 automatically.

In devuan, /var/lib/dbus/machine-id gets replaced on every boot and /etc/machine-id does not exist. (It might be there if you migrated a debian install to devuan, but I'm not certain of that.) See /etc/default/dbus to turn that on or off.

You're not removing the files in your home directory (in ~/.dbus/session-bus/*) and neither does the default devuan installation.  See https://dev1galaxy.org/viewtopic.php?pid=58117#p58117

I just have a single line in /etc/rc.local to remove the ones in my home so they get removed before I log in, and then a new one is created matching the one in /var/lib/dbus.

man xsession says:

       $HOME/.xsession
              is  a  sequence  of commands invoking X clients (or a session manager such as xsm(1)).  See the manual page
              for xinit for tips on writing an .xsession file.

This page talks about the security risks of 'xhost +':
https://www.debian.org/doc/manuals/secu … 04.en.html

daedalus-security is fixed.

Components: main contrib non-free non-free-firmware