• 0 Posts
  • 13 Comments
Joined 3 years ago
Cake day: June 15th, 2023
  • talkingpumpkin@lemmy.worldtoLinux@lemmy.ml•So, I'm a noob and I prefer... Debian?
    7·
    3 days ago

    I actually like Debian’s slow update cycle, as I don’t want to be bothered often with setting up my system again.

    I’ve been there too!

    Updating to a new version is such a chore: you have to follow the news, then wonder how long to wait before updating, then you have to set aside at least a few hours for the actual update (well, for fixing what may go wrong - not that stuff actually goes wrong, but you still set aside some time just in case).

    The solution to this is in the exact opposite direction you’d imagine.

    For a few years (since last time I got a new PC), I’ve been running a rolling distro (tumbleweed *) and… it’s been great: no big updates, just incremental ones.

    If anything breaks (and it never happened to me: there has been times where errors prevented the system to update, but never has it broken on me), you just boot the snapshot before the last update and try again in a few hours/days.

    I want something as close as “set it and forget it” as possible.

    That’s nixos :) It takes a long time to “set” (and you never really finish doing it) but you can switch to a new PC at any time and have your exact system on it (bar what the few things you have to change to account for the different hardware, of course).

    * I hear that with arch&co you actually have to follow the release notes as sometimes there are manual tasks to do - it’s not so in tumbleweed (at least, as much as i know and as far as me experience goes) - IDK about other rolling distros (or debian testing/sid)

  • talkingpumpkin@lemmy.worldtoLinux@lemmy.ml•Why is Debian always left out of the distro recommendations?
    2·
    22 days ago

    I’d say it’s because:

    1. the people who ask for recommendations won’t like (or understand) debian? (it’s just “old packages this” and “outdated that” for most people)
    2. the people who do use and appreciate debian don’t read “I hate windows pls recommend me a distro” posts (or at least don’t reply as often as the <insert popular distro> fanboys)

    And, no, I don’t use debian myself.

    but when I finally switched over to Debian, everything just worked!

    That’s most probably because you learned how to use your system without breaking it in the meantime :)

  • talkingpumpkin@lemmy.worldtoLinux@lemmy.ml•Pros and cons on - and alternatives to - running three separate servers on one single Linux instance using systemd-nspawn
    9·
    22 days ago

    Should I just learn how to use Docker?

    Since you are not tied to docker yet, I’d recommend going with podman instead.

    They are practically the same and most (all?) docker commands work on podman too, but podman is more modern (second generation advantage) and has a better reputation.

    As for passing a network interface to a container, it’s doable and IIRC it boils down to changing the namespace on the interface.

    Unless you have specific reasons to do that, I’d say it’s much easier to just forward ports from the host to containers the “normal” way.

    There’s no limit to how many different IPs you can assign to a host (you don’t need a separate interface for each one) and you can use a given port on different IPs for different things .

    For example, I run soft-serve (a git server) as a container. The host has one “management” IP (92.168.10.243) where openssh listens on port 22 and another IP (192.168.10.98) whose port 22 is forwarded to the soft-serve container via podman run [...] -p 192.168.10.98:22:22).