I looked into this a bit and found a fair few ducks to line up before it worked both in console and Xorg.

For bell sound by the "xkbbell" command I needed to

• add a special "InputClass" configuration snippet that tells Xorg to use the "kbd" module (from xserver-xorg-input-kbd) for the "PC Speaker" device;

• configure Xorg to bell with 50% volume rather than 0%, and

• enable loopback for the sound card.

My special configuration snippet /etc/X11/xorg.conf.d/pcspkeaker.conf is

Section "InputClass"
	Identifier  "PC Speaker"
	MatchProduct "PC Speaker"
	Driver      "kbd"
EndSection

You can use the "lsinput" command (from input-utils) to verify the name (i.e. the MatchProduct string) of the device. You also need to restart Xorg for loading the snippet.

The Xorg bell volume would be raised with an "xset" xommand:
# xset b 50

Loopback enabling might also be a command:

$ amixer sset 'Loopback Mixing' Enabled

though the actuals of that does depend on the soundcard; use a plain "amixer" command and guess from that.

I also needed that loopback enabling to hear a console bell.

Each terminal emulator has its own code to handle keyboard input and character output/display. Some of them have configurable properties to "re-enable" audible bell and some don't.

What do you get from lsblk ?

@unixuser, from memory (since I don't use firefox anymore) I needed a dmix pcm on the playback path for firefox; something with firefox spawning sub processes after having opened its playback sink and then in effect accidentally lock up itself (since the normal playback is exclusive) even though firefox has a single playback process. And for that same reason, it needs the similar setup with a  dsnoop on the capture path, and therefore it needs the prior asym pcm to split playback and capture.
Afair I had it working with that, something like:

pcm.!default { type asym; playback.pcm multisink; capture.pcm multisource }
pcm.multisink { type dmix; ipc_key 29879; ipc_key_add_uid true; slave.pcm plughw }
pcm.multisource { type dsnoop; ipc_key 16234; ipc_key_add_uid false; slave.pcm hw } 

Please note that whilst we can continue to be amazed about all your different operator habits, the OP problem was not a question about how and when to be root.

The problem was that libreoffice writer apparently added some extra "invisible" bytes to the beginning of a supposedly text file, and the solution was to remove those bytes.

My view is still that if one wants wiki pages to edit then one'd do that on a wiki site; if one wants to publish blogs then one'd do that on a blog site.

Each thing to its own rather than trying to shoe-horn in everything into the one system. It may require a moment of reflection on one's purpose behind the urge of sharing a thought structure, and I find that to be a good thing in itself even though it might place the rendering of that thought structure elsewhere than on this forum.

Those first three bytes are some kind of byte-order marker which is something that Window's Notepad likes to drop into text files, and you should remove them. You could do that with the folllowing command (do it ONCE only as it will otherwise remove the next three bytes):

sed '1s/^...//' -i /etc/apt/sources.list

Then, it should go without saying, never never never use Window's Notepad to edit text files.

(Of course I may well be wrong about Notepad )

Does a music player need to start at boot?

@cake, re git stores... nowadays I'd suggest codeberg.org
and you're of course also welcome at git.devuan.org

You seem to have messed up the APPEND line with a badly placed pointer duing copy+paste. Restore and try again.

Note that there must not be a space between a key and its value unless both the key and the value are wrapped into a pair of matching quotes.

Firstly, you have prepared the USB stick correctly. It does present itself as a disk image with two partitions where the first is an iso9660 partition (CDROM format) and the second is a FAT32 partition (also called vfat).

And the vfat partition is also an EFI boot partition that should be browseable with an EFI shell... are you able to do that?

I believe beowulf had a grub setup for EFI boot. Which files do you see in that partition with the EFI shell?

EDIT: yes, follow rolfie's advice..

update-rc.d $service $action

EDIT: I'm pretty sure there is a man page for it...