You are not logged in.
apt has a progress bar. Perfect for me, I am using apt since many years now, no complaints about it.
You must have omitted upgrading for quite a while.
Nevertheless, good luck for a new approach.
@RedGreen925 and @delgado:
Have you digested the OP's = the_edge123 input correctly?
My sources.list refers to stable.
During the last update, the packages were upgraded but/etc/devuan_version
still contains daedalus.
We are on Devuan here, not on Debian. Daedalus = Stable, Excalibur = Testing!!! I am sorry, you are both on the wrong track.
@Fabien: I am pretty sure you do not have Excalibur on your PC. You are on Daedalus still. The output is correct.
You may check with a
cat /etc/os-releaseWhen you want to upgrade to Excalibur, make sure your Daedalus is up-to-date. Then run
apt install usrmergeThen change your sources.list to excalibur.
Some reading: https://www.devuan.org/os/releases
Again: You never have upgraded to Excalibur if your sources.list refers to "stable".
My sources.list refers to stable.
For Devuan stable still is Daedalus. If you want to upgrade to Excalibur, change your sources.list to excalibur instead of stable.
I think so.
... you did install usrmerge before updating ...
There will be some complaints within the upgrade process if that wasn't done.
Is Devuan in process of putting this update into the Daedalus repos?
Definitely not. The Daedalus repo will only be updated if there is an update coming from the Debian repo.
Devuan is Debian w/o systemd, only parts that have relation to systemd are replaced or modified.
Anyhow, if I read the document correctly the main fix is an bios update.
kernel is 4.19.-27
Linux devuan 4.19.0-27-amd64
however there are no correspondent linux-headers available in the repo
I think that is not really true. From:
https://pkginfo.devuan.org/cgi-bin/poli … *&x=submit
linux-headers-4.19.0-27-common - 4.19.316-1
http://deb.devuan.org/merged beowulf-security/main amd64
http://deb.devuan.org/merged beowulf-security/main i386
http://deb.devuan.org/merged beowulf-security/main arm64They are available, but not in the main section, you have to enable security!
Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Found Devuan GNU/Linux 5 (daedalus) on /dev/nvme0n1p2 Found Arch Linux (rolling) on /dev/nvme0n1p3 Adding boot menu entry for UEFI Firmware Settings ...
This shows that os-prober is executed and finds Arch. And what is normal for any uefi system, adds an entry to access the uefi bios.
You should see Arch in the grub menu as selectable option.
Installed a Daedalus VM, encrypted with LVM, efi based, Lightdm and Cinnamon with German locale and Keyboard. Installation works, Lightdm is set to US keyboard, Cinnamon too. Adding a German keyboard works until reboot, then the system is back to US. Is that worth an issue? I think yes?
Edith: the screensaver login allows to switch the keyboard to German, the login doesn't.
From https://unix.stackexchange.com/question … rrupt-irq7
"Classically, the default usage of IRQ 7 is for the (essentially obsolete) parallel port (also known as IEEE 1284 or LPT)..."
Use the search machine of your least mistrust to find some more info.
Just pulled out my travelling laptop again.
apt update works fine w/o backports. Re-enabling the standard "deb http://deb.devuan.org/merged" backports throws a "Release file not found" error. Starngely enough it works with "deb http://archive.devuan.org/merged".
I have seen something in a German portal that you can configure NM to leave the resolv.conf alone.
You simply may need a new version for Debian 13 Trixie.
NetworkManager shouldn't affect /etc/resolv.conf, /etc/hosts or any of these files, except, unfortunately, the /etc/resolv.conf file.
Please read again, you see the discrepancy?
NetworkManager WILL affect the /etc/resolv.conf and take it out of the loop. Thats why I omit using NetworkManager on my workstation. On my small home network I am using static addressing.
I am using a Kyocera P6230 LAN printer with a PPD supplied by Kyocera. Before that I owned a FS-5100DN.
non-free is missing.
Just updated my laptop which is still running Chimaera for a reason, and I saw that no release file is present for backports anymore.
Why is Chimaera backports removed? Why is Chimaera different from e.g. Beowulf where backports still is present in the archive?
Sorry, you seem to have a silly idea how Devuan works. Even if the Debian 11 Bullseye backports is archived in Debian, it does not mean it will be archived in Devuan Chimaera. Though stopping support for Bullseye backports in Debian means that there will be no new packages coming in from Debian any more for that release.
Kyocera also is a possible choice.
what about chimaera-backports in archive.devuan.org?
Chimaera isn't yet archived.
Have a look at https://www.devuan.org/. Chimaera is oldstable, but not yet archived.
I do either one depending on the situation. If there is reason to resize partitioning, or significant changes in my setup like another init system, another desktop, I prefer fresh install. But I have also performed various dist-upgrades since I started to have Debian on my workstation starting with Squeeze.
So I mount ISO and then use general path instead of pointing on every directory of it?
No. Do NOT mount the iso. I assume you have the iso as a file in your Download directory. You cp the file, or dd it to the USB.
You do:
# cd /home/$USER/Download
# cp iso.file.spec /dev/sdxBTW: you could also use the netinstall. The installers on the netinstall the CD and the DVD are exactly the same. The amount of SW coming with the media are different.