Here's a live-iso I made today. It's a proof-of-concept, experimental, unofficial, and it looks like it works just fine.
Beowulf, LXDE, it has both lxdm and lightdm with lxdm the active display manager. I forgot to remove lightdm. To change the default, run dpkg-reconfigure lightdm

There's not much more than what comes with lxde. Just a few apps. No gimp or libreoffice.

https://get.refracta.org/files/experime … 2_0818.iso

Login: Password
user:user
root:root

sha256sum:
6d4247852ea41865b0f1977ea88f8399f6ddab4b55c91da079ce1536c443b859  snapshot_beowulf_lxde_amd64-20210312_0818.iso

I've never used ventoy, so I'm not sure how it arranges things. If it lets you boot live-isos that are on the usb, then I would guess that the first thing you'd see would be the refractasnapshot boot menu, which is just an isolinux boot menu. It lists several different boot options. It does not list any install options. So I'm not sure where you were.

It's an isohybrid image, so you could directly image a spare usb stick with it and boot the live system.

The iso you made with refractasnapshot should be an exact copy of the system that made it, with a few things excluded so it will boot properly and also to remove some private stuff. And you should be able to install it from a live-usb or live-cd/dvd.

And yes, it should work the first time without knowing what you're doing, as long as you don't ask it to copy your whole music and video collection. If you look under the hood, you can modify it to do things differently.

If you mean the subdirectories in your home for MUSIC PICTURES and whatever else, that would be xdg-user-dirs and xdg-utils. If those are installed, look in /etc/xdg/ if you want to edit the configs. There are a few xdg- commands, too. You might be interested in xdg-user-dirs-update.

If you mean /home/<username> does not exist, then you somehow failed to create a user during the installation. You would have had to say no when asked if you wanted to create a user. In an already-installed system, the adduser command does all the things you need to create a user. You can change those defaults in /etc/adduser.conf.

I added a few more services to runit using the three-step procedure I posted above.
- copy the sample files to /etc/sv/
- stop the service with  /etc/init.d/<service> stop
- add the service with  update-service --add /etc/sv/<service>

Added dbus, elogind, lightdm and all seems to be working.

# sv status /etc/sv/*
run: /etc/sv/acpid: (pid 1894) 1238s; run: log: (pid 1891) 1238s
down: /etc/sv/anacron: 1238s, normally up; run: log: (pid 1895) 1238s
run: /etc/sv/cron: (pid 1874) 1238s; run: log: (pid 1872) 1238s
run: /etc/sv/dbus: (pid 1885) 1238s; run: log: (pid 1884) 1238s
run: /etc/sv/elogind: (pid 1886) 1238s; run: log: (pid 1883) 1238s
run: /etc/sv/getty-tty1: (pid 1873) 1238s
run: /etc/sv/getty-tty2: (pid 1852) 1238s
run: /etc/sv/getty-tty3: (pid 1855) 1238s
run: /etc/sv/getty-tty4: (pid 1853) 1238s
run: /etc/sv/getty-tty5: (pid 1876) 1238s
run: /etc/sv/getty-tty6: (pid 1869) 1238s
warning: /etc/sv/getty-ttyS0: unable to open supervise/ok: file does not exist
run: /etc/sv/lightdm: (pid 1878) 1238s; run: log: (pid 1877) 1238s
run: /etc/sv/mdadm: (pid 1901) 1238s; run: log: (pid 1900) 1238s
run: /etc/sv/network-manager: (pid 1871) 1238s; run: log: (pid 1870) 1238s
run: /etc/sv/ssh: (pid 1899) 1238s; run: log: (pid 1898) 1238s

Edit: fixed typo. Thanks.

I'm not sure if I got the logging right. NetworkManager is working, but puts very little in the runit logs and puts more in syslog. It was spamming the syslog with everything it did until I added --log-level=ERR to the start command.

Also, mdadm gives an error (-1) when it stops. But it seems to be running. I don't have any raid array to test it right now.

pstree:

      ├─runsvdir─┬─6*[runsv───getty]
      │          ├─runsv─┬─acpid
      │          │       └─svlogd
      │          ├─runsv─┬─NetworkManager───2*[{NetworkManager}]
      │          │       └─svlogd
      │          ├─runsv─┬─sshd
      │          │       └─svlogd
      │          ├─runsv─┬─cron
      │          │       └─logger
      │          ├─runsv─┬─mdadm
      │          │       └─svlogd
      │          ├─runsv─┬─haveged
      │          │       └─svlogd
      │          └─runsv───svlogd

NetworkManager messages in syslog:
# on stopping network-manager:

Feb 28 02:25:08 chimaera-2 dbus-daemon[1506]: [system] Activating service name='org.freedesktop.nm_dispatcher' requested by ':1.35' (uid=0 pid=2919 comm="/usr/sbin/NetworkManager --no-daemon --log-level=E") (using servicehelper)
Feb 28 02:25:08 chimaera-2 dbus-daemon[1506]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

