Have you done

apt-get update

.. or whatever the corresponding button presses are on the gui tool?

Have you done

apt-get upgrade

.. or whatever the corresponding button presses are on the gui tool?

Have you done

apt-get dist-upgrade

  .. or whatever the corresponding button presses are on the gui tool?

Thoe are the three steps to follow after having changed sources.list.

I thought I just did Yes, go ahead.. see post #40

All the installer ISO have the same installer software and they only differ in which collections of packages they come with; the so called package pool. They work by installing that which you select, and then those selections expands by having dependencies. If you install with network mirror backing, they will all link up with the Devuan repository and they will all have all packages available.

The leanest system you can get from them is their base system where you opt for not installing anything else. That gives you a Linux operating system without all things you may expect, and in particular without graphical desktop environment. That's generally known as a "server system" although even a functional server would typically include some additional services such as perhaps ssh and web service.

The cinnamon desktop is generally understood to be "defined" by the task-cinnamon-desktop package, which is a content free-package that only depends on the collection detail packages that would make up a "cinnamon desktop". The "desktop" ISO contains all those packages, as do the collective of server+cd2+cd3+cd4 ISOs (both having also other packages that are outside of the task-cinnamon-desktop collection).

At a more general level, Devuan (like Debian) is like a warehouse of packages rather than an end-user "distribution", and it's up to the end-user to choose which subset of packages they will want to use. The installer offers some pre-packaged choices of end-user-like desktop collections, but that is supposed to be for convenience; in particular someone new to it may otherwise struggle a fair bit to pull together their best convenience package collection.

Nah. If you want to spout that shit you'll have to go elsewhere.

@Gregors, if you make a theme and email to me I can probably stuff it in as an option.

I'm not sure there is a bug report, but that particular issue of having multiple Xorg (in different VT) with seatd, is currently being worked on, and I believe an update is coming fairly soon.

yes, ascii has been moved. You should update your sources list to these

deb http://archive.devuan.org/merged ascii main
deb http://archive.devuan.org/merged ascii-backports main
deb http://archive.devuan.org/merged ascii-proposed-updates main 
deb http://archive.devuan.org/merged ascii-security main

(add contrib and non-free as desired)

@m1k3: slightly off topic, but I think you'd enjoy learning https://transfer.sh

@fsmithred: is it possible for you to convert the iso into a vdi format, then attach that as second disk

That should be booraable with legacy bios.. using the isolinux mastering of its mbr, or possibly by finding the second partition's legacy equipment (via chain loading).

@marma-lade, the next time you upgrade from 4.0 to 5.0, remember to add the new section named non-free-firmware which was added in Debian for some reason, and thus is added the same in Devuan.

That section is in addition to the "old" non-free in Devuan 5.0 and probably onwards; it doesn't exist for versions 4.0 and newer. It is a new repository section that appears to contain all firmware that previously were in non-free.

If you don't add that section, your upgraded system will not be able to find and install required firmware.

https://www.devuan.org/os/documentation … o-daedalus

When configuring for upgrade, did you include the new section non-free-firmware (whihc is in addition to non-free) ?

@tauro. It's hard to guess why your boot attempts on bare-metal fail. Especially the UEFI boots should be fine, unless perhaps it requires "secure boot".

Your BIOS boot might be confused by seeing the ISO partition as bootable.

You might change that by a) copy the ISO to a new file, say x.iso, and b) run

sfdisk -A x.iso 2

That will change the ISO to flag the EFI partition, which is a FAT filesystem, as bootable, and your BIOS might then discover the syslinux boot equipment in that filesystem.