friendica.eskimo.com

Bored. Give me a good "Living room PC" distro

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

This entry was edited (1 day ago)
59 8

Linux pretty much just doesn't work on TV. No streaming 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.

This entry was edited (15 hours ago)
1 34

I think you misunderstood completely, 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.

13
@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.
Yes but we all know no one talks about Linux and is referring to Android.
Linux doesn't work on TV


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

My brother in Christ…

5 3
I mean could have just read the next sentence and that would have cleared up your confusion...
The next sentence that incorrectly implies AMD is at all a necessity for those distros?
  1. That's not what I said.
  2. That would not be the next sentence. Try again.
3

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...?"

"E" - since Buddy is trying to imply I changed my comment after he responded, no. I added clarity within a couple minutes, changing no ideas. Talk about gaslighting with this guy.

This entry was edited (7 hours ago)
2 1
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.

E: the comment above was edited and they continued to double down and argue instead of just admitting that they made a mistake.

This entry was edited (16 hours ago)
1

I'm... lying?

No, it's pretty clear now that you're quite confused about the difference between apps and services.

And they do support Windows.


Oh god, tell me you're not using the windows store apps for these services on a PC. Even my Alpha kids know better than that.

Seriously, how can someone be even a little familiar with Linux and be so wrong about internet services working on Linux?

And your attitude is just... something else.

This entry was edited (20 hours ago)
1
I'm... lying? No, it's pretty clear now that you're quite confused about the difference between apps and services.


Your lying has nothing to do with apps and services and everything to do with gaslighting people in this thread into believing you weren't wrong instead of just admitting you made a dumb mistake.

Seriously, how can someone be even a little familiar with Linux and be so wrong about internet services working on Linux?


That's a great question, how can you?

And your attitude is just... something else.


Sorry I don't take being gaslit very well.

1

Jesus, Buddy. It's not gaslighting to explain how I interpreted your comment, and it's starting to sound like your angry responses are to avoid explaining your position.

Please explain to the class exactly what you mean by services not supporting Linux. No "obviously you know and are just pretending to make me look bad" stuff.

Explain like we're 5.

1 1
It's not gaslighting to explain how I interpreted your comment


Oh good now you're gaslighting me about gaslighting.

and it's starting to sound like your angry responses are to avoid explaining your position.


I'm not angry, and I've already explained my position.

Please explain


In the extremely unlikely case that you're legitimately just bad at counting, I advise you to scroll up and try again. If you cannot do that then I literally cannot help you. Restating my explanation will not help you.

We're done here.

This entry was edited (16 hours ago)
2

Ok, not angry. Tossing constant accusations of lying and gaslighting rather than answering.

Your position was "Linux not supported by platforms". You never explained what that means and no one understood you, clearly.

Almost like... gaslighting to say that you explained your position already.

This entry was edited (15 hours ago)
1

NixOS.

It is good for everything, if you invest a little time1 into it.


  1. Your entire life, lol. ↩︎
7 5

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.

Please tell me more about your work and how you use Nix in it. I'm interested.

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.

codeberg.org/madamegaymes/NixO…

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.
2

Oh, sweet!

In that case, I highly recommend taking a look at some more real-world examples. That 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.

This entry was edited (1 day ago)
3

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?

This entry was edited (1 day ago)
2