• 1 Post
  • 42 Comments
Joined 1 year ago
Cake day: June 12th, 2023
  • nottelling@lemmy.worldtoSelfhosted@lemmy.world•How to avoid "things going wrong"? (Immutable distros?)English
    2·
    1 month ago

    The answer to your overarching question is not “common maintenance procedures”, but “change management processes”

    When things change, things can break. Immutable OSes and declarative configuration notwithstanding.

    OS and Configuration drift only actually matter if you’ve got a documented baseline. That’s what your declaratives can solve. However they don’t help when you’re tinkering in a home server and drifting your declaratives.

    I’m pretty certain every service I want to run has a docker image already, so does it matter?

    This right here is the attitude that’s going to undermine everything you’re asking. There’s nothing about containers that is inherently “safer” than running native OS packages or even building your own. Containerization is about scalability and repeatability, not availability or reliability. It’s still up to you to monitor changelogs and determine exactly what is going to break when you pull the latest docker image. That’s no different than a native package.

  • nottelling@lemmy.worldtoSelfhosted@lemmy.world•Confused about PodmanEnglish
    12·
    2 months ago

    Just cause you’ve never seen them doesn’t make it not true.

    Try using quadlet and a .container file on current Debian stable. It doesn’t work. Architecture changed, quadlet is now recommended.

    Try setting device permissions in the container after updating to Debian testing. Also doesn’t work the same way. Architecture changed.

    Redhat hasn’t ruined it yet, but Ansible should provide a pretty good idea of the potential trajectory.

  • nottelling@lemmy.worldtoSelfhosted@lemmy.world•Confused about PodmanEnglish
    2·
    2 months ago

    Every complaint here is PEBKAC.

    It’s a legit argument that Docker has a stable architecture while podman is still evolving, but that’s how software do. I haven’t seen anything that isn’t backward compatible, or very strongly deprecated with notice.

    Complaining about selinux in 2024? Setenforce 0, audit2allow, and get on with it.

    Docker doing that while selinux is enforcing is an actual bad thing that you don’t want.

  • nottelling@lemmy.worldtoNo Stupid Questions@lemmy.world•What is the exact meaning of a misogynist person?English
    574·
    7 months ago

    Or how about, rather than your narrow, specific 3 definitions, a fourth thing, such as how it’s phrased in the wiki:

    Misogyny is hatred of, contempt for, or prejudice against women or girls. It is a form of sexism that can keep women at a lower social status than men.

    The emphasis there is why you’re being called names on the internet. If you’re advocating systems or societal norms of gender oppression, you’re being misogynist. This remains true even if you’re not doing it intentionally.

    The world we live in is deeply patriarchal, so it can be hard to see these problems, because the views and opinions you’ve got are just “normal”. Something being the norm doesn’t mean it isn’t oppressive, and having an opinion doesn’t mean you shouldn’t consider the impacts of that opinion.

    Generally, if someone calls you a misogynist, and you go “bUt I rEsPeCt wOmEn”, you might want to take a little time to figure out where it’s coming from. It can certainly be real without fitting in your 3 tidy little self-serving definitions.

    I’ll also point out that you can replace nearly every instance of misogyny in this thread with racism, and replace women with black, and it would be the same discussion. Or you could swap misogyny/women with misandry/men. Oppression is oppression, no matter who holds the power.