Just so you’re aware, Gitea was taken over by a for-profit company. Which is why it was forked and Forgejo was formed. If you don’t use Github as a matter of principle, then you should switch to Forgejo instead.
If I’m not mistaken, I believe the 2018 J3 has a locked bootloader. The fact that I can’t find even a SINGLE custom ROM on XDA for this model means it’s highly likely that the bootloader is locked, and/or the device isn’t dev friendly (no kernel sources available etc).
so I guess doing the same on my smartphone wouldn’t be too hard.
Mate, you’ve no idea… Smartphones are a completely different ball game to desktops. You could try and compile your distro, but without the kernel sources and drivers for your specific model, nothings gonna work. You won’t even be able to boot the damn thing. And even if you did have those, it’s going to take a LOT of effort just to get basic OS functionality working. Forget getting actual phone stuff working, like making calls etc - that’s next to impossible. Even large projects like PostmarketOS struggle to get basic functionality going even on dev-friendly phones.
But you can stop dreaming about all the above if you can’t even unlock the bootloader.
Basically, what all this means is that there’s no point wasting your time on the J3. Stop right now and don’t waste any further time on this.
If you’d really like to run GrapheneOS / Linux on your phone, your best option is to sell your J3, and get a used Google Pixel from Swappa/eBay or something.
It’ll really depend on your local job market. I was on a serious job hunt earlier this year and I couldn’t find a single Linux job which asked for LFCS certs. There were a couple which asked for Red Hat certs though. Of course, this could be specific to where I live, so I’d recommend looking at some popular job sites for where you live (+ remote jobs too) and see how many, if any, ask for LFCS, and you’d get your answer.
Should I focus more on dev ops? Security? Straight SysAdmin?
From what I’ve seen so far, the days of “traditional” Linux sysadmin roles are numbered, if not long gone already - it’s all mostly DevOps-y stuff. Same with traditional security, these days it’s more about DevSecOps.
As a modern Linux sysadmin, the technologies you should be looking at would be Ansible, Kubernetes, Terraform, containers (Docker mainly, but also Podman/LXD), GitOps, CI/CD and Infrastructure as Code (IaC) concepts and tools.
Some Red Hat shops may also ask for OpenShift, Ansible Tower, Satellite etc experience. IBM shops also use a lot of IBM tools such as IBM Could Paks, Multicloud Management, and AIOps/Watson etc.
And finally there’s all the “cloud” stuff like AWS, Azure, GCP specific things - and they have their own terminologies that you’d need to know and understand (eg “S3”, “Lambda” etc) and they have their own certs to go with it. I suspect a “cloud” cert will net you more jobs than LFCS.
So as you’d probably be thinking by now, all of the above isn’t something you’d know from just using desktop Linux. Of course, desktop Linux experience is certainly useful for understanding some of the core concepts and how it all works under the hood, but unfortunately that experience alone just isn’t going to cut it if you’re out looking for a job.
As I mentioned before, start looking for jobs in your area/relevant to you and look at the technologies they’re asking for, note down the terms which appear most frequently and the certs they’re asking for, and start preparing for them. That is, assuming it’s something you want to work with in the future.
Personally, I’m not a big fan all this new tech (I’m fine with Ansible and containers, but don’t like the industry’s dependency on proprietary techs like Docker Desktop, Amazon or Red Hat’s stuff). I just wanted to work on pure Linux, with all the all standard POSIX/GNU tools and DEs that we’re familiar with, but sadly those sort of jobs don’t really exist anymore.
Plasma Panels have now gained a new visibility mode: “Dodge Windows” aka “intelligent auto-hide!” In essence, the Panel auto-hides when touched by a window, but is otherwise visible
Finally! With this, we can now have a panel behave like a proper dock.
There are already a few actively maintained forks of Tachiyomi. TachiJ2K and TachiyomiSY are two such popular forks which have several features not present in the original app. In fact, many hardcore manga readers in the community had already switched to them years ago. There’s also Aniyomi, which not only supports manga but also watching anime via extensions, the same way you’d read manga in Tachiyomi.
So thanks to the power of FOSS, Tachiyomi already continues to live on and you don’t need to wait for a fork.
FYI, Windows doesn’t have any feature either to automatically clear all of it’s temp folders (%TMP%, C:\Windows\Temp, C:\Windows\Panther), plus several other folders where orphaned files are often leftover, such as C:\Windows\Installer, C:\Windows\CSC, and various folders and cache files in your AppData\Local etc, to name a few off the top of my head.
I used to be a Windows sysadmin for a long time, and let me tell you, HDDs becoming completely full due to cache/temp files is very much a problem in Windows.
Autotype is already solved - ydotool, wtype and dotool exists (and possibly others as well).
Screen magnification is already present in KDE (Meta + +, Meta + - to zoom in/out). There’s also a magnifier tool (KMag). There may be similar functionalities in other DEs.
My issue is the lack of an overall GUI automation tool, ie, like AutoHotkey. X11 had PyAutoGUI, but there’s no such AIO equivalent for Wayland yet, and the PyAutoGUI devs don’t seem to be interested in Wayland support - it’s neither on their road map, nor have they even answered any Wayland questions on their Github page, which is disappointing. But this isn’t Wayland’s fault, when other tools have shown that automating the GUI is possible, we just need someone to put together a complete package like PyAutoGUI / AHK.
I used it at work recently to update my work-provided HP Thunderbolt dock, and it resolved an issue where the external monitors would fail to activate after resuming from standby. I never got an update notification when I was using my Windows laptop so I was oblivious to it; it was only thanks to connecting it to my Linux laptop and fwupd, that I found out there was an update, which subsequently resolved the issue.
I love it when stuff like this happens and Linux saves the day. =) (and I get to show off to my Windows heathens colleagues.)
In addition to the other comment re. LibreOffice, I’d also recommend trying out OnlyOffice - generally, it has better compatibility with MS Office formats compared to LO, and the UI is very similar to MSO which may make it easier to use.
As others have said, there’s Vanilla and Endless, but both use GNOME.
Is there a reason why it has to be Debian? With an immutable distro, you won’t be using traditional package managers anyway (like apt), all have the same stability factor, and with the same systemd + KDE, it’s more or less the same experience regardless of which distro you go for.
One of the key usage patterns of an immutable distro is using a container to install your extra packages. So you could go for a Fedora-based immutable KDE distro like Kinoite, and set up a Debian container where you can use apt and other Debian tools.
Because Toolbox is a Red Hat/Fedora project and Distrobox isn’t. Also, Distrobox is a much more recent project (2021) compared to Toolbox, which was developed back in 2018. When Silverblue came out, there was a need to make it easier to install apps, and thus Toolbox was born.
Since Toolbox is a Red Hat/Fedora project, it means that it’s officially supported, whereas Distrobox isn’t. Not that it means much from a community support/home use case of course, but that might matter if you’re an enterprise and you want support from Red Hat or official Fedora communities.
But both use podman behind the scenes so internally they aren’t that different, but you can think of Distrobox as a more distro-agnostic and user-friendly version of Toolbox. If you’re a home user then stick to Distrobox.