Choosing Better Alternatives Amid Confusing Policies
news.opensuse.org
A recent back-and-forth on Windows 11’s hardware requirements and the end-of-life timeline for Windows 10 leaves millions of users frustrated and uncertain a...

The case for Linux and openSUSE is clear. Linux provides viable, cost-effective and sustainable alternatives. Users can enjoy a free, open-source operating system that doesn’t require costly upgrades or restrictive hardware requirements with installing openSUSE. Here are a few things users that want to transition can consider:

  • Complete Transparency: Linux distributions like openSUSE are governed by open-source principles, ensuring clear and consistent development.
  • No Forced Obsolescence: openSUSE supports a wide range of hardware like modern machines to older PCs that allow users to extend the life of their devices.
  • Cost Savings: openSUSE is free to use, with no licensing fees or hidden subscription costs for extended support.

By switching to Linux, users can help combat e-waste as every PC saved from a landfill is a win for the environment.

  • not_amm@lemmy.mlEnglish
    3·
    5 days ago

    Hey, may I ask how has it been MicroOS for you? I’m interested in using it for my small server and self-hosting, but I mostly use containers with Docker and I’ve seen that MicroOS comes with Podman by default.

      • not_amm@lemmy.mlEnglish
        1·
        5 days ago

        Will do, thanks!. Have you used something like Docker Compose? I didn’t have a lot of time before, but I’m still researching and I don’t get what is the “standardized” way of dealing with composed containers

        • NanoooK@sh.itjust.works
          2·
          3 days ago

          I have never used Podman Compose but it exists. I guess it’s really similar to docker compose.

          With podman you can use “Quadlets”, which are systemd files allowing the services to integrate very well with the system (you can use journalctl to see the logs of a container).

             Podman  supports  building,  and starting containers (and creating vol‐
  umes) via systemd by using a systemd generator.  These files  are  read
  during boot (and when systemctl daemon-reload is run) and generate cor‐
  responding  regular  systemd  service  unit files. Both system and user
  systemd units are supported.  All options and tables available in stan‐
  dard systemd unit files are supported. For example, options defined  in
  the  [Service]  table and [Install] tables pass directly to systemd and
  are handled by it.  See systemd.unit(5) man page for more information.

  The Podman generator reads the search paths above and reads files  with
  the  extensions  .container  .volume, .network, .build, .pod and .kube,
  and for each file generates a similarly named .service file.
          • not_amm@lemmy.ml
            1·
            1 day ago

            I’ve been reading about them, thank you! I’ll test them in a VM soon, I find it weird to use systemd, but I guess if it works… I hope I get a new PC this month so I can transition distros and storage easily.

    • rodbiren@midwest.socialEnglish
      1·
      5 days ago

      I ended up installing docker. Didn’t want to make a bunch of systemd files. It automatically updates each day and has required almost no maintenance at all. It’s a little strange, but can work great.

      • not_amm@lemmy.ml
        1·
        1 day ago

        I already use Docker, but in rootless mode, which works kind of weird. I wouldn’t say I’m obsessed, but I like to go by example and implement all the best practices and zero trust in my own devices, since I’m studying cybersecurity:)