Wie kann ich in /etc/network/interfaces in #Debian es einstellen, dass auf allen Interfaces #DHCP gemacht wird, auch wenn ich jetzt noch nicht weiß, wie das Interface in Zukunft heißen wird?
Jetzt steht da halt:
iface enp1s0 inet dhcp
Aber auf einer anderen Hardware heißt das Ding ja vielleicht eth0 statt enp1s0...
Also was tun?
Brauch ich ein Startupscript, dass die Config generiert?
Ubuntu 22.04 (LTS) is also critically broken. Example: Depending on your storage configuration IO performance can be 100x worse when compared to an unpatched mainline kernel. (dsync when using mdraid 5 or 6 on NVMe)
I gave up because pipx refuses to install urwid, and I think Debian's version is drumroll way too old. ;)
I wish pipx just had scli. There's an scli package in PyPI, but it's literally an empty placeholder for nothing.
Infuriating.
The funny part about the removal of networking from the default #keepassxc package on #debian, is that they did it for "security" reasons, without thinking that the MOST INSECURE way to transfer a #password to your #browser is via the CLIPBOARD. Absolutely every running app or service can read the clipboard! And yet, that's the default way they expect users to do it now!
🌀 16 years of CVE-2008-0166 - Debian OpenSSL Bug
— 16years.secvuln.info
"A patch in Debian's and Ubuntu's OpenSSL packages broke the random number generator, effectively limiting the number of possible keys to a few ten thousand plausible variations"
@passthejoe I've tried using Guix a few times. It makes a lot of sense to me as a system you can spin up by specifying a few parameters in a deployment management script. It seems less suited for a personal desktop system that I'd work with daily.
Try #guix on Debian as a package manager: this will let you figure out if the packages you need are there.
I really like the shell feature of Guix: you can very easily deploy virtual environments for any language/tool--think of Docker without any of the complexities.