Containers, the concept that Docker implements, lets app developers give a self-contained environment for distribution. For devs that means consistency in deployments across environments, which in turn means sysadmins can deploy each of these apps as fully isolated units.
With that, you get really clean installs/updates/uninstalls, and your deployments get done with a well-defined, declarative definition file which can also handle multi service dependencies (a la Docker Compose/K8s)
The firmware has to allow it, so if you've got physical access to the machine that's possible. Remote access root, on the other hand, can't tell the firmware to register new keys as long as it's configured correctly
Generally yes. For many distros, the kernel signing key is with the distro maintainers and so the package comes with pre-signed kernel images. For distros like Arch and Gentoo, it's the user's responsibility to maintain the signing key and sign each updated kernel
I find it funny it didn't point out Active Directory
LGPL actually, not GPL
Ooh can I get an equivalent for zsh? :D
I'm genuinely having a chuckle at how shocked people are at my submission, made my day xD
To add on to this explanation, you generally use source ~/.bashrc to reload your shell whenever you want to make changes to your user config. Tab completion weakens the barrier to destruction significantly (esp. in my case)
I feel that might be an issue from 4G onwards, considering VoLTE and VoNR are intended to avoid the use of a separate voice network to their existing data network
source ~/.bash_history
I do miss removable batteries, they had the added benefit of having a heavy mass (the battery) get thrown out when the phone falls. That helped save the display from getting damaged because a lot of the momentum was transferred to the battery popping out
Specific to JS, due to the double equals being type oblivious