Great point.

You can, but you need to basically completely turn that laptop into a router. A cheap WiFi bridge would be more flexible.

This is spam

Give this a shot: https://github.com/dimtpap/coppwr

I’m not aware of anything that ties display and audio output together in the way you’re expecting, but you could make a Pipewire config to tie some things together and probably make it work. If your TV is using DP or HDMI for audio output, then this is already handled for you in some small part because it helps to define which display will be in use.

“It’s really great, and I hate it” is kind of an insane take, but if you’re looking for things to tune, tweak, or squeeze extra performance out of, try compiling your own optimized kernel and drivers. Maybe get into building a more portable profile for yourself so your changes can move with you elsewhere.

They probably paid for some long ago, and don’t want to pay again for updated versions of everything. They could probably even get away running stuff on Wine 🤣

It’s literally in every display you see in the world. OEMs stopped fucking with Windows years ago.

Go to any fast food restaurants with those vertical displays? Linux.

Check-in kiosks that have been deployed in the past 5 years? Linux.

Your router, most platforms you interact with online, media devices, cars (they should be using RTOS, but many use Debian), movie theaters, POS systems…

Linux is the most deployed OS on this planet by far. I’m kind of annoyed when people don’t realize this.

I actually hate when engineers are just letting a desktop sit like this. It’s sloppy and unnecessary.

Vibe coded? You know how this works?

Good luck with that. I look forward to your future posts about it.

🤣

PXE is unnecessary unless you’re going to be creating a reusable boot image. Just faster to use LiveUSB.

What did you getaid off, and what are you trying to apply to? Maybe help to understand on what you’re trying to learn.

Just for your own sanity, just install Talos on the 3 machines, understand how to join them to a cluster, then deploy some stuff around the cluster. Get a feel for the basics before you get into the mess of trying to do it all in VMs.

I’d also check some comparisons on the various flavors of different lube stacks: k3s, microk8s, kubedge…etc. Theres so many now it’s hard to track.

Because you’re being rate limited. Don’t let these tools constantly hammer Github’s API in mass fits and starts or you may get a back off from GH.

Neh

And I got downvoted into oblivion for bringing it up 🤣

Then why if you aren’t familiar would you make a comment you didn’t see anything?

Do you randomly walk into other people’s jobs with zero proficiency and speak to how they’re doing at it?

Here’s a very simple list of issues that any Node dev would immediately say is generated and has not been cleaned up:

• package.json
• knip (check that tab usage)
• WILDLY fucking stupid Dockerfile
• What directory am I in here??? Note the dupe code because whatever shit tool lost track
• What in the absolute fuck?

I mean I can keep going, but if you even glanced at this and didn’t IMMEDIATELY get it, you are bad at your job.

Edit: This one is fucking hilarous

Lolwut??? Did you check the GitHub at all?

Check the code

This is so vibecoded 🤣 Nawthx

Red Hat is the largest funder of the Fedora Projects because it serves as a base for other things they make and support aside from their enterprise distros. Being the largest single funder gets you the most pull on the direction of said projects. They also have Red Hat employees directly running or contributing to various projects and upstream commits.

The actual community boards and such are independent of Red Hat otherwise. Similar to how Valve suddenly has a bunch of pull in the direction of the projects they’ve been directly funding and contributing to the past few years, Red Hat informs the independent community board with commits and contributions.

This is how the FOSS community works in general though. ‘Project A’ could be widely used in the community, but generally have fairly slow development. ‘Company A’ comes in and offers to fund feature development or big hunts, or maybe directly contribute fixes because they rely on this project. That project then either has the choice to turn down that extra help that could greatly benefit the project, or take that help, and as part of that deal, accept that ‘Company A’ now has some pull in the direction of the project.

Kind of a majority rule via resource commitment.

Logs