You are not logged in.
Beginning of February I downloaded a current Bullseye netinstall image and installed it in VBox. Can't remember that I got an init choice like in Devuan.
rolfie
Started off with sysvinit under ASCII some years ago, then experimented with openrc in VBox and finally installed an AMD470/Ryzen 2700X with openrc / ASCII. Motivation: refer to HOAS comment in the previous post.
Meanwhile all my active PCs at home have moved to openrc/Beowulf. With my kind of operation (office and internet, a nfs fileserver in the background) I have no issues found.
Currently I am investigating runit/Chimaera in VBox.
I can only encourage you to try openrc.
rolfie
Mate 1.20.4 from the Devuan repository.
Rolfie
sudo apt -t beowulf-backports install linux-image-amd64
Should also work and provide automatic kernel updates.
Kernel:
apt list linux-image-5*
apt install linux-image-5.10.0-0.bpo.3-amd64Firmware:
apt list firmware-linux-nonfree* -a
apt -t beowulf-backports install firmware-linux-nonfreeWhat happens on
apt full-upgrade?
rolfie wrote:The main repo is missing.
http://deb.devuan.org/merged beowulf main contrib non-freeConsider if you need to complie packages. If not, disable the deb-src lines.
What does non-free mean in this context? Licenses other than GPL, MIT, and their kin?
Have a read: https://www.debian.org/intro/free.en.html
non-free means code that is propriatry. Unfortunately you will need non-free stuff to get your tg3 working.
Same with me and my AMD GPUs.
rolfie
Actually your post is off topic, you would have better written a new post.
Read https://www.devuan.org/os/packages
rolfie
The problem is also present in a fresh install based on Beowulf 3.0.0 netinstall in VBox. Same procedure used as for the 3.1.0 install, only difference is runit on 3.1.0 and openrc on 3.0.0.
I guess there must be a bug somewhere in Mate. Strangely enough my workstation is fine.
rolfie
You are missing a quote before the print command. Use copy/paste.
rolfie
Just done a Mate install from 3.1 in VBox, can confirm that that installation forgets the picture from the home folder.
rolfie
There should be no difference in the Mate desktop if I update an older 3.0 install or do a fresh install from 3.1 when using the same init.
Beowulf 3.0 install with Mate dated June 2020, amd64 with backports kernel 5.9, up to date:
Just added a picture from my home folder as background: survives changing the background and a reboot.
rolfie
Here is an example regarding ASCII with Mate desktop: https://dev1galaxy.org/viewtopic.php?id=1952
Maybe this helps.
rolfie
cat /etc/apt/sources.list # # deb cdrom:[Devuan GNU/Linux 3.0 (beowulf) amd64 - desktop 20200526]/ beowulf contrib main non-free # deb cdrom:[Devuan GNU/Linux 3.0 (beowulf) amd64 - desktop 20200526]/ beowulf contrib main non-free # A network mirror was not selected during install. The following entries # are provided as examples, but you should amend them as appropriate # for your mirror of choice. # deb http://deb.devuan.org/merged beowulf-security main deb-src http://deb.devuan.org/merged beowulf-security main # beowulf-updates, previously known as 'volatile' # A network mirror was not selected during install. The following entries # are provided as examples, but you should amend them as appropriate # for your mirror of choice. # deb http://deb.devuan.org/merged beowulf-updates main deb-src http://deb.devuan.org/merged beowulf-updates main1. Got any other sources I should use (mirrors, for instance), and if so can you tell me why (or point me towards something that will tell me what and why)?
The main repo is missing.
http://deb.devuan.org/merged beowulf main contrib non-free Consider if you need to complie packages. If not, disable the deb-src lines.
2. Got anything to read RE mirrors and how that helps me or Devuan in general?
Scan through https://www.devuan.org/. There is a lot of useful information.
During the upgrade (which was blessedly fast and simple compared to Windows 10), I noticed this:
/etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64 W: Possible missing firmware /lib/firmware/tigon/tg3_tso5.bin for module tg3 W: Possible missing firmware /lib/firmware/tigon/tg3_tso.bin for module tg3 W: Possible missing firmware /lib/firmware/tigon/tg3.bin for module tg3A search indicates it could prevent network cards from working after reboot. If that's an issue, the same says that I need to add non-free to my sources.
https://thespecter.net/blog/technology/ … odule-tg3/Going back to the link rolfie posted:
Note that all software shipped with Devuan in the main component is free software. But if needed, non-free software is also available. Just add the non-free and contrib components to the appropriate line(s) in /etc/apt/sources.list like this:
deb http://deb.devuan.org/merged beowulf main non-free contrib
Is there any way to specify that I only want certain software from a specific source? I do a lot of emulation and rom-hacking stuff, and the authors of programs for such love to require the latest stable versions for compilation.
Enabling contrib non-free does not mean everything in there is installed automatically. You have to install packages from non-free explicitely to have them available. Once they are installed they are maintained automatically. Example:
apt install firmware-linux-nonfreeYou may also install non-free packages, and then disable the non-free section in the sources.list again. Your choice. But then the stuff is no more updated.
How would I add package sources from debian while restricting it to the subsets that don't require things that are forbidden in devuan?
This is not recommended at all.
Where can I see the list of packages that are forbidden?
Look for "Banned packages" on the Devuan web page.
rolfie
I am directly booting the iso into the VM. Beowulf 3.1.0 with runit is up and running on cli level in the VM now.
Found a solution. When playing around with various isos I had available I realised that the latest Bullseye download did boot in efi mode, whilst all Devuan isos didn't. Looked at the difference, and found that the Debian stuff has an EFI folder in the iso.
Extracted the 3.1.0 iso, added the EFI folder from Bullseye, and burnt it with brasero to a new iso. That now boots into VBox.
Is that something to consider for Devuan too?
rolfie
I know the effect that most distros end up in the efi shell after being switched off once. And I know the workarounds. Also I would claim VBox has improved the efi support a bit recently, its not only Arch which is starting automatically now. Or it may be related to the fact that I created a file in the efi shell that simulates the nvram (can't remember the name out of the top of my head, need to look it up).
In my case I even can't get the installer iso to boot in efi mode. I searched through FS0: but couldn't find any grubx64.efi or any efi file. Which file starts the installer in efi mode?
rolfie
Edit: on a bootable Beowulf memory stick that I think was created from the 3.0.0 DVD an EFI directory is present containing a BOOTX64.efi, which I do not find in FS0:, BLK1: or BLK2:.
Downloaded the netinstall and the server isos to play a bit with the runit setup in a VBox VM.
Both boot up fine when in BIOS mode, with the efi setup I end up in the efi shell. This also happens with the 3.0.0 netinstall image.
I am running 6.1.18 on Beowulf/Mate. Another install a few days ago worked in efi mode.
Is there something wrong with the isos or is my VBox suddenly screwed? How can I start the iso manually from the efi shell?
rolfie
Well, you need to polish your sources.list. Have a read: https://www.devuan.org/os/packages
rolfie
Most likely a matter of user rights and policies. Maybe related to elogind?
Are you on Beowulf? Which desktop, how do you start? How did you get there? Upgrade from ASCII, fresh install?
rolfie
The path issue with su is not a Devuan topic but coming down from the Debian side of things. Get used to this. Also there are hints in the Release Notes how to handle the issue on your own.
Rolfie
Alternative solution:
download VBox directly from Oracle including the extension pack, copy the Buster .deb file to /tmp and install it with dpkg -i.
rolfie
Read https://www.devuan.org/os/packages.
apt -t beowulf-backports install packageToo bad, I am stuck here. You definitely need the elogind versions of these packages for mate desktop to work correctly.
That command did the job for me a while ago. Maybe one of the real Linux gurus can help.
Sorry that I could not help to fix this, rolfie
Edith: That problem with consolekit/elogind came up with ASCII, finally found the original post about that problem: https://dev1galaxy.org/viewtopic.php?id=1952