• 2 Posts
  • 57 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle











  • The main “instability” I’ve found with testing or sid is just that because new packages are added quickly, sometimes you’ll have dependency clashes.

    Pretty much every time the package manager will take care of keeping things sane and not upgrading a package that will cause any incompatibility.

    The main issue is if at some point you decide to install something that has conflicting dependencies with something you already have installed. Those are usually solvable with a little aptitude-fu as long as there are versions available to sort things out neatly.

    A better first step to newer packages is probably stable with backports though.

    https://backports.debian.org/





  • Stability is no longer an advantage when you are cherry picking from Sid lol.

    This makes no sense. When 95% of the system is based on Debian stable, you get pretty much full stability of the base OS. All you need to pull in from the other releases is Mesa and related packages.

    Perhaps the kernel as well, but I suspect they’re compiling their own with relevant parameters and features for the SD anyway, so not even that.




  • I don’t think I’ve ever come across a DNS provider that blocks wildcards.

    I’ve been using wildcard DNS and certificates to accompany them both at home and professional in large scale services (think hundreds to thousands of applications) for many years without an issue.

    The problem described in that forum is real (and in fact is pretty much how the recent attack on Fritz!Box users works) but in practice I’ve never seen it being an issue in a service VM or container. A very easy way to avoid it completely is to just not declare your host domain the same as the one in DNS.