"For the new Manjaro fan. 😁"

https://www.makeuseof.com/which-is-best-linux-distro-manjaro-vs-ubuntu/

👇 If you are using a different model of Pixel follow the instructions on the GrapheneOS Website. The below video is for showing you how to do it. Training purposes only.

Hey all, here is a tutorial/demo of using the webusb installer to flash GrapheneOS onto a Pixel 3 XL.

https://rumble.com/v178p5r-grapheneos-webinstaller-demo-pixel-3-xl.html

"Pacman is the Arch based distro package manager. It runs differently than APT or RPM/DNF (Fedora). Arch based distros usually bundle everything you will need into the package install."

https://www.fosslinux.com/47168/use-pacman-arch-linux.htm

"The Linux Business Line is based on RHEL which is Red Hat Enterprise Linux. What they are known for is how long their versions are supported. Businesses who have critical processes that can not be changed, or need very specific conditions to run consistently and with stability.

I personally can not recommend RHEL because of the recent James O'Keefe expose and they locked their source behind a developer paywall. There are downstream distros like Rocky, Oracle, CentOS Stream, that are all based on RHEL that offer a good experience while maintaining the stability and long term support.

https://access.redhat.com/support/policy/updates/errata

"The Fedora Core that powers RHEL, and other workstation, server distros. Also can be used for personal computing. Using the DNF package system very similar to Debian in commands."

https://fedoraproject.org/

"The word package manager is used a lot and is how you get your software. Sometimes that might be confusing when you see three entries of the same things. There is a simple rule I use when choosing something to install.

Official Repository - Is always the most ideal place to get your software if it is available. This will be updated first and the system will let you know when updates are ready to install. This will also be the most compatible with the distro. It is curated by the maintainers of the distro.

Extra/Community - Some distros will have extra repositories available these can be added by default or you if you know what to do. These are well maintained alongside the official repo by the community or distro maintainers.

Flatpak - A universal repo that is maintained by the application developers. Considered distro agnostic but will be bloated as it includes everything for the app needed to run. Also installed without much in the way of permissions that may limit functionality until given correct permissions. Flatpaks are also not always included in the list of updates for your software often needing separate attentions. Especially if you use command line over GUI.

AUR - Arch based distros will have the option of the AUR which is user added software packages that need to be compiled before being usable. This repository can be very hit and miss and should only be used if you need something unavailable in the other lists."

"If you are using an Arch based distro this is how you find and compile software from the AUR."

https://www.howtogeek.com/how-to-install-and-use-yay-on-arch-linux/

"One of the other things Linux can do, is compile and use software from source. This should be available on every distro and even BSD can compile and use 90% of Linux software. However this is for advanced users as it's not a user friendly process."

https://www.fosslinux.com/9686/how-to-install-a-program-from-source-on-linux.htm

"Another universal application method to install software to Linux."

https://rumble.com/v4bgdui-appimage-launcher-how-to-add-appimage-icons-to-your-applications-launcher.html

The subject of /e/OS has come up again. A former developer at /e/OS, now developer of LeOS, sums up the issues with /e/OS as follows: "Too much commerce, too much bloatware and not really fully degoogled".

For us at Bones' Tech Garage, the main point is using only fully degoogled phones. LineageOS and many fan ROMs do not include GAPPS (Google Apps), but the OS source code has not been stripped of Google links and dependencies.

Most commercial offerings we have seen are more exploitive of the trending privacy buzz words and do not deliver on their promises, only claiming their OS to be degoogled without actually doing the hard work of removing Google from the ROM and maintaining it.

At the moment, the only Android compatible operating systems that are known to be fully degoogled are GrapheneOS, DivestOS, and LeOS. The best and easiest solution is to get a supported Pixel phone and put GrapheneOS on it. Even DivestOS tells us it's better to use GrapheneOS, but DivestOS fills a need by supporting the wide range of devices that LineageOS supports because DivestOS is actually a fully degoogled fork of LineageOS.

LeOS similarly fills a need in supporting a further range of devices that can use the Generic System Image (GSI) update installation method. So the core of degoogled phones is GrapheneOS on Pixel phones, and then branches out to reach more devices with DivestOS and LeOS.

This 2019 critique of /e/ was scrubbed from the internet, but it can still be accessed by this link at the Wayback Machine internet archive. It does link to /e/'s response. No telling if /e/ has made changes to address the criticisms.

/e/ – privacy-enabled Android ROM, or Evil Corp? · InfoSec Handbook – information security blog
https://web.archive.org/web/20200215130732/https://infosec-handbook.eu/blog/e-foundation-first-look/

"Hardware issues most people probably never think that when the system malfunctions maybe something is going out. Here is a guide to basic issues and how to tell what could be going wrong."

http://www.acmehowto.com/howto/pc/problems/diagnosis.php

"If you run a headless (without monitor) PI. Sometimes if you need to plug a monitor in it doesn't always like to cooperate. Here are some ideas to coax it into working again."

https://www.maketecheasier.com/raspberry-pi-monitor-not-working-fixes/

"More on the RHEL line and it's alternatives."

https://www.tecmint.com/redhat-based-linux-distributions/