Thanks GNUser for this thread. Useful for me as I have only wireless here (in some areas only) from a neighbour's router.

True but its been forked, and maintained (in the last 2 months) elsewhere:

https://github.com/lakinduakash/linux-wifi-hotspot

There is a deb package with python-based GUI (but usable from cli only). Or build your own from the source, as did I. Working here, tested only on ceres so far, at least as wireless repeater. I'm using network-manager, that seems to be detected and not permanantly interfered with. I now have optional connection in a previously dead zone via another Devuan box.

Using 2x cheap usb wireless adapters, couldnt get either to work alone.

You might want to disable automatic start of dnsmasq (sysv-rc-conf) unless you got reason not to.

I will try your more minimal script at some point.

Seems something else is using 127.0.2.1:53 (maybe another instance of dnscrypt-proxy?) You could investigate using lsof and ps ..

Or just change 127.0.2.1:53 to 127.0.0.1:53, that's the default anyway. I only use 127.0.2.1 from an older release custom config, which simply works here. Remember to update network-manager configs also, if you use that. Should all be good after a reboot.

You may also need to create ~/.asoundrc wih something like this (change "Port" and device "mac address" to suit.:

pcm.Port { 

	type bluealsa
	device "77:20:1E:FE:4E:E4"
	profile "a2dp"
	hint  { show on description "Port" }
}

I used bluez-alsa for a while with reasonable success but now finding pipewire more reliable. You can have both installed but if you try pipewire  bluealsa service should stopped and disabled in sysv-rc-conf..

blueman-applet seems the easiest way to search available devices, get info, set up.  Or bluetoothctl in a terminal.  Setup sequence is trust>pair>connect .. good luck..

Thanks all here for the info on setting up pipewire for chimaera. Tried and failed till now.  Although  bluez-alsa does work for my BT speaker. I don't use pulse-audio.

I first installed the packages as described by Devarch. Note these packages actually get installed as deps: pipewire-bin libpipewire-0.3-modules libwireplumber-0.4-0 libpipewire-0.3-0 . These backports are almost up to current unstable versions.

With the latest packages, everything subsequently (at least after reboot) worked "out of the box" on my Toshiba laptop. No file copying no other configurations. The Debian wiki is outdated. The BT speaker is up and running, including firefox streams which failed with bluez-alsa.

Thanks HoaS for the start script. I adapted it quite a bit because I want to start/stop pipewire manually. Also, sometimes a restart is needed (here) to fix an occasional bt connection drop out. And I don't want processes not in use autostarting (I disabled also /etc/xdg/autostart/blueman.desktop).

Placed in ~/bin/ and called from a desktop launcher:

#!/bin/bash

# Script name: bluestart
# Place in ~/bin and make a desktop launcher 
# Execute "bluestart stop" to just stop pipewire and related processes without restarting.

# (in case you used "stop" parameter)
MODE="$1"

# You probably need to restart your system mixer to register/deregister the pipewire device.
# Edit (or comment) the next line to suit whatever your DE uses:
MIXER=kmix

# Don't run this as root!
if [ $EUID -eq 0 ]; then exit 1; fi

restart_mixer () {

	if [ -n "$MIXER" ]; then

		pkill -u "$USER" "$MIXER" >/dev/null 2>&1
		$MIXER &
	fi
}

stop_pipewire () {

pkill -u "$USER" pipewire-pulse >/dev/null 2>&1

pkill -u "$USER" wireplumber >/dev/null 2>&1

pkill -u "$USER" pipewire >/dev/null 2>&1

killall blueman-applet blueman-tray blueman-mechanism 2>/dev/null

# delete blueman stat files in ~/.config
for i in $(ls ~/.config|grep blueman); do rm -f $i; done

}

stop_pipewire

if [ "$MODE" = "stop" ]; then
	sleep 3
	restart_mixer
	exit 0
fi

pipewire &

until pgrep -f pipewire >/dev/null 2>&1 ; do
   sleep 1
done

wireplumber &

pipewire-pulse &

blueman-applet &

sleep 2

restart_mixer

Hope that helps someone..

@OP: Please note Devuan default runlevel is 2 (you only change that if you got a reason)

It is! (and you can generate any others needed and choose your system default)

root@exegnu:~# dpkg-reconfigure locales
Generating locales (this might take a while)...
  de_DE.UTF-8... done
  en_GB.UTF-8... done
  en_US.UTF-8... done
  es_ES.UTF-8... done
  fr_FR.UTF-8... done
  it_IT.UTF-8... done
  pl_PL.UTF-8... done
  pt_PT.UTF-8... done
Generation complete.

? It boots here with or without "apparmor=0" ..

I always found "findiso" simpler to configure than "fromiso".. here's my grub.d/40_custom entry:

menuentry "devuan5 preview" {
	insmod part_gpt
	set isofile='(hd0,gpt7)/devuan_daedalus_5.0.preview_20221022_amd64_desktop-live.iso'
	loopback loop $isofile
	linux (loop)/live/vmlinuz boot=live tzdata=Europe/London locales=en_GB.UTF-8 username=devuan findiso=/devuan_daedalus_5.0.preview_20221022_amd64_desktop-live.iso
	initrd (loop)/live/initrd.img
	}

That was the case before although the Debian packages were compatible with Devuan. TDE now have specific repos for all Devuan versions (and R14.0.11 is released today, in case anyone still thinks it's old, unmaintained code)

https://wiki.trinitydesktop.org/Devuan_ … structions

Worth a go here as my trusy old Vaio netbook has **** sound (and I don't want pulseaudio).

I got bluealsa working but it was not so simple. For a start packages bluez-alsa-utils libasound2-plugin-bluez (you need both) have only a systemd service file, no sysv script. I needed bluetooth daemon running first and a custom ~/.asoundrc

pcm.SoundCoreMini {
        type bluealsa
        device "XX:XX:XX:XX:XX:XX"
        profile "a2dp"
        hint { show on description "Sound Core Mini"}
}

Having already installed blueman I could use those tools to get the device ID. The device can then be manipulated using blueman-manager.

I repackaged it with a custom init script but havent got that quite right as yet. It won't detach from the shell and hangs on bootup. But I can start it manually after disabling the init daemon.

Running chimaera you *might* get away with just a few lib deps from ceres. The original packages will break beowulf. My crude "backport" rebuild from source can run on beowulf.

Here's the offending custom init script, if anyone wants to debug it. More later (if) I get time to revisit this. Or maybe it's better not to have this start automatically..

#!/bin/sh
### BEGIN INIT INFO
# Provides: bluez-alsa

# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6

# Required-Start:	$syslog $local_fs $remote_fs bluetooth 
# Required-Stop:	$syslog $local_fs $remote_fs 
# Short-Description: Bluealsa daemon
### END INIT INFO

. /lib/lsb/init-functions
prog=bluez-alsa
if test -f -/etc/default/bluez-alsa; then
	. -/etc/default/bluez-alsa 
fi

PIDFILE=/var/run/$prog.pid
DESC="Bluealsa daemon"
start() {
	log_daemon_msg "Starting $DESC" "$prog"
	start_daemon -p $PIDFILE /usr/bin/bluealsa $OPTIONS
	if [ $? -ne 0 ]; then
		log_end_msg 1
		exit 1
	fi
	if [ $? -eq 0 ]; then
		log_end_msg 0
	fi
	exit 0
}

stop() {
	log_daemon_msg "Stopping $DESC" "$prog"
	killproc -p $PIDFILE /usr/bin/bluealsa
	if [ $? -ne 0 ]; then
		log_end_msg 1
		exit 1
	fi
	if [ $? -eq 0 ]; then
		log_end_msg 0
	fi
}

force_reload() {
	stop
	start

}

case "$1" in
	start)
		start
		;;
	stop)
		stop
		;;
	force-reload)
		force_reload
		;;
	restart)
		stop
		start
		;;

	*)
		echo "$Usage: $prog {start|stop|force-reload|restart}"
		exit 2
