Vibe coded? You know how this works?

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

🤣

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

Get a better job so you can afford better drugs. This is “Minimum Wage Methy”, and you want to be “Salaried Methy”.

Gotta say… This is not how you’d generally do any of this. Where you get this info?

It’s not the CPU. All that will do is consume CPU and raise your energy bill.

1. Get some sort of resource monitor running on the machine to collect timeseries data about your procs, preferably sent to another machine. Prometheus is simple enough, but SigNoz and Outrace are like DataDog alternatives if you want to go there.
2. Identify what’s running out of control. Check CPU and Memory (most likely a memory leak)
3. Check logs to see if something is obviously wrong
4. Look and see if there is an update for whatever the proc is that addresses this issue
5. If it’s a systems process, set proper limits

In general, it’s not an out of control CPU that’s going to halt your machine, it’s memory loss. If you have an out of control process taking too much memory, it should get OOMkilled by the kernel, but if you don’t have proper swap configured, and not enough memory, it may not have time to successfully prevent the machine from running out of memory and halting.

https://gist.github.com/camullen/0c41d989ac2ad7a89e75eb3be0f8fb16

Just cut Windows out as much as possible and run everything in WSL. Setup everything to boot straight to all your WSL layers, and aside from the absolute shit Base OS, it should be the same.

Okay, but give a little look into where your disk is using space.

du -hsc /

And work from there.

It depends on where that storage was used. Some details would be useful.

At its core, you shouldn’t need to keep any previous layers than the one you’re using for the OS.

You also technically don’t need snapshots for anything but your personal file space.

I’m not sure what you’d like here. You didn’t give much info.

Did you want someone to literally work out a full config for you in here? We don’t know what you’re even running.

This is just basic network routing and subnetting.

Not sure what the Frame means with any of this. It’s going to be running the same stack as Deck, which is KDE. It’s also not going to be any sort of headset for your PC, at least at the outset.

As for your other Dr questions, it’s all just personal preference. The Desktop is just window dressing on a compositor and window manager anymore. If you’re comfortable without all the system helpers and convenience of using either Gnome or KDE, you can just run a WM like Hyprland or Sway instead.

Wait…so you’re looking for a solution with zero problems because of…clout or something? I don’t get it.

If you like Debian, just stay with Debian. Especially if you’re not familiar with what running Arch really means in the deeper sense. Mostly that the guardrails are off, in a sense.

CachyOS puts a ton of work into adding UX helpers that makes it pretty user friendly, but it’s still going to have a lot of manual intervention required, but that’s a feature to some.

If you have an AMD laptop, maybe look into installing SteamOS and Kodi as a non-steam app. That could be your sweet spot.

Are you just SAVING as these file extensions, or EXPORTING as each type of file extensions.

Not the difference, and see in the File menu that you need to use the EXPORT function to change actual file type.

1. What’s a PFP?
2. What format are you uploading them in?
3. What app are they generated with?
4. Do they also look corrupted on other devices you may have handy?

Yeah…this seems like OP is doing this in extra hard mode, and there are simpler ways to handle the problem.

Unless there is a mapping between a UID of a user across many different machines (something like a domain controller), you’re not going to be able to set proper permissions by user. You need to use a generic group, or provide global read access at a minimum.

I’m not 100% sure why you’ve chosen this route, but there are MUCH simpler ways of doing this that don’t involve VMs and NTFS volumes.

At this point, you’re butting up against 3 levels of nested permissions, including the VM. My suggestion would be to make sure all the files on the NTFS volume have global read access, then go into the VM and attempt to set NTFS permissions on the files (they are different). If that becomes too tedious, you could just try setting 777 on all shared files. It’s unsafe, but may get you through until you find a more…workable solution for what you’re doing here.

I think the overall solution is to just not need this Windows VM, so look at moving these sites off to Nginx or something ASAP.

Nothing in particular. They all seem about the same to me. Check top rankings on GitHub perhaps.

It blocks on all the major engines. DDG included.