If you know how to use git, you will know how to use docker (provided you know what you want to do). They are completely different programs, yet you can quickly grasp the other instinctively.
Now, Photoshop and Blender - they are also different programs, but if you know Photoshop, you still need to relearn Blender’s interface completely.
This is why I prefer terminal programs in general. Unless it’s more convenient to use GUi, i.e. Drag&Drop file manager, some git tools etc.
With the amount of different distros you’ve tried (though mostly derivatives of Arch/Debian), I’m actually surprised to see that you haven’t used any derivative of Fedora. Is there any reason in particular?
I forgot to mention Fedora Silverblue. I’ve used it after Micro os and it was a better experience. Fedora seems to have a better out of box experience and had no issues.
I’m not surprised to hear that you preferred Fedora Silverblue over openSUSE MicroOS. Don’t get me wrong, I think that openSUSE Aeon/Kalpa (current names for openSUSE MicroOS Desktop) have a lot of potential. However, as it stands, Fedora’s Atomic Desktops are just more mature.
Outside of Microsoft and Windows, what’s the application for it? Does Linux or UNIX have much use for TPM? Pardon, my ignorance, but I bet this is a good place to ask!
It scares me. What if the chip dies? How am I gonna be able to get my stuff? I don’t fully understand how it works, but where is the encryption saved? On the chip itself or somewhere else?
I’ve got Ubuntu on my server, mint (xfce) on an old iMac, and I really want to install Asahi on my m1 Mac mini, but my wife also uses that machine and I don’t think she’d like using asahi.
I love xfce, I’ve tried some WM like AwesomeWM and I see the appeal for sure, it just takes a while to get used to, like VIM, which I want to mess with as well. Asahi Linux looks super good, but I honestly don’t dislike macOS that much.
I think about it like a tree structure for both. With a gui you have to move your mouse around to various places, with a cli each character branches off into another tree. Mathematically you can handle more options faster with a CLI.
I attempted to try Garuda Linux (cinnamon) on a mini PC (Ryzen 5800H based APU), but graphic artefacting was a constant issue as soon as the install started.
After several tries I had to abandon ship and wait till a new release to maybe try again, if I remember. Not exactly “Nope, this one’s not for me” as I had yet to properly try it.
Otherwise, I tried Crunchbangplusplus and just gave up for being a bit too minimalist or not yet ready for prime time as I kept geting issues after issues and did not have the patience to wrangle the whole OS for everything from getting network working to audio and screen issues on my system.
Anyways, it is always fun to try new systems/apps/protocols and see where thing are headed towards.
After using Arch based distros for more than a year when I use any Debian/Ubuntu based distro it really feels like they aren’t for me, at least when it comes to daily driving. I still have a laptop with PopOS that I use for school, stable distro is a better option in my oppinion for that usecase because I use it twice a week (unless it’s summer or winter in which case I don’t use it at all).
In 2007 I tried Ubuntu and it was weird, then again in 2008, no! In 2009 I found Mint and was really happy, until they stopped supporting KDE. Then I tried a ton of distros, Xfce, no. Lxde, no. open suse, no. fedora, no, lots of others, no. I finally found Kubuntu and I have been on it ever since. Even tested Neon lately but hated it.
Kubuntu does what I want it to do.
Linux always seems scary at first, but once you learn enough, it's super easy.
Yeah, did you find mint easy to use? I’m in Ubuntu and thinking about switching. I just worry about driver support, cause everything works on Ubuntu for me. I try and apt get everything I can TBH.
I really liked Mint at the time, but only the KDE version, and would never have left if they hadn't stopped supporting it. They had great nVidia support. I no longer have nVidia on any of my computers because it's just annoying to fight with that mess.
Plus Linux as a whole has better driver support than it used to.
Honestly, depending on whether you count it or not, LFS. I have not tried Gentoo yet, though I want to one day, for the learning experience, and yet I already know that compiling everything is not something I enjoy.
I can get by with OpenSUSE and Void (kinda), I’ve used Debian for a few weeks, I’ve used Fedora for a month or so, I’ve used Ubuntu for a bit, I’ve tried PopOS for a week or two, I’ve used NixOS for a few months, and I’ve used Arch for most of my time on Linux.
Currently I’m on Arch, but I don’t like rolling releases that much. At the same time, I am also not a fan of immutability, as there are some programs I need that cannot be installed on an immutable distro, so that’s why I’m on Arch. Why am I only using these 2? Because they are the only distros that have all the packages I need (excluding the specialist software that I need for university). By the time I discovered Distrobox (which would solve this problem), I was already on Arch. I’ve also done some changes to my setup and as such, I’ll need to wait for some new features to make their way into program releases and into the NixOS Stable repo with the following release. Until then, I’m on Arch.
Gentoo is useless for learning how things work. Back in the 00s when I still had time to hang out at events it was always quite ridiculous at what kind of basic stuff the gentoo crowd got stuck at - and with the tooling 15+ years more polished now I’d expect what is actually going on is way more hidden than back then.
If you do want to understand how things work just build a minimal system - either on spare hardware, or qemu/kvm. Don’t go with systemd, or other fat userland options - that just makes you compile a lot of dependencies not adding value for learning.
Use some lean init (or just write one yourself), and some lean shell.
I’d just start from very simple kernel and static init, and work my way up to adding more functionality. I’d use kvm with rootfs on p9fs - that allows playing with it without having to build images. I can throw together the initial invocation, if you’re interested.
Then start building simple core elements in a language allowing easy static linking - I’d use C with dietlibc or go. Start adding core userland programs, explore initramfs (without using something like dracut), add dynamic libraries and explore the dynamic linker, … - if you’re interested we could set up a matrix channel for questions (typically with some lag, though), and do a github repo to follow along.
LFS iirc goes for full desktop - the high level userland is very complex, but easy to understand when you know the basics. You pretty much learn how to compile lots of libraries - which has limited use. A full LFS style desktop I’d no longer recommend nowadays - it’s just too many dependencies to deal with. I used to build my own system (not following LFS) until the Xorg fork made it sigificantly more complicated - and things got just worse since then, and I never was using a complicated UI stack.
edit: I had a few minutes, so I’ve thrown this together github.com/bwachter/lll - you should easily get a kernel with a custom init running, and have enough to start experimenting. If you or anyone else is interested to go deeper I’ll set up a matrix channel for guidance.
Ubuntu gnome. Wanted to install a gnome add on (hibernation button), searched how to do it and learned there’s a section in the gui store but couldn’t find it. Searched for that and turns out they removed the add ons section from the store in the latest version and I need to use a browser. Tried to install it from a browser and it still didn’t work. Tried the other browser and failed again. Searching for that discovered that the pre-installed browsers are snap packages and can’t interact with anything else 🤦
Instantly switched to kubuntu. It had the hibernation button out of the box
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.