esac

My installed bluetooth-related packages:

root@vaio:~# dpkg -l|grep blue
ii  blueman                                  2.0.8-1+deb10u1                     amd64        Graphical bluetooth manager
ii  bluez                                    5.50-1.2~deb10u2                    amd64        Bluetooth tools and daemons
ii  bluez-alsa-utils                         3.0.0-2                             amd64        Bluetooth Audio ALSA Backend (utils)
ii  bluez-firmware                           1.2-4                               all          Firmware for Bluetooth devices
ii  bluez-obexd                              5.50-1.2~deb10u2                    amd64        bluez obex daemon
ii  libasound2-plugin-bluez:amd64            3.0.0-2                             amd64        Bluetooth Audio ALSA Backend (plugins)
ii  libbluetooth-dev:amd64                   5.50-1.2~deb10u2                    amd64        Development files for using the BlueZ Linux Bluetooth library
ii  libbluetooth3:amd64                      5.50-1.2~deb10u2                    amd64        Library to use the BlueZ Linux Bluetooth stack
ii  libpam-blue                              0.9.0-3                             amd64        PAM module for local authenticaction with bluetooth devices

EDIT: example use:

:~$ mpv --audio-device=alsa/SoundCoreMini 'Sweet Georgia Brown 1.m4a'

