You are not logged in.
Thank you very much. Now nothing is displayed anymore:
root@wm-1:~# dpkg -l | grep systemd
root@wm-1:~#One more question: How can I ensure that systemd is no longer present?
Here is an output:
dpkg -l | grep systemd
ii systemd-standalone-sysusers 257.9-1~deb13u1 amd64 standalone sysusers binary for use in non-systemd systemsIs this OK?
Thank you very much. I still have Trixie on one computer. I set up sources.list, deleted debian.sources, and migrated to Excalibur according to the instructions. Everything seems to be OK.
The sources.list has been removed from Debian. Instead, there is now
/etc/apt/sources.list.d/debian.sources
How does this work in Devuan?
Is /etc/apt/sources.list still used?
Ah, right. Thank you!
Hello everyone,
I have Daedalus. The meta-package linux-image-amd64 is on the computer and therefore the current kernel 6.1.0-28-amd64. Now I saw that there is also the kernel 6.11.5+bpo-amd64-unsigned. I installed it and no problems occurred. As far as I can see, the kernel is not updated by upgrades. The linux-image-amd64 meta-package does not do this. Do you know of a way to always update to the latest kernel with a simple dist-upgrade?
Does anyone know anything current about Heads?
Will heads be further developed or is it better to use Tails?
Addendum: I found something about Heads here:
Index » Devuan Derivatives » heads linux: https://dev1galaxy.org/viewtopic.php?id=4761
I have always been very satisfied with Heads. But now I have concerns because safety can no longer be based on current knowledge.
Hi ralph.ronnquist,
I wouldn't have thought of anything like that. That solved my problem! Thank you very much.
Addendum:
I have uninstalled Connman. Because I use KDE Plasma almost exclusively, I have installed plasma-nm, which accesses the network manager. Yes, that's certainly not the purist option, but it's convenient for me and it works. However, I will actually have to deal with ifupdown, wpa_supplicant and wpagui. Yes, I'm also thinking about the man interfaces ;-)
Hi ralph.ronnquist,
I use connman. Do you think this is the Problem? Is it better to use network-manager or wicd?
Hi rolfie,
you say: "That means you are not resolving anything - localhost". But why does it work with us.deb* and de.deb*? And why do I get to other pages on the net? Aren't nameserver ::1 and nameserver 127.0.0.1 just the placeholder for the ISP's IP address assignment?
Hi em-777,
This is the Google DNS server ...
For me here:
cat /etc/resolv.conf
# Generated by Connection Manager
nameserver ::1
nameserver 127.0.0.1I replaced deb.devuan.org in the sources.list with us.deb.devuan.org and this is the result:
apt-get update
OK:1 http://us.deb.devuan.org/merged daedalus InRelease
OK:2 https://packages.mozilla.org/apt mozilla InRelease
OK:3 http://us.deb.devuan.org/merged daedalus-updates InRelease
OK:4 http://us.deb.devuan.org/merged daedalus-security InRelease
OK:5 http://us.deb.devuan.org/devuan daedalus-proposed-updates InRelease
OK:6 http://us.deb.devuan.org/merged daedalus-backports InRelease
Paketlisten werden gelesen… FertigThere are no problems.
I replaced deb.devuan.org in the sources.list with de.deb.devuan.org and this is the result:
apt-get update
OK:1 http://de.deb.devuan.org/merged daedalus InRelease
OK:2 http://de.deb.devuan.org/merged daedalus-updates InRelease
OK:3 http://de.deb.devuan.org/merged daedalus-security InRelease
OK:4 http://de.deb.devuan.org/devuan daedalus-proposed-updates InRelease
OK:5 http://de.deb.devuan.org/merged daedalus-backports InRelease
OK:6 https://packages.mozilla.org/apt mozilla InRelease
Paketlisten werden gelesen… FertigNo problems here either.
And I can also access http://de.deb.devuan.org/ with the browser without any problems.
Hi chris2be8, thank you. This is what it looks like:
host deb.devuan.org
deb.devuan.org has address 185.38.15.84
deb.devuan.org has address 141.84.43.19
deb.devuan.org has address 147.78.194.22
deb.devuan.org has address 125.228.189.120
deb.devuan.org has address 185.178.192.43
deb.devuan.org has address 190.64.49.124
deb.devuan.org has address 67.219.104.166
deb.devuan.org has address 131.188.12.211
deb.devuan.org has address 95.216.15.86
deb.devuan.org has address 198.58.118.8
deb.devuan.org has address 195.85.215.180
deb.devuan.org has address 103.146.168.12
deb.devuan.org has address 130.225.254.116
deb.devuan.org has address 94.16.114.15
deb.devuan.org has address 185.236.240.103
deb.devuan.org has address 46.4.50.2
deb.devuan.org has address 5.161.180.234
deb.devuan.org has address 160.16.137.156
deb.devuan.org has address 106.178.112.231
deb.devuan.org has address 185.183.113.131
deb.devuan.org has address 200.236.31.1
deb.devuan.org is an alias for deb.rr.devuan.org.ping deb.devuan.org
ping: deb.devuan.org: Temporärer Fehler bei der NamensauflösungEnglish: Temporary error during name resolution
Browser: http://deb.devuan.org/
Seite wurde nicht gefunden
Die Verbindung mit dem Server deb.devuan.org schlug fehl.
English: Page was not found
The connection to the server deb.devuan.org failed.
Strange and difficult for me.
My transmission has also become slow. Maybe that's a problem with us. I mean here in Germany in Weil der Stadt.
Hi rolfie, how can i check if my DNS is working alright? Just a keyword, I can then continue searching myself.
Addendum: I get to devuan.org excellently and the answer is fast. But the subdomain deb.devuan.org refuses to work for me.
ping: http://deb.devuan.org: The name or the service is not known
ping: https://deb.devuan.org: The name or the service is not known
ping: deb.devuan.org: Temporary error during name resolution
Hi Ron, you're luckier than me. It looks like this for me at the moment (German language setting):
root@rechner:~# apt update
OK:1 https://packages.mozilla.org/apt mozilla InRelease
Ign:2 http://deb.devuan.org/merged daedalus InRelease
Ign:3 http://deb.devuan.org/merged daedalus-updates InRelease
Ign:4 http://deb.devuan.org/merged daedalus-security InRelease
Ign:5 http://deb.devuan.org/devuan daedalus-proposed-updates InRelease
Ign:6 http://deb.devuan.org/merged daedalus-backports InRelease
Ign:2 http://deb.devuan.org/merged daedalus InRelease
Ign:3 http://deb.devuan.org/merged daedalus-updates InRelease
Ign:4 http://deb.devuan.org/merged daedalus-security InRelease
Ign:5 http://deb.devuan.org/devuan daedalus-proposed-updates InRelease
Ign:6 http://deb.devuan.org/merged daedalus-backports InRelease
Ign:2 http://deb.devuan.org/merged daedalus InRelease
Ign:3 http://deb.devuan.org/merged daedalus-updates InRelease
Ign:4 http://deb.devuan.org/merged daedalus-security InRelease
Ign:5 http://deb.devuan.org/devuan daedalus-proposed-updates InRelease
Ign:6 http://deb.devuan.org/merged daedalus-backports InRelease
Fehl:2 http://deb.devuan.org/merged daedalus InRelease
Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
Fehl:3 http://deb.devuan.org/merged daedalus-updates InRelease
Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
Fehl:4 http://deb.devuan.org/merged daedalus-security InRelease
Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
Fehl:5 http://deb.devuan.org/devuan daedalus-proposed-updates InRelease
Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
Fehl:6 http://deb.devuan.org/merged daedalus-backports InRelease
Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Alle Pakete sind aktuell.
W: Fehlschlag beim Holen von http://deb.devuan.org/merged/dists/daedalus/InRelease Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
W: Fehlschlag beim Holen von http://deb.devuan.org/merged/dists/daedalus-updates/InRelease Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
W: Fehlschlag beim Holen von http://deb.devuan.org/merged/dists/daedalus-security/InRelease Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
W: Fehlschlag beim Holen von http://deb.devuan.org/devuan/dists/daedalus-proposed-updates/InRelease Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
W: Fehlschlag beim Holen von http://deb.devuan.org/merged/dists/daedalus-backports/InRelease Temporärer Fehlschlag beim Auflösen von »deb.devuan.org«
W: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt.What's going on? Since yesterday I get errors (Temporary failure resolving deb.devuan.org) and the sources are ignored. I probably just have to wait, right?
Here is my sources.list:
deb http://deb.devuan.org/merged/ daedalus main contrib non-free non-free-firmware
deb-src http://deb.devuan.org/merged/ daedalus main contrib non-free non-free-firmware
#Updates
deb http://deb.devuan.org/merged/ daedalus-updates main contrib non-free non-free-firmware
deb-src http://deb.devuan.org/merged/ daedalus-updates main contrib non-free non-free-firmware
#Security
deb http://deb.devuan.org/merged/ daedalus-security main contrib non-free non-free-firmware
deb-src http://deb.devuan.org/merged/ daedalus-security main contrib non-free non-free-firmware
#Proposed-Updates
deb http://deb.devuan.org/devuan/ daedalus-proposed-updates main contrib non-free
deb-src http://deb.devuan.org/devuan/ daedalus-proposed-updates main contrib non-free
#Backports
deb http://deb.devuan.org/merged/ daedalus-backports main contrib non-free non-free-firmware
deb-src http://deb.devuan.org/merged/ daedalus-backports main contrib non-free non-free-firmwareThat can't be a solution either. Devuan is not the worst choice. I'm sticking to it. The malicious code never made it into stable. Security just needs to become more important in the future. The attacks will get much better. You have to be prepared for that.
The malicious code arrived in Testing and Unstable. If it recognized that it had landed on a system that does not work with systemd, it did nothing. But it was still there. This is an obvious security problem. Malicious code lurking in the system. Nobody can say if, how and when it can become active and cause damage. Thank God it has been found. But that should be a lesson to us. Security will have to become more important in the future.
And for the German speakers here, an interesting publication - also in relation to systemd:
https://dnip.ch/2024/04/02/xz-open-sour … wtab-de-de
Perhaps there is someone here who can evaluate systemd against this background.
Good morning everyone, due to the unpleasant incidents with xz / liblzma, I have the feeling that a "Security" section is missing here in the forum. There are News & Announcements, Forum Feedback, Support etc., but "Security" is missing. Or have I overlooked something? What do you think?
This publication is also interesting for Devuan because it may confirm Devuan's philosophy:
https://www.wired.com/story/jia-tan-xz-backdoor/
Here is a timeline of what happened:
https://research.swtch.com/xz-timeline
Take a look at this:
So far, I have found everything I need at Devuan.
OK, I'll just keep working with Devuan and trust the people who do it.