No, this is
Landing gears are usually designed to drop by gravity (or manual hand cranking) alone if there's a hydraulic failure.
The linked article — and others — explain that in Android 10+, (a) executable binaries can no longer reside in a read/write directory, and (b) access to /sdcard will go away. Simply put, these changes destroy my application's ability to function, and that of Termux as well.
That sounds like proper security to me? Inability to access the user's storage is a bit lame, but they've been moving to nicer APIs for that anyway.
Android is a mobile phone OS, not desktop / embedded Linux.
I'm going to agree with Burstar here - if you're setting out to prove that something is possible, you're going to give it the best chance you can. Once you know its possible (whether its something like using an arduino to simulate an old price of hardware, or if a compound can cause cancer), you go and refine it down.
Where are these OEMs that allow proper bootloader unlocking on most of their range?
Google, Sony ...? Huawei stopped doing it, Oppo & Samsung doesn't last I checked.
I'm pretty certain that the USB IF decided to use the max possible Gbps as the cable rating, rather than the mess that was
USB 3.0 USB 3.1 USB 3.1 (Gen 1) USB 3.1 (Gen 2) ...
So it's more likely apple are just being specific in the type of cable you need.
gedit in native Linux or WSL2. use it for Ansibke, python, C, bash, basically anything I need to edit. Has a git plugin, bottom terminal pane, left open files / current folder pane. Does all I need it to do, and it's not a huge fuckoff electron app.
(If you buy a suitable device) You don't have to use the preloaded OS (see Graphrne, Lineage etc).
It means that if someone breaks out of your container, they can only do things that user can do.
Can that user access your private documents (are these documents in a container that also runs under that user)?
Can that user sudo?
Can that user access SSH keys and jump to other computers?
Generally speaking, the answer to all of these should be "no", meaning that each group of containers (or risk levels etc) get their own account.
There is a db migration command that I used to do the same thing, was pretty painless, just needed to run that and then update the config iirc
Just a point of clarification: Don't use RAID 5 for more than 2-4 TB. The rebuild takes so long that the mean-time-between read errors statistic basically guarantees a read error while rebuilding, which may cause the controller to trash the array.
That and rebuilding that much data might push one of the drives over the edge anyway.
One thing that people miss - either out of ignorance, or because it goes against the narrative - is that systemd is modular.
One part handles init and services (and related things like mounts and sockets, because it makes sense to do that), one handles user sessions (logind), one handles logging (journald), one handles networking (networkd) etc etc.
You don't have to use networkd, or their efi bootloader, or their kernel install tool, or the other hostname/name resolution/userdb/tmpfiles etc etc tools.