Oh no…anyway

👏👏👏💩💩💩💩💩

In Gentoo, emerge compiles packages from source on practically every machine you set up. matrixOS remedies this by building once and distributing binaries, so you skip the compilation wait entirely.

Okay, soooooo…basically disregarding the entire point and benefit of Gentoo? The entire reason you’d want to build from source on a specific machine or architecture is for the compiler optimizations done on that hardware. Just shipping binaries around is normal, so I’m not getting what the point is here.

Any company who gets up and running focusing solely on consumer facing memory supply is going to make a fucking mint. There are only a few who could manage to do so right now, and they are unfortunately not likely to do so.

Look into recapping that set. Can probably improve the picture quite a bit pretty cheaply.

Lolwut?

You think that’s why Canonical and RedHat make money, huh? 🤣🤣🤣

You take the good, you take the bad, you take them both and there you have The facts of life, the facts of life.

There’s a time you got to go and show You’re growin’ now you know about The facts of life, the facts of life.

When the world never seems to be livin up to your dreams And suddenly you’re finding out the facts of life are all about you, you.

Wait til all these projects crash, burn, and get liquidated. Gonna be an amazing secondary market for brand new, unused bulk hardware.

Symlinks are just links to a hard file. Unless you’re setting specific flags, you’re coming the hard files along with everything else. I’d run a dedupe script on your copied files and see if you didn’t happen to double up on some things.

Depends on how the code is using it. You could look deeper, but that’s not what OP is asking for help with.

It’s not about how big they are really, it’s about how many can be open at a time. Without sane limits, then anything is a ticking time bomb.

Reduce the number of active connections, or the total number of active transfers available at once, and that will lower that number.

If you’re POSITIVE your memory situation is in good shape (meaning you’re not running out of memory), then you can increase the max number of open files allowed for your user, or globally: https://www.howtogeek.com/805629/too-many-open-files-linux/

Again: if you do this, you will likely start hitting OOMkill situations, which is going to be worse. The file limit set right now are preventing that from happening.

You have a process holding open a bunch of FD’s. Instead of just blindly increasing the system limits, try and find the culprit with something like: lsof | awk '{print $1}' | sort | uniq -c | sort -nr

That will give you a list of which processes are holding open descriptors. See which are the worst offenders and try and fix the issue.

You COULD just increase the fd open max, but then you actually will more than likely run into OOMkill issues because you aren’t solving the problematic process.

deleted by creator

deleted by creator

Awww, Lonnie didn’t get invited to the cool table.

Chin up, lil’ tubby bitch!

Riiiiight 😉😉

You probably have debug logging enabled somewhere.

Back up a bit because you’re conflating a number of things, so let me try to break it down:

1. If you’re using Hyprland, you’re losing all the power management features of the more fully featured DE’s like Gnome or KDE. This isn’t a flaw, it’s just an acceptance of the trade-off.
2. Unless you’ve directly intervened, the power profiles are set to whatever your distro installs and sets from the initial install. Which leads to…
3. There are different defaults for powered vs battery by default. If you’re on a laptop and you don’t have the DE helpers, you’re on your own.
4. The hardware power management built in to your laptop may be playing a role here, so check your BIOS
5. Check dmesg to see what live changes your hardware controllers might be making
6. Check the Framework forums for keywords related to “Hyprland” to see if somebody has easy scripts for you to help. Otherwise, just switch to a DE that manages power the way you’d expect.

Your power restrictions are preventing the higher power settings.

If you’re using Gnome or KDE, you can use the applets to just turn it up a notch and get more brightness.

You’re not wrong on your initial points at all, and I said as much above, so we’re in agreement.

You seem to be thinking Valve is shutting down Deck as a product, and I never said that at all. They just have more important irons in the fire. There is also an obvious benefit in them pivoting Deck 2 to an ARM SoC in the next version, and they’ve literally said as much. AMD already quietly announced their ARM-based SoC (sort of by accident), so it’s not weird at all for a company like Valve to: 1) Focus on the pivot they are currently making and 2) Focus on the development of Deck 2.

On your other point: nobody, including Valve said they were discontinuing anything. People are freaking out because they’re out of stock. So what? They have bigger fish to fry. If they do another production run, they may do it after launch of the new hardware just to see where things lie, but who knows.

If you’re familiar with Valve’s history in hardware, you know they don’t officially discontinue anything, they just stop selling it in between hardware revision releases. There is absolutely nothing weird happening here that is inconsistent with their history of this.

My personal bet is they are guessing that Frame will be in direct competition with Deck, and they want people to buy that instead. Running out of stock of one during a product push for the other just seems like they care less about producing a dated product, but have the option to make another production run if they see things going that way.

We also don’t even have the insights into how well Deck is selling at this point. Maybe it just doesn’t make fiscal sense to make another production run right now. Who knows 🤷