New torrent files:
https://files.devuan.org/devuan_beowulf.torrent
https://files.devuan.org/devuan_ascii.torrent

Magnet link

We're using these trackers now:
udp://9.rarbg.me:2710
udp://tracker.opentrackr.org:1337
udp://tracker.cyberia.is:6969

Yes, you could add a boot paramater instead of removing that live-config script. To test on the fly, press TAB at the isolinux boot menu or 'e' at the grub boot menu to edit the boot command.

To change the templates for the boot menus, so you don't have to edit them on every build, look in /usr/lib/refractasnapshot

If there's a way to tell the computer to boot from usb, then it should ignore any bootloaders on the hard drive.

Boot loop usually means kernel and initramfs are missing. Mount the iso and look inside the live folder. There should be filesystem.squashf along with kernel and initramfs. And if the file names are different, make sure the boot menu has the right names.

I have no idea what would do that.

Look in /var/log/apt/history.log to see what really got installed or removed.

If you're using grub-efi-amd64-signed and have ID=devuan in /etc/os-release, you'll boot to a grub prompt instead of a boot menu. That's because grub will expect the signed bootloader to be found under /boot/efi/EFI/debian, but your bootloader will be in /boot/efi/EFI/devuan instead.

Some third-party software that expects to see debian might complain or refuse to install. I don't have an example.

There's also /etc/issue, which is in most linux distros.

You missed one option:

4. Ignore the question and continue. The driver will be installed automatically unless you choose expert install and exclude non-free software.

If we remove that question, then those people who need certain broadcom firmware will be stuck.

I can confirm that iwlwifi-7260-17.ucode is in firmware-iwlwifi in jessie, beowulf and chimaera.

1. On devuan you have to edit /etc/pulse/client.conf.d/00-disable-autospawn to get sound.
On Refracta, that's not an option because pulseaudio is not installed. Sound works out of the box in most cases.  What does aplay -l show? Is the hardware too new for the debian kernel?

2. Not enough info to diagnose the problem. Check the log. Maybe delete the work directory if you're saving it between runs. Maybe something got mangled there and it's not getting cleard on subsequent runs.

In English, the name changed from Preferred Applications to Default Applications, and in the Settings manager, it got moved from the Personal section to the System section.

I had to upgrade my ceres to get 4.16 and xfce4-settings was held back to 4.14. At that point, Preferred applications was missing, but I don't know if Default applications was there. I upgraded xfce4-settings to 4.16 and restarted the destkop before I noticed it.

Here's one with backports kernel (kinda old one now) and wireless firmware already installed for testing new hardware. It's not the full mix - openbox, lxpanel, not a lot else.
https://get.refracta.org/files/experime … 5_1323.iso

Update: Here's a newer one with 5.9 kernel.
https://get.refracta.org/files/experime … 9_0205.iso

You got this output for the line that says losetup ${LOOPDEV} $img but there's nothing for $LOOPDEV in the output. "No such device." The error also shows up in the first lines of the output where it shows that cat failed and LOOPDEV is empty.

+ losetup test.img
losetup: test.img: failed to use device: No such device

I think you need to define LOOPDEV after you run 'losetup -f'.

crypt_create () {
        losetup -f > /tmp/nextloop
        LOOPDEV=$(cat /tmp/nextloop)
        losetup ${LOOPDEV} $img
        cryptsetup luksFormat $img
        cryptsetup open $img cryptfs
        mkfs.ext4 /dev/mapper/cryptfs
}

Thinking about how that will expand is making my head hurt. Wouldn't $1 = 'if=/dev/urandom'? And so on...

I like to redefine positional paramaters at the beginning of the script to give them meaningful names and to make sure I know what they really are.

outfile="$1"
blocksize="$2"
blockcount="$3"

dd if=/dev/urandom of=$outfile bs=$blocksize count=$blockcount iflag=fullblock

Then call the script with

myscript.sh value.img 100M 1

You only need one line. There's no chimaera-updates or chimaera-security until it goes stable. Leave those commented out for now. Also comment the third-party repo for the upgrade. The deb-src lines are only needed if you want to rebuild source packages.

I did an upgrade from beowulf to chimaera back in July. There were a few tricky spots. I'll leave you my notes. You will probably run into some different tricky spots, so do not follow these directions exactly. They are only here as an example. Also, search this forum for other accounts of upgrading to chimaera.