Eskating cyclist, gamer and enjoyer of anime. Probably an artist. Also I code sometimes, pretty much just to mod titanfall 2 tho.
Introverted, yet I enjoy discussion to a fault.
Oh, for sure. If you wait a month, the bigger update can be a lot more trouble.
But look at it like this. If a rolling distro has a problem once a week, which is fixed within 24 hours, updating daily guarantees you will run into it.
While updating weekly means your chance is only one in seven. Since because by the time you update, the fix is more likely to already be in the repos, so you’ll be jumping over the problematic update.
The functionality is conceptually identical, yes.
And timeshift is by default set up such that only / is rolled back while /home is kept as-is.
So same as atomic distros, rolling back doesn’t mean going back in time in terms of personal files or settings.
So I’m really only missing out on the updates for something like Bazzite being potentially more reliable.
I’ve been on endeavour+plasma over a year now.
I share your desire for a system that always, 100%, every time, is there and ready to be used.
At the same time, I really like arch and the convenience of the AUR.
Hence, I boot-strap reliability onto my system through btrfs snapshots.
The setup is extremely simple, (provided your install is grub+btrfs) just install timeshift + the auto-snap systemd services. Configure it, and forget it.
Next time something breaks, instead of spending time on troubleshooting, you timeshift back to a known good point and then just get on with using your system.
With the auto-snap package installed every update also creates a restore point to go back to before it.
In addition to that, I started updating my system less frequency. The logic being that the more often you update a rolling release install, the more likely you are to catch it at a time when something is wrong, before it is fixed. Still regularly, but instead of every other day, I now have an update notification that goes off once a week.
The result has been zero time spent troubleshooting my system. If it worked yesterday, it’ll work today. If it worked last week, but doesn’t today, I’m a reboot away from a known good snapshot.
Wayland has been fine on nvidia for a while now. Even G-Sync works.
Uuh. That is exactly how games work.
And that’s completely normal. Every modern game has multiple versions of the same asset at various detail levels, all of which are used. And when you choose between “low, medium, high” that doesn’t mean there’s a giant pile of assets that go un-used. The game will use them all, rendering a different version of an asset depending on how close to something you are. The settings often just change how far away the game will render at the highest quality, before it starts to drop down to the lower LODs (level of detail).
That’s why the games aren’t much smaller on console, for exanple. They’re not including all the unnecessary assets for different graphics settings from PC. They are all part of how modern game work.
“Handling that in the code” would still involve storing it all somewhere after “generation”, same way shaders are better generated in advance, lest you get a stuttery mess.
And it isn’t how most game do things even today. Such code does not exist. Not yet at least. Human artists produce better results, and hence games ship with every version of every asset.
Finally automating this is what Unreals nanite system has only recently promised to do, but it has run into snags.
CSAM is against their terms of use. Afaik they remove it both using some automated systems, as well as manually.
Games can’t really compress their assets much.
Stuff like textures generally use a lossless bitmap format. The compression artefacts you get with lossy formats, while unnoticable to the human eye, can cause much more visible rendering artefacts once the game engine goes to calculate how light should interact with the material.
That’s not to say devs couldn’t be more efficient, but it does explain why games don’t really compress that well.
Aren’t a lot of the 2.5" ones already empty space?
How big, and how expensive, would a 3.5" SSD be, if it actually filled enough of the space with NAND chips for the form factor to be warranted?
Even in the most generous scenarios, cryopreservation of a person has to be done quickly, lest the brain decay.
Current methods cannot achieve it to begin with. Let alone once the person has been dead for days.
What do you mean “but”?
This doesn’t produce anything. It removes jobs instead of creating them. And by the end there is one less company in the system.
I wrote in response to you saying this is what they “should” be doing. That it would either work, or not.
But this is working sustainable businesses being butchered for their value on the meat market, rather than operated long term.
It most certainly isn’t what they “should” be doing.
If this is the best way to make money, the rich will continue to do it instead of starting new companies. That is not going to have pleasant long-term effects on the world.
Then you need to look into how private equity works.
They buy mature companies, often with borrowed capital, and then place the debt on the purchased company. They essentially make companies take on a massive loan to buy themselves from themselves, except the private equity firm ends up the owner.
The company then goes into overdrive trying to pay off the debt, while the firm makes changes intended to make the company “more efficient”. All while paying themselves “consulting fees” and “bonuses” for stepping in and “helping” the company do better.
This usually means mass layoffs, dumping assets, paycuts, restructuring…
Best case scenario, the company was already failing, and now it fails faster.
Worst case… The company was doing perfectly fine, making a sustainable living for its employees. And then it gets purchased by a private equity firm.
Suddenly everything is on fire. Not a single penny can go unpiched, workplace comfort unsacrificed, or employee unoverworked. And that that is the new norm, is the good ending.
Private equity makes money by killing the golden goose, and then finding another. And then another. And then another.
What the money in our pocket allows us to afford is not the same as what our health and planet can afford.
Causing that disconnect by supplanting secular consideration with economic consideration is one the reasons so much evil is done and accepted in the name of profit.
Apparently windows doesn’t like it, but it can be done using Rufus or WinToUSB.
Should be. A USB drive is a storage device like any other. Shouldn’t matter that it isn’t connected via SATA or NVME.
Wine can’t properly access USB devices, so even if you got iTunes installed, it wouldn’t work.
I’m sceptical that a VM is out of the question, one should run on almost anything, though not necessarily perform well. I would give it an attempt, if you didn’t already.
Still, it might be simplest to set up a windows install with itunes on a usb, or second partition, and boot into windows only when you need to.
What are you on about?
Unless you’re the admin, using nextcloud involves nothing more complicated than google drive or dropbox.
I have half a dozen “normies” on my instance as users, and they figure it out just fine.
Oh that’s new for me. I’ve been using alternativeto.com
My guess it just doesn’t evict stuff from before the suspend, starts re-loading stuff after the resume, which makes the apparent amount “used” go up.
On a normal linux system, “free” RAM will over time drop down to zero, as the kernel puts the extra memory available to use. But it doesn’t mean there isn’t room to evict less-needed stuff if necessary.
AFAIK linux only starts actively evicting RAM once it fills up.
Like the other guy mentioned, drill down and see if yiu can find the actual program causing the problem.
I don’t think there’s any effective difference between timeshift and snapper. They’re both essentially just GUIs for features supported by the underlying btrfs filesystem.
Timeshift backup to another disk, is just rsync.
Yes.
Just do
yay timeshift, then install all three packages that show up.Timeshift itself is one, autosnap is a second, and the third is a systemd timer that handles the scheduled snaps (monthly, weekly, etc).