Tunapie

I've got it but don't use it much. Here it's working with audacious as a player. I just open tunapie and can select from a huge list of radio stations, sorted by genre if I want.

Looks like it does not include real broadcast radio stations. I tried a few call letters in the search box and got no hits. Even for stations that I know do web streaming. For those, you can put their url in just about any player.

Another solution (new in devuan 3.1.0 point-release.)

Install debian-pulseaudio-config-override
Description: Debian configuration overrides for pulseaudio

You'll get this automatically if you install a desktop environment from the 3.1.0 installer isos.
(task-desktop Recommends debian-pulseaudio-config-override)

Looks like there's a mis-match in the directory name and maybe confusion between a function name and a directory. I see
custom-packages
install-custpackages
install-custdebs

#!/bin/sh
cd custom-packages
dpkg -i *_all.deb *_amd64.deb

 (*) Chrooting to execute 'install-custpackages' ...
chmod: cannot access '/home/user1/live-sdk/tmp/devuan-amd64-build/bootstrap/install-custpackages': No such file or directory

I have to go out and can't poke around in this right now. My build failed on trying to install firmware. And every time the build fails, I have to reboot my computer. I am not a happy camper right now. Maybe later I'll tar up the version of live-sdk that I'm actually using to build the official isos and you can download it.

One more item: live-sdk is getting a complete re-write. I don't know the current status, but I intend to get in on that effort.

Without a blend, you could adjust the package lists in lib/libdevuansdk/config but you're better off creating a blend. It gives you more control. This is the file:
https://github.com/parazyd/libdevuansdk … 300/config

For the package sets, edit where the sets are defined to add or comment/remove packages, and you can exclude whole sets in the stanza you posted that shows which sets to include by commenting them out.

I'm not sure what commands to use on the version you're running. I've been using an older version to build isos. Changes were made since I last interacted with the git repo (on git.devuan.org). And I've had some trouble using the newer version. However, I can reproduce your error with the new version.

You need to define the arch in your blend config file instead of on the command line. So put
arch="amd64"
or
arch="i386"
in blends/devuan-minimal-live/config

and use these commands (as root):

zsh -f
source sdk
load devuan devuan-minimal-live
build_iso_dist

One more thing. If you build for i386 you might want to look in lib/libdevuansdk/zlibs/kernel if you want to change it from plain 686 kernel to the 686-pae kernel.

Here's the one on devuan's git: https://git.devuan.org/devuan-sdk/live-sdk

This doesn't seem to be working for me, and I can't figure out what I'm doing wrong. I followed the directions in the README and set up cron and then anacron to work with runit. I can't tell whether it's running or not because it looks like I'm getting contradictory information.

Also, I made a test script that dumps the time into a file in user's home and put it in /etc/cron.hourly/. It works when I run it manually but does not run every hour.

sv says they are down but shows the pid and how long they've been running.

root@chimaera-2:/home/user# sv status cron
down: cron: 24s, normally up; run: log: (pid 2038) 24s
root@chimaera-2:/home/user# sv status anacron
down: anacron: 34s, normally up; run: log: (pid 2042) 34s

Attempt to bring them up makes no change.

root@chimaera-2:/home/user# sv up anacron
root@chimaera-2:/home/user# sv up cron
root@chimaera-2:/home/user# sv status cron
down: cron: 4s, normally up; run: log: (pid 2038) 59s
root@chimaera-2:/home/user# sv status anacron
down: anacron: 14s, normally up; run: log: (pid 2042) 63s

'ps ax' says they are running but pstree does not.

root@chimaera-2:/home/user# ps ax | grep cron
 2033 ?        Ss     0:00 runsv cron
 2034 ?        Ss     0:00 runsv anacron
 2038 ?        S      0:00 logger -p daemon notice -t runsv-cron
 2042 ?        S      0:00 svlogd -tt /var/log/runit/anacron

      ├─runsvdir─┬─6*[runsv───getty]
      │          ├─runsv─┬─acpid
      │          │       └─svlogd
      │          ├─runsv─┬─sshd
      │          │       └─svlogd
      │          ├─runsv───logger
      │          └─runsv───svlogd

What next?

One of the founding fathers of devuan is an astronomer. All our releases are named after minor planets.
https://www.devuan.org/os/releases

1+ for apod. Some of my favorite desktop backgrounds come from there.

Maybe you can do something with these.

From refractainstaller. This lists partitions. It does not differentiate between encrypted and non-encrypted. Using blkid would be one way to find the encrypted partitions.

find /dev -mindepth 1 -maxdepth 1  | egrep  "*[shv]d[a-z][1-99]|*nvme[0-9]n[0-9]p[1-99]|*mmcblk[0-9]p[1-99]"   | sort | awk '{print "\n" $0 }'

Same thing with a graphical interface (yad)

