Points for something I’ve never tried.

Edit: Think I’ll just blast Bazzite on it. The recent Gnome scales well and it has nice performance tweaks.
Cheers

    • Reygle@lemmy.worldOP
      4·
      6 days ago

      Okay this looks kinda neat, but the page says it “isn’t available for public use yet”? More of a DE/tweak than a distro?

    • TunaLobster@lemmy.world
      2·
      6 days ago

      I am annoyed by the weird UX differences between Kodi and Jellyfin. I really want this to be a thing. I’ve got an N100 box running libreelec right now. I really want Bigscreen to work on x86. Just need to have patience.

  • snroh@lemm.ee
    2·
    5 days ago

    I tried using bazzite as a media PC and gave up after a couple of days, this isn’t even remotely something I want in my household.

    try it on fast hardware and make up your own mind. good luck!

    p.s.: plasma bigscreen isn’t available for public use and kodi and its derivatives should be tossed in the deepest volcanoes we got.

  • crawancon@lemm.ee
    2·
    6 days ago

    I would have thought open/libreElec would have worked.

    other mentionables centered around media are AVLinux , Ubuntu studio, and dynebolic.

    • sic_semper_tyrannis@lemmy.todayEnglish
      1·
      6 days ago

      Batocera is nice too. It’s half an emulation console and half Kodi. You can tell it to launch Kodi as default too. Whereas LibreElec is only Kodi with a limited gaming ability

    • madame_gaymes@programming.devEnglish
      4·
      6 days ago

      I daily drive NixOS and use it in many other situations. However, I’m also a systems engineer and it’s the distro I use for managing all the environments.

      I’m sure it was a joke(ish), but definitely not for the light-hearted or fairweather penguins.

        • madame_gaymes@programming.devEnglish
          1·
          6 days ago

          I can’t tell if you’re being serious or facetious 😅

          I assure you it isn’t all that glorious, though, just a lot of configs. NixOS is just my favorite method of infrastructure-as-code, and in conjunction with nixops I can’t imagine going back to anything else unless the project required it for some reason. Disaster recovery is simple, and testing/pushing config changes to hundreds of machines is almost too easy.

          I have a clunky set of configs, for self-hosting at home and small side-clients, I slapped together you can look at, but again it’s not all that special and I wouldn’t necessarily follow this for real production stuffs. It also doesn’t utilize any of the fancy NixOS stuff, fairly basic and Docker heavy.

          https://codeberg.org/madamegaymes/NixOS-Docker-Framework

          • marauding_gibberish142@lemmy.dbzer0.comEnglish
            1·
            6 days ago

            I am serious. I am a cloud engineer (glorified system admin for cloud + Linux VMs) and I’m still stuck on Ansible + Terraform (stuck isn’t the right word, we are a RHEL and Alpine shop for our VMs and Containers and things work well enough). My friends in bigger companies are using Nix though, but I was always scared of the learning curve. I want to see clear benefits of using nix so I can push myself to actually learn it, which is why I asked. Thanks for the link.

            • madame_gaymes@programming.devEnglish
              2·
              6 days ago

              Oh, sweet!

              In that case, I highly recommend taking a look at some more real-world examples. My original link is just something that makes self-hosting and small jobs more or less thoughtless for me.

              Imagine all those config management tools built into your OS, and that’s NixOS in a nutshell. There’s obviously WAY more it can do if you look into creating your own derivations, or getting into the new-ish concept of Flakes.

              Again, though, nixops is the thing that makes me continue to use it, besides just already knowing how to throw together a config in nix’s syntax. The nixops tool basically allows you to federate all your systems, tag them, group them, and do anything under the sun with each machine (or several in batches). It’s hard to get across in a simple text blurb.

              In my case (SaaS), imagine having 10 devs that all want their own dev environment that mirrors production within our VPN, then you need a beta and production environment for each client that licenses the app. Each environment has a couple databases, a few different APIs, some background scraper-type applications, and front-ends for everything. Some of that stuff can live on one machine, some needs to be alone and redundant. You can see how very quickly there’s a lot of machines to keep track of.

              Now I need to update a couple config pieces to match a new feature in the app itself. Well, all I gotta do is sort out the config, then run a couple nixops command to push to all the dev environments. When ready, do the same for beta, then do it for prod when the fat lady sings.

              Being all within one ecosystem, focused on security hardening, is what I really like about it. Hopefully that wasn’t too stream-of-consciousness for ya, lmao.

              ETA: links, also note that nixops is undergoing some serious changes in the past year. NixOS itself also undergoes changes fairly regularly in syntax as vulnerabilities are addressed and improvements made.

              • marauding_gibberish142@lemmy.dbzer0.comEnglish
                3·
                6 days ago

                Thank you for the note. I’m been cursing myself for not being able to provide my devs with something similar (they don’t complain but I know it will make their lives easier). I will start nix from scratch if I learn it but nixops definitely seems like it can help because terraform isn’t that great at the example you provided. Thanks.

                focused on security hardening

                Could you elaborate?

                • madame_gaymes@programming.devEnglish
                  2·
                  6 days ago

                  Some NixOS native packages and options change the defaults to be more security conscious rather than “easy to spin up.” Doing a basic nginx config in NixOS will be more secure than if you had installed it through debian’s apt or from source. Similar for ssh, you just don’t have to think as much about doing those few obvious config changes you always have to do when spinning up a new machine. Of course, there are some things you have to customize for yourself (like custom ports, paths, etc.), but they make it a little simpler by assuming you’re using NixOS in a production environment.

                  A couple of other links that you’ll end up referencing all the time if you get into NixOS:

                  The first link is the native package repo, and the second link are all the NixOS config parameters for each of those packages and the system in general.

                  they don’t complain but I know it will make their lives easier

                  Perfect. So when you do provide them with an efficiency boost when they never asked about it, you can be a rockstar and get a raise. Or keep it in your back pocket until they do complain and implement it then for a similar effect 😜

    • Reygle@lemmy.worldOP
      3·
      6 days ago

      Nix looks like a fun way to wild away 3 weeks, not entirely sure this is what I’m after for a living room TV box. :D

  • the_weez@midwest.social
    1·
    6 days ago

    https://libreelec.tv/ If you like Kodi this is the business. I have had it working with remotes, the biggest drawback for me was streaming services not supporting 4k on the Odroid N2+ I was trying to use. Plex worked great through Kodi, and that was my biggest use case.

    • Reygle@lemmy.worldOP
      0·
      6 days ago

      I’m a Plex guy so that part is appealing but I admit I mostly watch youtube in this scenario

      • the_weez@midwest.social
        0·
        6 days ago

        Yeah, I’m not sure how well YouTube is going to run on Kodi, I’ve never actually tried it. If you have another Linux box around you could install Kodi and try it pretty quickly.

  • pastermil@sh.itjust.works
    11·
    6 days ago

    I got openSUSE Leap. It’s stable and reliable. My complaint is that I needed to go thru all the hoops to get all the media codecs I need to play what I want.

      • pastermil@sh.itjust.works
        1·
        5 days ago

        Honestly, I picked it because I was lazy. It’s such a low maintainance machine. As for the codec, the flatpak version of VLC does it.

  • Ulrich@feddit.orgEnglish
    15·
    6 days ago

    Linux pretty much just doesn’t work on TV. No platforms have Linux support, unfortunately.

    Bazzite, Chimera, Nobara all have a pretty sweet SteamOS-like distro, if you’re after gaming and have AMD GPU.

    • madame_gaymes@programming.devEnglish
      4·
      6 days ago

      I think you misunderstood, hence the downvotes.

      OP is asking what a good distro is for a media center PC, as in the PC’s video output will be connected to the TV’s video input. At which point Linux does not give two shits.

      Sounds like you thought they wanted to stream/cast via some TV app or something, but that just sounds like a nightmare and I’m not sure that anyone would even want to try to do that. Just run Linux and use the TV as a big monitor, be done with smart TV garbage.

      • Ulrich@feddit.orgEnglish
        110·
        6 days ago

        I didn’t misunderstand anything. The downvotes are just from salty Linux users who think piracy tools are a direct replacement for streaming services.

        A media center is nothing without streaming apps.

    • 4am@lemm.ee
      42·
      6 days ago

      Linux doesn’t work on TV

      proceeds to name 3 distros that not only work but do gaming

      My brother in Christ…

      • Ulrich@feddit.orgEnglish
        15·
        6 days ago

        I mean could have just read the next sentence and that would have cleared up your confusion…

        • zenpocalypse@lemm.eeEnglish
          2·
          6 days ago

          The next sentence that incorrectly implies AMD is at all a necessity for those distros?

          • Ulrich@feddit.orgEnglish
            11·
            6 days ago
            1. That’s not what I said.
            2. That would not be the next sentence. Try again.
            • zenpocalypse@lemm.eeEnglish
              2·
              6 days ago

              It was the next sentence after the list of distros referenced in the response to you, and it is still very misleading at best.

              But, yeah, the second sentence. There’s a huge difference between an HTPC and an Amazon stick, Roku, or “smart” TV.

              Those have apps and must be supported by “platforms” because they are limited hardware with a limited OS.

              YouTube and Netflix don’t need to “support” Linux any more than they need to support Windows for an HTPC.

              If that’s not what you’re saying, you’ll probably want to elaborate because I expect there are plenty of readers giving your comment a “wha…?”

              • Ulrich@feddit.orgEnglish
                23·
                6 days ago

                It was the next sentence

                You’re just lying. And I don’t know why because everyone can see it. You’re not fooling anyone and you’re not accomplishing anything.

                There’s a huge difference between an HTPC and an Amazon stick, Roku, or “smart” TV.

                Yes there is, in that a PC is much more versatile. But streaming services are a basic function of HTPC.

                YouTube and Netflix don’t need to “support” Linux any more than they need to support Windows for an HTPC.

                Yes…they do? And they do support Windows.

    • nanook@friendica.eskimo.com
      01·
      6 days ago

      @Ulrich @Reygle There are Android televisions, Android uses a Linux kernel, some of them you can jailbreak, once you get access you can install whatever you like and remove what you don’t.

      • Ulrich@feddit.orgEnglish
        21·
        6 days ago

        Yes but we all know no one talks about Linux and is referring to Android.