Or in VLC, pick  it from the audio device GUI.

Cheers all (and thanks for chimaera), D

I guess some have their use-case reasons to automount removables. I don't know why.

Mounting an mtp device should be as simple as:

jmtpfs /path/to/your/mountpoint/
fusermount -u /path/to/your/mountpoint/

Or you could script that with some checks and a fancy yad dialog.

(OT) thanks xinomilo for mentioning  "lineageOS" (android AOSP based without bloat/spyware), probably as clean as you will get on such devices. The only network connection here at the moment is 4g. I did quite a bit of research on android (lack of) security and run lineage (without gapps).

Recent Youtube changes broke gtk-youtube-viewer (maybe other clients). It was forked to "gtk straw viewer" and works again. Well here and for now at least.. https://github.com/trizen/straw-viewer

Using a youtube client avoids heavyweight browser loading, ads, tracking... This one is quite light on deps and system resources but has a very good descriptive gui. No qt deps. Probably needs latest youtube-dl to run properly https://github.com/ytdl-org/youtube-dl

I posted (probably the only) deb package: http://exegnulinux.net/apt/pool/main/s/straw-viewer/

Sources, dsc et al are at the same url if anyone wants to inspect, compile or modify yourself. If interested, please post back if you see anything wrong with the package.

EDIT: youtube-dl (and anything else that uses it) will puke unless you update it quite often.

Maybe or not your problem is related but:

My ceres live builds, with *default* 5x kernels (all of them), hang every time in seemingly random stages of bootup. Often while still in initramfs. This older HP (Intel) laptop is all I have around at the moment. They boot fine with some combinations of "failsafe graphics" parameters on the cmdline (maybe breaks some acpi-related functions):

noapic noapm nodma nomce nolapic nosmp

Seems a major kernel issue. A search for, e.g. "linux 5x intel hangs", returns much info but little good news, at least not soon. No such issues here with Beowulf and Ascii systems.

:~$ uname -r && inxi -CG
5.4.0-4-amd64
CPU:
  Topology: Single Core model: Intel Core2 T5500 bits: 64 type: MCP
  L2 cache: 2048 KiB
  Speed: 1662 MHz min/max: N/A Core speed (MHz): 1: 1662
Graphics:
  Device-1: Intel Mobile 945GM/GMS 943/940GML Express Integrated Graphics
  driver: i915 v: kernel
  Display: x11 server: X.Org 1.20.7 driver: intel
  unloaded: fbdev,modesetting,vesa resolution: 1024x768~60Hz
  Message: Unable to show advanced data. Required tool glxinfo missing.

My usual method is an out-of-the-box live image (Refracta is the prime candidate but there are others) with LUKS encrypted full persistence. The live image is tailored to suit as many machines as possible. The persistence is a custom overlayfs, can be a (decent size) file or a partition. On boot it will prompt for the LUKS key, if you don't have that it will continue to boot to only the basic, default live image. The security of the rest is down to the strength of your encryption key.

It's quite surprising how quickly and efficiently such a system can run..