device=$(find /dev -mindepth 1 -maxdepth 1  | egrep  "*[shv]d[a-z][1-99]|*nvme[0-9]n[0-9]p[1-99]|*mmcblk[0-9]p[1-99]" \
  | sort | awk '{print "\n" $0 }' \
  | yad --list   --title="Select device" --center --borders=10 --text="Select a device." \
  --separator="" --column ' ' --column$'Partitions' --height=380 --width=200 --button="OK":0)

From refracta2usb. These list usb devices.

usbdevlist=$(/usr/sbin/hwinfo --usb --short|grep "/dev/sd"|awk '{print $1}')
usbdevfulllist=$(/usr/sbin/hwinfo --usb --short|grep "/dev/sd"|awk '{print $0}')

And used with yad.

device=$(yad --width=400 --height=200 --center --title="$TITLE" --list --separator="" --column="" --text=$"Detected USB devices:\n\n$usbdevfulllist\n\nSelect the target device you want to copy the live image to." $usbdevlist \
	--button="OK":0 --button="Exit":1

I had to alter some of these so they would make sense. I hope I didn't break anything.

The mute light on my T420 doesn't work right. I haven't looked into that.

You are right that a window comes up asking for root password after selecting sudo as default. That part was written so long ago I didn't remember that, and nobody else has pointed it out. There is a checkbox in that window that says "Disable root account" so I know the window was meant to come up. I'm not sure why, but I'll look into it.

The debconf dialogs really are the same ones in the graphical installer, but there are some problems with that. For one, we don't offer a graphical version of the debian/devuan installer because it got too big and was making the isos larger than we wanted. If you want to see the familiar ncurses version of these dialogs, sudo apt remove libgtk3-perl in the live session before running the installer. (More on this later.)

The second problem you noted is the drop-down menu. It went off-screen on my laptop and I couldn't get down to London. I believe that's a gtk-3 feature that I've seen before. The graphical debconf dialogs are going away in the next set of isos and it'll be back to the ncurses version. That's what it was for jessie and ascii. We're working on getting the beowulf point-release out, so it should be soon.

As you noted, selecting the locale does not automatically select the keyboard map. I just checked with the netinstall iso, and it doesn't do it there on the regular install, but it does on expert install. I think that's easy to change. (dpkg-reconfigure -plow ...)

I'm not familiar with this method. What installer uses encryptfs? The regular debian/devuan installer can do plain luks encryption on single partitions or it can encrypt a physical volume that contains multiple logical volumes for separate partitions. If you do encrypted LVM, you only have to put in a password once to unlock the encrypted volume. The live installer does not do LVM (without some manual tricks) so you can only encrypt individual partitions. If you choose a separate /home partition (it is not mandatory) and you encrypt that partition, you will need to enter a password for it. As I mentioned before, you can create a keyfile and keep it in the encrypted root to automatically unlock the home partition. It's not a plain-text password. See man cryptsetup for details.

In either of the above situations, you need a separate /boot partition that's not encrypted. It is possible with the live installer to do full-disk encryption and have an encrypted /boot partition. In that case you get to give the luks passphrase an extra time for grub, and on top of that, it takes grub a long time to digest the password.

You missed those things for the same reason you had some other problems with the live installer. It's because you are not familiar with how it works. It's different from what you are used to. You certainly do have access to all those things because you are in a running live environment, and any changes you make to the system will be copied to the installed system. That includes network setting and configuration changes. You could also remove or install packages, but installing them might use up too much ram in the live session.

Thanks for the input. I will make some changes.

Security updates are sometimes late in devuan because amprolla gets confused when it sometimes gets a 404 on a debian repo. When this happens, it's usually discovered and fixed within a few days. You've probably seen the discussions on this forum about it.

There are people working on this, and based on something I was told a few days ago, it might already be fixed.

Thanks. I wasn't aware that a private company is offering commercial support for Debian, but I'm not surprised by that. If someone wants to form a private company to offer extended support for Devuan users, they are welcome to do so. I don't think it's fair to fault the dozen or so devs we have for not doing that.

WTF???

security uploaded by anyone. Right.

Buster/Beowulf has another year before it moves into LTS. Then figure another two  before Bullseye/Chimaera moves to LTS. You could easily add another year or two to that, so we are potentially up to 5 years. Chimaera is already working pretty well, and Bullseye has gone into soft freeze, so I feel confident that it can't get screwed up too badly for us to fix and use it.

Wow, this all sounds so wrong.

ifup/down works with interfaces that are configured in /etc/network/interfaces

ssh starts and stops according to the links in /etc/rc?.d which are defined in the init script, /etc/init.d/ssh. It does not care about ip addresses or interfaces. Check your system logs to see if you can figure out why ssh is not running.

If you're going to always use wireless on this device with the same local network, you could set up a static ip in /etc/network/interfaces. If you have any network management software installed (n-m, wicd, connman, etc.) you should remove it so it doesn't fight with your static config.