# on starting network-manager

Feb 28 02:26:50 chimaera-2 dbus-daemon[1506]: [system] Activating service name='org.freedesktop.nm_dispatcher' requested by ':1.38' (uid=0 pid=3006 comm="/usr/sbin/NetworkManager --no-daemon --log-level=E") (using servicehelper)
Feb 28 02:26:50 chimaera-2 dbus-daemon[1506]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

network-manager runit log on exit:

2021-02-28_02:25:09.02206 invoke-run: network-manager : run exit code is 0
2021-02-28_02:25:09.02209 invoke-run: network-manager stopped

mdadm runit log error on exit:

2021-02-28_01:26:40.87497 invoke-run: ERROR -1 in mdadm: runscript didn't exit normally
2021-02-28_01:26:40.87504 invoke-run: mdadm : run exit code is -1
2021-02-28_01:26:40.87505 invoke-run: mdadm stopped

network-manager/log/run

#!/bin/sh
set -e

NAME=network-manager
LOG="/var/log/runit/$NAME"

test -d "$LOG" || mkdir "$LOG" && chown -R _runit-log:adm "$LOG"
exec chpst -u _runit-log svlogd -tt "$LOG"

mdadm/log/run

#!/bin/sh

NAME=mdadm
LOG="/var/log/runit/$NAME"

test -d "$LOG" || mkdir "$LOG" && chown -R _runit-log:adm "$LOG"
exec chpst -u _runit-log svlogd -tt "$LOG"

Lorenzo, thanks for helping us with this and thanks for doing it.

Tested. And it does work just as it is. I haven't tried dbus yet.

1. /etc/init.d/network-manager stop
2.  copy files into /etc/sv/network-manager
3. update-service --add network-manager
4. (maybe)  sv start network-manager    Not sure if you need to do this. I started/stopped and check status a bunch of times until I was able to get the logging out of the syslog.

Here are the files I used:

network-manager/run

#!/bin/sh -e
## uncomment the following if you have dbus as runit service
#sv start dbus && sv check dbus || exit 1
exec 2>&1
exec /usr/sbin/NetworkManager --no-daemon

network-manager/log/run

#!/bin/sh
set -e

NAME=network-manager
LOG="/var/log/runit/$NAME"

test -d "$LOG" || mkdir "$LOG" && chown -R _runit-log:adm "$LOG"
exec chpst -u _runit-log svlogd -tt "$LOG"

network-manager/finish

#!/bin/sh
set -e

. /lib/runit/finish-default "$@"

I also set up mdadm with runit. I used the same procedure as above with the sample runscripts but had to change the last line in mdadm/log/run from a hard-coded log file to "$LOG". That file looks like this now:

#!/bin/sh

NAME=mdadm
LOG="/var/log/runit/$NAME"

test -d "$LOG" || mkdir "$LOG" && chown -R _runit-log:adm "$LOG"
exec chpst -u _runit-log svlogd -tt "$LOG"

If you want gpt with legacy bios boot, you need a special partition for grub that is at least 1MB size, has no filesystem on it and has flag bios_grub (in gparted) or type ef02 (in gdisk). Then you get the advantage of more than four primary partitions.

Edit: Fixed what I wrote in my sleep. Thanks, HoaS!

It's not nonsense at all. You miss the point. I think it's fine for you to modify your system any way you want. The ability to do that is one of the best features of linux.  I think it would be very bad if debian made it official policy to remove all sysvinit scripts. Likewise, I think it would be very bad if devuan made it official policy to remove all systemd service files.

Is this something new that a boot partition needs to have a boot flag, or are you talking about an efi partition?

Same here. 1.20 from devuan beowulf main repo

Thanks. They're working on it.
https://bugs.devuan.org/cgi/bugreport.cgi?bug=548

Thanks. I never noticed that. Most of my installs are tests, so I use very short passwords. The yad dialog window only takes 18 characters, but it stores more if you type them. I'm not sure why it didn't use your long password.

I tried running the code in a terminal (as root), and it works. I'll have to try it in an install.

Here's the code for that window with the output of my 20-character password entry.

~# pass_entry=$(yad --form --title=$"Configure $pass_dialog password" --center --borders=10 --button=$"OK":0 \
--text=$"You should reset the $pass_dialog password.\nUse TAB to change fields." \
--field=$"Enter new $pass_dialog password::H" \
--field=$"Confirm new $pass_dialog password::H"  \
--field=$"Use current password\? (not recommended)":CHK \
"$field_four")
12345678901234567890|12345678901234567890|FALSE|

Trim the output, check it and feed it into the passwd command, and it works.

newpass=$(echo $pass_entry|awk -F "|" '{print $1}')
echo $newpass
12345678901234567890

/bin/bash -c "echo -e \"$newpass\n$newpass\n\" | passwd $newusername"
New password: Retype new password: passwd: password updated successfully