Considering it - appears - to also need Google Play services then I don’t know how that will affect degoogled phones.

I’ve disabled all the Google services on my phone, and I’m able to restart them if necessary, but I don’t have a google account (which has to be tied to a physical phone number?), so it’s all waaay to sketchy for me.

And the API that connects to? Is that auditing anything else of mine? Capturing yet more data?

Not happy, me.

I think this has all the info:

https://keepandroidopen.org/

And their open letter: https://keepandroidopen.org/open-letter/

That’s exactly why I moved to Arch too…

I don’t recall what it was, but the fixed upstream version had been around for months, so I just moved.

I’ve even helped report / triage bugs, and they’ve been fixed and appeared in updates, which gives a good feeling

Wow. Thanks for the detailed breakdown, that’ll take me a while to work through!

I was looking into this recently and un-convinced myself that rsync was handling all the symlinks and permissions correctly.

What’s your command options? I was using -Prvtz for ages, then thought I needed an Aa too (from memory)

And, to be fair, you’ll know more about your setup when you don’t use the defaults as you have to learn more…

Yeah, I don’t disagree, I just wanted to keep it focused on their partitions.

Personally, I have everything I need on a persistent bootable Arch stick - that basically has everything to fix & rebuild any device I’m working on.

And I could remove it and reinstall another one if I wanted…

Kinda already covered by others here, but my summary:

You won’t have partitions nicely numbered from 1~3 unless you start again.

1 - Backup

2 - Check the backup

3 - Boot from GParted Live (feel free to use another live distro with gparted on)

4- Delete sda1, sda2, sda3 & sda4

5- Move sda5 to the beginning of the drive and resize down to 512MB

6- Slide sda6 & sda7 down next to sda5. I like to have 1MB gap between all partitions to deal with future issues (sometimes restoring a partition might nip the next one)

7- resize /home to fill the rest of the drive

8- redo another backup

If you wanted, you can apply each of those steps and then reboot to check it’s all working, then you’ll gain confidence in what’s happening for the future.

I also advise doing a health scan of your drive to check it’s SMART parameters. Something like smartmontools (with gsmartcontrol if you like a GUI). Then you’ll know if the drive’s going to die during all that data moving…

Isn’t it better to let them wither and die due to no clicks, rather than encourage them?

Nice. Thanks for the info on the fans

I guess you’re running the Fohdeesha firmware, I’ll have to look into this a little more…

Thanks

• MythTv
• LVM
• Xfce
• Transmission
• Doom

OT, but how are the Ruckus switches?

I’m using 2nd hand Ruckus WAPs with the Unleashed firmware and they’re great

Yep, esp. as the Immich team (and most likely others) should be using automation for their container builds anyway…

Which distro are you using?

My NAS is running Arch (btw) and I have Immich installed baremetal because someone’s nicely maintaining it in the AUR… would need a little work to convert that script into something for another distro…

They don’t seem to be very accurate, or check availability… Amazon.com for ~$5 ?

Depends.

I’m not going to buy the lowest priced parts, but I don’t buy overpriced stuff with flashing LEDs and gold heatsinks either…

Today, I’d rather have a RAID array of multiple drives than rely on 1 (even just a mirror) so failures of cheap-ish wouldn’t be a problem for me.

So… yeah?

The humans can’t downvote the AI slop videos? 🤔

Is?

Ok… it was… but is…?

I guess you’re helping out by absorbing allll the malware 🤔😉

No references to Doom yet?

Thst photo’s literally the Doom3 menu screen…