I really like these suggestions, I’ve always wanted to contribute to FOSS software, but always felt underskilled. I will add this to my list of things to do to challenge my Linux and basic programming skills.
It’s worth noting that the barrier to entry as a maintainer depends on which distro you’re using at the time. It’s not uncommon for a distro to have a community repository system, like PPAs in Ubuntu, AUR for Arch, MPR for Debian, etc. I’m not very familiar with Mint, and couldn’t easily tell if it has its own or just uses PPAs from upstream.
It isn’t especially taxing on programming skills, and if you don’t pick too complex of a package, the Linux skills required shouldn’t be wildly above your level, but may push you to learn some new things by digging a bit deeper. I haven’t formally maintained public packages, but I’ve needed to build a few over my years using Linux, and it was easier than I’d expected to just build one. It may be easier than you think, too.
Thanks for the additional info. I installed Arch, it was far less daunting then I anticipated. In fact, it was prettt straightforward. I’ll look into your suggestion.
A biggie you miss is the toolchain: the compiler/binutils/linux-headers/libc/libstdc++ combination. The libc and usually libstdc++ are key components of any install. The other parts usually don't make it to non-dev-desktops, but the distro couldn't be made without them, so they're virtually always available as packages.
Only exception is if the entire distro is cross-compiled or it's made exclusively for containers, but those kinds of special distros break every rule imaginable anyway. Some might not even ship a bootloader or a Linux kernel by themselves.
The hardest part is when you need to use tools from windows, or to develop a program for that system. Also, many things require good amount of configuration, and with that, expertise at what you doing. I’m currently struggling with solving bug as to why VSCodium will not debug in external terminal.
Hello OP, warm welcome to the schizophrenic community that is linux! I’m running this exact same setup as you intend to.
Couple of points I’d add:
Nvidia and linux is a shit show. You either use the gimped mesa drivers (not so good), or the closed source drivers (even worse), especially on Wayland. If you still want to try it out, I suggest you stick with X11. I was using a 3080Ti and gave up trying to get it to work on Wayland+KDE Plasma v5 without screen glitches and bought a 7900XTX instead. AMD works out of the box without further configuration. I’ve had nothing but issues with Nvidia. For the GPU neckbeards that are going to achytually me, please don’t, I have no skin in this game as I have a bunch of cards from both.
I am not a pro nor expert in the foundations of linux, but I more or less know my way around its fundamentals (enough not to get into too much trouble), so I would actually suggest not getting into a rolling-releasing distro like Tunbleweed until you are super comfortable with a little hands-on and figuring shit out. Pop!_OS might be a better bet for your use case for now because it comes bundled with Nvidia drivers, but it uses a GNOME derivative (cosmic DE) so you don’t actually get the KDE experience.
Having said these, I absolutely adore Tumbleweed and KDE, I’ve been half daily-driving it but the gaming experience is not the absolute best (be prepared to experience weird glitches and crashes). If a flawless gaming experience is non-negotiable to you, stick with Windows. But if you’re ready to explore the quirky wonders of linux, the beauty of it all is the experience and the real reward is the friends you make along the way.
Keep notes on what you do including outcomes. You can always reinstall, skip all of the extra crap you didn’t need to mess around with and have a good clean system without having to back track.
It’s easy to forget the steps you took to do something on your computer, especially several months later when you’re trying to upgrade. Sometimes when you try several different ways of solving a problem, it’s easy to forget which method was successful the next day!
It’s a very good idea to take notes about the software you’ve installed and configuration changes you’ve made. When editing configuration files, it’s also a very good idea to include comments in the file explaining the reason for the changes and the date they were made.
This has saved me so much grief. If ever I mess up a system so badly that I want to re-install or when I want to set up a new machine, having a clear set of notes makes it a breeze.
It’s easy to forget the steps you took to do something on your computer, especially several months later when you’re trying to upgrade. Sometimes when you try several different ways of solving a problem, it’s easy to forget which method was successful the next day!
I’m very confused about what OP considers customization. My only experience has been setting up my home server so far, so maybe I’ll be compelled to do more “customizing” when I make the switch on my PCs.
Does installing a GUI on Ubuntu Server already break that rule? Or is it a success because it’s only software? It’s definitely not “out of the box”.
Debian, I use one Gnome extension but could easily do without it. All the defaults are fine if you just want to sit down and browse, edit media, create documents or write code.
ok >w< I understand that and you are free to customise that a lot if you want to, it’s ok!! But I personally want to keep the brand and colors of the vanilla distro!!! It’s a cuter and more honest experience c:
init system, without which you’d be left with only one program running at a time
some programs are written in interpreted language (e.g python, shell, perl), so the interpreter would also be required
C library, without which none of the above would function (yes, even if all the programs are statically compiled, it still has that library included with each executable)
this one is not necessary for the runtime, but is needed for creating a working system: toolchain – preprocessor, compiler, linker, assembler – all the stuff for transforming the source code into executables
Another comment mentioned Linux From Scratch, I’d totally recommend that, but it would take so much of your time manually building stuff (which is why it is so educational). If you don’t have the time, you may want to opt with Gentoo instead.
The multi-user system, which is a bunch of config files, libraries, utils and UIs, that deal with logging in or doing stuff as a specific user.
The logging system. Individual applications can simply log to a different file each but for system services the logging is usually centralized and offers additional features (like logging remotely etc.)
Setting up networking is pretty much mandatory these days.
Once an admin I know forgot to install a text editor. Imagine the fun editing files with cat, grep, awk etc., now imagine you have to use it to browse the web.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.