Are you using secure boot?
Are you unable to boot your os?

If your answer to the second question is 'yes' then you will need to do something. We will help you figure that out. Otherwise, you can ignore it.

In previous testing, the bootloader had to be named 'debian' if you used the signed grub package. Otherwise, it could not find the bootloader, because $prefix was hard-coded as EFI/debian. I don't know if that's still true in beowulf.

lsb-base and lsb-release in ascii are devuanized packages. You can tell because 'devuan' is in the version. In beowulf, chimaera and ceres, we're using the unchanged debian versions.

The code you're looking for might be here: https://salsa.debian.org/debian/lsb

Probably not, but I'll try. I think the behavior of grub has changed since that was tested for the release notes. To change it in the boot menu, you can either change it in /etc/default/grub or /etc/os-release and re-run update-grub.

Like this works:

GRUB_DISTRIBUTOR=Devuan

Changing the 'ID=' line in /etc/os-release will also change the name of the bootloader created by 'grub-install'. I don't think /etc/default/grub will do that. Correct me if you find otherwise.

Changing it in /etc/lsb-release works, too, but you won't have that file unless you created it. Or maybe I created it for you, if you're running Refracta.

If you have secure boot enabled, I don't know what will happen. Some time ago, the bootloader directory on the efi partition needed to be named 'debian' if you were using the signed version of grub-efi-amd64, even without secure boot enabled. That appears to have changed in chimaera. Either that or my motherboard is lying to me about secure boot. That's a distinct possibility, since manufacturers can seem to agree on uefi implementations.

Welcome to Devuan.

You've been around linux long enough to see that every release gets bigger and more hungry for resources. Part of the reason we left the graphical installer out of the installer isos was to leave more room for applications that might be needed when installing without a network connection.

If you've used graphical installers on other distros, you might be disappointed with the debian-installer's rendition. The ncurses variety that you saw is actually easier to use - it requires less motion.

You can see for yourself. There's a graphical installer in the mini.iso on this page.
https://pkgmaster.devuan.org/devuan/dis … tboot/gtk/

The mini.isos get made when the installer gets rebuilt. They're mainly for testing, and they require a wired network connection to get even the most minimal working system.

The live isos use a different installer that just copies the system from the media to the hard drive. It takes about 10 minutes, but you don't get to choose the software.

.

A condensed version with the essentials is always good, especially when I don't have to do it. Thanks.

Replace /lib/cryptsetup/cryptdisks-functions with the patched copy I linked above.

Just this in sources.list. There's no -security or -updates (or anything else) for chimaera or ceres. You could add contrib and non-free if you want.

deb http://deb.devuan.org/merged chimaera main

There's no amarok in buster, therefore there is no amarok in beowulf. Try stevepusser's build. I recommend downloading the packages to install manually rather than adding a foreign repo.
http://forums.debian.net/viewtopic.php? … dd5b92d7be

It's not a bug. It's just that events are happening slightly out of sequence. Official announcement is coming soon. Say yes. If you were already up to date, you won't see any new packages.

jfs, xfs, btrfs and all the other usual choices are there in manual partitioning. That option is available in both regular install and expert install. If you're not seeing all the options, check the sha256sum to make sure the download was good.

I just did a no-mirror install from devuan_beowulf_3.0.0_netinstall-amd64.iso onto a new btrfs partition.

That one does not have the udev fix, but it does have whatever I fixed before that. (mouse, keyboard and ping, I think.) And it has the default log level for udev.

Anyway, I'm making RC2 right now. Put the fix in rc.local because it's less hidden and easier to remove. (live installer has post-install cleanup scripts) If I didn't break anything in the process, these will be the official release isos. Better fix for the udev issue might come with the point-release, which we expect will be soon.

Here's one for now. I'll upload the whole set to the official site when they're all done.
https://get.refracta.org/files/testing/ … p-live.iso

sha256sum:

8225b3d4cc30327f142cbe1584ed100da0d48785c6e105983a64e16f8d620ad4  devuan_beowulf_3.0.0_RC2_amd64_desktop-live.iso

A few more notes... (using refracta10-beta5)

If I boot to runlevel S or 2 (default), then eudev is running as '/sbin/udevd udevd', but boot to runlevel 1 and eudev is not running.

If I boot to single and then change to runlevel 1,  /sbin/udevd udevd is gone, but the pid file is still present. If I delete the pid file and go to runlevel 2, I got no mouse or keyboard.