5 ms·
If you're not ready for the LFS plunge, install and configure an Arch Linux system with a graphical desktop environment. I learned more about Linux in that 8 (
by freedomben 6y ago
If you're not ready for the LFS plunge, install and configure an Arch Linux system with a graphical desktop environment. I learned more about Linux in that 8 (non-consecutive) hours than I had in the couple of years preceding.
Then study for the RHCSA and RHCE v7 (v8 is all Ansible now). Arch Linux and RHCSA and RHCE taught me a ton about Linux and made me super comfortable with my Linux desktops and servers.
- R0b0t1 6y agohttps://knowyourmeme.com/memes/install-gentoo https://knowyourmeme.com/memes/install-gentoo Goes even deeper than arch. The desktop profiles make it almost set-and-forget now.
- yjftsjthsd-h 6y agoI'd say Arch, then Gentoo, then LFS. Arch provide you with usable binary packages and leaves you to know what to install and how to configure it. Gentoo makes you actually build those packages from source and gives you more control over how the process works. Then LFS takes away even what portage was doing for you and makes you do the build process yourself by hand from scratch.
- t-writescode 6y agohttps://xkcd.com/456/ https://xkcd.com/456/
- znpy 6y agoIt's kinda sad that no one recommends Slackware Linux anymore. Back in the day there we used to say: "when you know slackware you know Linux. When you know red hat all you know is red hat". Effectively when I got into slackware my computer wasn't 100% working all of the time but I learned a lot. I then moved on and years later I got rhcsa certified and that's very worth it too. Not sure about arch, I never really used that, but I can vouch for slackware, Gentoo and the RedHat/centos/rhcsa thing.
- teekert 6y agoI started with Slackware (~18 years ago) but it was just pain with no standard package manager. Sure, later I found slapt-get and I turned to dropline-gnome at some point. But moving to any apt distro, Mandrake, Arch or even Gentoo just felt like a warm bath to me back in the day.
- nonbirithm 6y agoI tried using Slackware since everyone said it was the most Unixy distro, but then I ran across a bunch of issues. I don't want to seem like I'm berating Slackware or anything, since I might not understand how to use it coming from Arch, but this was just my experience. I remember needing to use Clang for ccls but found out that the version of CMake included didn't support C++17, then when I tried upgrading CMake I found that some library named libarchive was too old to use as a dependency, so I essentially had to spend hours of time upgrading things to versions not supported on Slackware just to get to the point where I could use Clang. I'm pretty sure I wouldn't have to spend all that time if I was using pacman instead where the important packages are all up to date and I could get to work within a few minutes. Honestly only the distros with a large enough community like Arch or Gentoo would probably have enough people to submit and maintain even the most obscure packages. Also, there was no easy way to do a system upgrade. In Arch Linux, which is what I'm used to, you can usually do 'pacman -Syu' without too much fuss, but the Slack document for upgrading the kernel is a multistep process that I couldn't successfully complete. (It even wishes you "good luck".) Third-party packages on slackbuilds have no automatic dependency resolution either (!) which was very painful every single time I needed a package not in the official repository, which was all the time in my case. I could literally feel my heart sink every time I needed a slackbuilds package and it required upgrading a system dependency. Apparently this was a political decision instead of a technical one[1], which I don't understand because pacman handles it fine. I also had integrated graphics issues that caused Firefox to hang on startup or Love2D to freeze, forcing me to kill the X server, for which I found no solution. Arch ran them fine. This was on a ThinkPad, by the way. It could just be a philosophy thing, or that people with my specific needs are better served by other distros, or maybe I've been hopelessly spoiled by Arch and can't see the benefit Slack brings over it yet. But I have to admit I am still mildly curious about it, just not in the sense of using it as a daily driver. [1] https://slackbuilds.org/faq/#deps https://slackbuilds.org/faq/#deps
- ubercow13 6y agoI learned a lot using Gentoo back in my youth, but I am not sure it is much better than Arch for general Linux knowledge. A lot of the effort involved was with configuring Portage and fixing build problems rather than learning my way around the system or configuring the OS itself.
- BlackLotus89 6y agoThe gentoo installation process is better documented and you learn a lot more about compilation. I started with gentoo, installed lfs for fun and years later made the switch to arch. I think I learned a lot of things I didn't know when installing lfs, but nothing new when installing arch (had used gentoo for at least 5 years at that point thought). I think that the main sticking point is the documentation. It was certainly the reason why I went with gentoo at first, not because of the control over the system, but the fact that there was a great wiki (that was often down :D) and great official documentation that lead me every step of the way. I'm of the firm believe that every linux install can teach you everything as long as the documentation doesn't skip on things. You won't learn anything from lfs if you just copy paste commands and you can at that point install ubuntu.
- teekert 6y agoI learned a lot from Gentoo, and then from Arch, my stormy relationships with both took place over 10 years ago but to this day I use the knowledge I gained. Linux is just "familiar" to me now (things like fstab, the root folder structure, popular partitioning schemes). Now that I'm 38 I don't have the time for Gentoo anymore but I'm glad we got to know each other when skipping a night didn't cause me any problems :)