I assume the KDE implementation resizes to default when you stop shaking it.

I could totally see someone coding a function that increases the mouse pointer by x% every y mouse shakes, and then neglecting to put in a size cap.

This is kinda old information, but my understanding was that there were 3 issues with dasiy-chained UPSes.

The first is that you’re potentially going to cause a ground loop, which is not healthy for the life of anything plugged into those UPSes.

The second is that there’s a potential for a voltage droop going through from the first to second UPS, which means the UPSes will flap constantly and screw their batteries up, though I’d be shocked if that was necessarily still true for modern high-quality units.

And of course, the UPS itself won’t be outputting a proper sinewave when it’s on battery, which means your 2nd UPS in the chain will freak out (though again, maybe modern ones don’t have that limitation).

Yeah, and Windows and OS X both do it as well.

Though there being no upper limit to the size is amusing.

Sounds good to me?

really effects performance that much

Depending on the exact flags, some workloads will be faster, some will be identical, and some will be slower. Compilier optimization is some dark magic that relies on a ton of factors, but you can’t just assume that going from like -O2 to -O3 will provide better performance, since the optimizations also rely on the underlying code as to what they’ll actually make happen… and is why, for the most part, everyone suggests you stop at -O2 since you can start getting unexpected behavior the further up the curve you go.

And we’re talking low single digit performance improvements at best, not anything that anyone who is doing anything that’s not running benchmarks 24/7 would ever even notice in real world performance.

Disclaimer: there are workloads that are going to show different performance uplifts, but we’re talking Firefox and KDE and games here, per the OP’s comments.

Also they do default to a different scheduler, which is almost certainly why anyone using it will notice it feels “faster”, but it’s mainlined in the kernel so it’s not like you can’t use that anywhere else.

The master-omnibus image bundles all that into a single container is MUCH simpler to deploy.

Literally just used their compose file they provide at https://github.com/AnalogJ/scrutiny/blob/master/docker/example.omnibus.docker-compose.yml and added in the device names and was done.

Are uptimekuma and whatever you’re trying to monitor on the same physical hardware, or is it all different kit?

My first feeling is that you’ve got some DNS/routing configuration that’s causing issues if you’re leaving your local network and then going through two layers before coming back in, especially if you have split horizon DNS.

Alternate headline: “Person with lots of money who doesn’t have to do anything useful to survive has opinions on why people with no money should stop worrying about money”

For sure, just wanted to mention that it’s not just the China side of the trip you need to be vigilant about.

If your device is out of your sight, then yeah, you should probably assume it’s compromised.

Of course, that’s hardly JUST China doing funky shit with your devices, but depending where you’re calling home, odds are customs/immigration when you head home will try to do the exact same thing, too.

And the answer to everything is yes, always use a VPN if you don’t trust the network and you should never trust the network.

Judging from the last time I looked at their comment platform, it had the feeling that the only users of it were ones that were banned from Youtube because of the toxic shit they’re wanting to post so I mean, I guess, but it’s not the experience you’re wanting, probably.

Does !12345:p do what you want?

Edit: that also makes hitting the up arrow result in whatever command that was, so if you wanted to edit the line or whatever, you could !12345:p, up, then edit and execute.

Uh, are you sure your shell you’re using is bash and not zsh or something else?

Bash is indeed just !12345.

And suddenly billionaires are no longer interested in AI.

Why not save time and do it the other way?

Install the minimal/netinstall image, and then add what you need.

You’ll probably spend less time adding than trying to figure out what’s installed that you do or don’t need and trying to remove random packages without breaking anything.

IDK it sounds like they’re just plain non-competitive and should find something else to do with their time.

Perhaps make appliances that aren’t 80% plastic, or insert-product-here that doesn’t catch fire?

MediaTek will sell them better SOCs for the phones than they’re using anyways, so win/win for everyone.

two commands: dd and resize2fs, assuming you’re using ext4 and not something more exotic.

one makes a block-level copy of one device to another like so: dd if=/dev/source-drive of=/dev/destination-drive

the other is used to resize the filesystem from whatever size it was, to whatever size you tell it (or the whole disk; I’d have to go read a manpage since it’s been a bit)

the dd is completely safe, but the resize2fs command can break things, but you’d still have the data on the original drive, so you could always start over if it does - i’d unplug the source drive before you start doing any expansion stuff.

Yeah quicksync won’t help you there.

I thought nVidia’s limit was enforced by their drivers, but that’s probably changed since it’s been a while since I looked at nvenc as a solution (quicksync, then an ARC card over here).

dd then resize the fs?

Edit: one caveat here I forgot: if your fstab is using UUIDs, you’re going to have to update that, since the new drive won’t be the same UUID because, well, it’s not the same drive.

If you have an Intel CPU with quicksync, it will likely perform better than the 1060 in terms of visual quality, if its coffee lake or newer (8th gen).

If not, well, it’ll be fine up to whatever the stream limit is (4?).