Yeah, we made it official at yesterday's meeting. Nice to see that you showed up, but you left too soon. IRC is asynchronous. You gotta hang around, even if you don't sit there watching the irc screen.

sda1 should be the efi partition, which appears to be correctly mounted at /boot/efi. Run blkid to prove to yourself that it holds a fat32 (vfat) filesystem.

I'm having trouble keeping up with the changes in grub's behavior over the last year or so, but I think you probably just need to remove grub-efi-amd64-signed. The unsigned package will remain. Run grub-install and update-grub afterward. This solution assumes you don't use secure boot.

If that doesn't work, ask again or poke around the forum for other solutions. (Hint: search for "set prefix")

I'm another one who saw this on the chimaera isos. I don't know if it's in any of the beowulf isos. My solution was to change the wireless password to one that contained only lower-case characters, and it worked. Disabling the password worked, too.

It only seems to be a problem with the installer. The installed system works fine with the original password that contains other characters.

All the installer isos have non-free firmware that gets installed if your hardware needs it unless to choose expert install and tell it you don't want non-free. In the live-isos, most of the wireless firmware packages are already installed.

arno-iptables-firewall is nice and simple. You can configure it with debconf, and it will ask a few questions about which interface(s) to use and which ports to open, etc. There's a way to do fancier stuff by editing configs, but I've never done anything with that.

After making the edit:
Use su -if you want to cd to /root.
Use su if you want to stay in the current directory or if you want to run a graphical app as root on the user's desktop. (e.g. I frequently start gparted from terminal because I'm already in a terminal and it's easier than going up to the menu.)

@Dutch_Master: check to see if your cpu or motherboard is known to freeze with linux. I have one box that needs an extra boot option to prevent lockups.

I hate using 'su -'. Most of the time when I become root, I'm already in the directory where I want to do stuff, and I want to stay there. I don't want to change to /root. And sometimes I want to run a graphical app as root from the user's desktop. That got lost in the change, too. Fortunately, there's a way to restore the old behavior.

ALWAYS_SET_PATH yes

in /etc/default/su

su got moved from shadow to util-linux. I don't know what thought went into the change in root's path when you get there via 'su'. If you use 'su -' it still works the same as it used to. It's in the release notes for beowulf along with some other inherited gems and workarounds. https://files.devuan.org/devuan_beowulf … _notes.txt

After you configure the clock/timezone, you get the following screen. Choose "Manual".
https://www.devuan.org/os/documentation … disks1.png

Here's the link for that page: https://www.devuan.org/os/documentation … all-devuan

I use refracta2usb for that.
https://refracta.org/docs/readme.refracta2usb.txt
https://sourceforge.net/projects/refrac … b/download

You can create multiple partitions on the usb stick.
First partition must be fat32 and will hold live-isos or unpacked live-isos.
Additional partitions can be used for persistence or to hold loopback files for persistence.
Persistence volumes can be encypted if you want.
If you really want to only have one partition, you can have that with loopback files for persistence on the same volume.
More...

Ask if you have more questions.

I just tried this in a test system (chimaera in qemu) and had a lot of trouble going back to sysvinit. I'm pretty sure that's because of some changes I made. After I added some runscripts and got them working right, I used update-rc.d to remove the corresponding sysvinit links and I also made the init scripts non-executable. I should have reversed those changes before installing sysvinit-core.

It's working, but it takes a long time for the desktop to come up. Boot time is normal, it pauses at console login, and at first I thought I would get no desktop. So I logged into console, and it took a minute to respond to my password. About that time, the desktop came up. If I don't log into the console, the same thing happens. Takes about a minute from when I log in for the desktop to come up.

I have no idea about the audio problem. Does aplay -l show anything?

Console font can be changed with dpkg-reconfigure console-setup as root.

A1: alsa is installed, mocp can play audio files, and if you choose one of the access options to boot, the computer will talk to you the entire time it's on. I don't recommend using that unless you have vision problems.

A2: ifconfig eth0 down There's also a way to do it with the 'ip' command, but I haven't gotten around to learning that one yet.