Initially, books along with using Linux. Then, as you mentioned earlier, trial by fire. I started with RedHat when win98se pissed me off for the last time. I just said "fuck it", fdisked my desktop's hard drive and decided to learn Linux. Once I learned the basics, I switched distros to Mandrake. Got comfortable with that, switched to SuSE. Stuck with SuSE for a bit and then decided to try a distro called Sorcerer.
While I would generally not recommend that path, if you can work it out, brilliant.I went right to gentoo knowing literally nothing about Linux (besides knowing a little about POSIX) after I couldn't get RedHat installed because the installation script failed somewhere because of my hardware. Everyone can just jump right to gentoo. It's really not all that hard if you have any kind of attention span and patience. The "lol you compile stuff all day" argument doesn't even matter anymore, even "old" and underpowered ARM boards are fast enough to handle it and on modern computers it really doesn't matter. Gentoo's capability of avoiding "features" included in software through use flags to trim down bloat is now more relevant than it ever was.
That being said, if you have the fitting hardware, maybe try one of the *BSDs first. Linux userland regarding critical software is going downhill with no signs of stopping.
I have the kernel save its config file in /proc/config.gz, so on any kernel update, I'll symlink the new kernel to /usr/src/linux then run zcat /proc/config.gz > /usr/src/linux/.config followed by a make oldconfig. With any new options being shown during the oldconfig. I like to verify afterwards with make menuconfig to ensure that I've understood what ever new options were shown.Also you can sit down and roll a custom kernel for your hardware and usually only have to very slightly touch it for later hardware updates. This used to be easier back in the day since the kernel has become a lot more complex with a lot more options, but if you are a bit hardware literate and read the option descriptions, that also is mostly a game of patience
If Linux is for autists, who are the BSDs for?Does *BSD count or should I make a separate thread if the need to sperg about it in length arrives?
I'm currently twiddling with FreeBSD (NetBSD always got a uvm_fault on boot after attimer) trying to set up an X environment with JWM. It's my first time trying to rice up an OS after doing a little research.
Get really proficient with GNU Emacs, try to write a major mode. Me, I'm trying to install Arch+i3wm and customize all the configs, Currently the display has gone wonkey (very tiny text) after installing nvidia drivers. I think it's a DPI issue. I have an RP4 too, but can't think of anything to do with it until retropi becomes stable.Getting bored with quarantine and shit, anyone got any projects to recommend? I don't use Debian as my daily driver but I do have a VMware box where I host headless Debian VMs. Things I've done so far is make a Pi-Hole server, Plex, set up NTP, firewall and I think that's about it. Will probably set up a VPN or something next but I don't really have any more ideas.
Port postMarketOS to an old phone you got lying around.Getting bored with quarantine and shit, anyone got any projects to recommend? I don't use Debian as my daily driver but I do have a VMware box where I host headless Debian VMs. Things I've done so far is make a Pi-Hole server, Plex, set up NTP, firewall and I think that's about it. Will probably set up a VPN or something next but I don't really have any more ideas.
Would this be a dual boot?I'm still keeping around a windows machine for gaymen but I'm itching to just throw Linux on it and rip that band-aid.
Any insights regarding partitioning schemes between ssd and hdd, gaming, and distros? It will be for development, gaming and personal usage.
This won't be my first linux install but I don't consider myself an expert (suse on laptop, ubuntu on work machine)
afaik if I keep a dual boot I keep window's bootloader because it won't play nice otherwise. If I'm nuking windows from orbit, I want to make sure it's clean.Would this be a dual boot?
Personally I like to approach partition tables by minimizing my interactions with them. What I would do with multiple disks (or even a single one) is use LVM. That way you can change the layout of the SSDs and HDDs later if you find out that it's not what you want. You still need to have a partition table on at least one of your disks, (and an ESP if you're booting from UEFI) but after you've done the install process, you don't need to hear about partition tables ever again. That's why I think it's neat.