Yes. That’s what allows Unix legends like this: https://www.ee.torontomu.ca/~elf/hack/recovery.html

You keep the user-changeable files on a separate filesystem. Whether that’s just a separate partition, or an external disk. Keep the system itself read only, and write-heavy directories like logs and caches in RAM.

Polish.

It useless to be first if that product isn’t reliable, sustainable, practical. Apple adds polish to other concepts to make them usable by the vast majority of people.

Laptops existed……with weird keyboard layouts and mice that were afterthoughts. PowerBook pioneered the keyboard forward design that every laptop now has.

Smartphones existed……incredibly limited, weird UI, awkward input, targeted at businesses instead of regular people. iPhone changed everything so much that every other design died.

Collecting different innovations and figuring how to combine them in a way that is practical and sellable is their continuous innovation.

Wow. Thank you for that incredibly detailed explanation!!

It does sound like though that it is POTENTIALLY cheaper than something like B2, but also much easier to misconfigure and end up in a more expensive tier.

Seems to me unless you have a reason to use Amazon storage or already have something using it, using it for backup isn’t the best idea.

How much is their cheapest glacier tier? Seems complicated to calculate, seems there’s some relation to s3 storage or I’m just missing something? Haven’t looked that closely.

You could also pull all out through cloudflare and then it should be completely free

Sorry thought he wanted to play emulators from his 1070 rig.

Sunshine and Moonlight are what you want instead.

https://github.com/LizardByte/Sunshine

https://github.com/moonlight-stream/moonlight-qt

Didn’t we do this already back in the 90s with IE bundling??

Ok but……who the hell runs blender and FFP in 8GB?

The vast majority of users are NOT running pro apps like that.

It’s just a name. If you’re actually running pro stuff, you’d be an idiot to run that on 8Gb no matter what machine.

Apple’s argument that it’s the same as 16gb is dumb, but anyone actually using pro apps on 8Gb is dumber. The majority of browser(with sane numbers of tabs)/iPhoto/office users really are probably not gonna notice.

My 701 with 2gb ram and extended battery still works. I used to go wardriving with that thing!

I had a pi 1b running my hvac/humidifier/HRV unit at home for years. Only removed it when we moved out.

So I’m SUPPOSED to run a miner to keep mine from being overly idle??

I have 2 Pi 4s in operation. One is a Moonlight/USBoverIP stream gaming portal. It automatically turns on and connects to a VM running Sunshine on my Proxmox host, passes any USB controllers/bluetooth etc to the VM so the big loud gaming box is in the basement and the tiny Pi is next to the TV. 1080p60 works great, minimal lag.

The other acts mostly as a quorum server for the proxmox servers, I have two proxmox hosts and use the second Pi to ensure the cluster doesn’t get split brain. It also acts as a USBoverIP host for my home automation Zigbee and Zwave usb sticks, so that either proxmox host can connect to the USB sticks and the home automation VMs aren’t locked to a physical host.

I loved Pi’s, but I hate the micro hdmi connectors

If you’re forwarding between haproxy instances, use proxy-protocol instead of forwardfor header forwarding.

Depends on your system. Desktop have different requirements than servers.

On both at minimum, I’d keep /home and /var/log separate. Those usually see the most writes, are least controlled, and so long as they’re separate partitions they can fill up accidentally and your system should still remain functional. /tmp and /var/tmp should usually be mounted separately, for similar reasons.

/boot usually keep separate because bootloaders don’t always understand the every weird filesystem you might use elsewhere. It would also be the one unencrypted partition you need to boot off of.

On a server, /opt and /srv would usually be separate, usually separate volumes for each directory within those as well, depending how you want to isolate each application/data store location. You could just use quotas; but mounting separately would also allow you to specify different flags, i.e. noexec, nosuid for volumes that should only ever contain data.

/var/lib/docker and other stuff in /var/lib I usually like to keep on separate mounts. i.e. put /var/lib/mysql or other databases on a separate faster disk, use a different file system maybe, and again different mount options. In distant past, you’d mount /var/spool on a different filesystem with more inodes than usual.

Highly secure systems usually require /var/log/audit to be separate, and needs to have enough space guaranteed that it won’t ever run out of space and lock the system out due to inability to audit log.

Bottom line is its differnet depending on your requiremtns, but splitting unnecessarily is a good way to waste space and nothing else. Separate only if you need it on a different type of device, different mount options, different size guarantees etc, don’t do it for no reason.