Garuda breaking after one update
So just don’t update it then
It doesn’t tell you up front that it’s going to break
So it’s like update roulette? I, too, like to live dangerously.
Same as any OS, yes
EndeavourOS ftw imo
In any case, I end up wasting all that saved time on my semiannual rewrite of my
neovimconfig anyway.Same until I started using helix, where my only config is adding another language server and setting a theme
welp, there goes my Tuesday.
- be satisfied with neovim config
- see someone has created a shiny new config on github
- add similar stuff your config
- break everything
- spend a week fixing everything
- be satisfied with neovim config
- repeat the above steps indefinitely
I agree, also thanks neovim 0.10 making me spent half a day tracking that obscure line that was throwing errors.
What’s some neovim config you always keep?
Over the years of using Vim both professionally and for my own uses, I’ve learned to just install LunarVim and only add a handful of packages/overrides. Otherwise I just waste too much time tinkering and not doing the things I need to.
I usually keep most of the config. Just I just move them around to make it more comprehensive. The only time I made a huge change during a rewrite was when I learnt about treesitter textobjects.
Endevouros
Endeavour does it for me.
No nonsense arch setup without any bells and whistles.
Yeah, I get that. I do, however, really like how FireDragon comes with a lot of the extension I’d like to use, and with searx as the default web search. It also takes almost no time to switch to a much better KDE layout as opposed to the seemingly script kiddie dr4a6onized default.
You can’t install FireDragon on any other Linux distribution?
I wouldn’t use firedragon. It is a very outdated fork of librewolf, which is hardened even more. While librewolf is only a few days behind regular Firefox, firedragon sometimes is months behind making it a horrible choice for security.
I think it’s a fork of floorp not librewolf. But it used to be that way.
Those two days aren’t really spent configuring, they’re spent learning.
First time maybe, the second time not really
second time doesn’t take two days, but yeah you’re right.
Idk, install arch, then pull make files and dot files from git, wham bam, done how I like it on no time flat.
The arch install guide doesn’t teach you to make dotfiles
Learning to install Arch, now that’s a transferable skill.
If you actually try to understand what’s happening, I think it’s one of the best ways to learn how a system is composed, at least if you install manually. What’s a partition, file system, what does mounting do, chroots, you name it.
I don’t use Arch anymore but still think it’s a great distro to learn the basics while still having the luxury of new binary packages. Manual Arch install abstracts basically nothing away from you, for better or for worse.
Currently on NixOS, I’d say while its engineering is better overall, the things you learn there are much more distribution-specific or maybe concept-specific and often not applicable to other distributions.
I guess there are also probably ways to install e.g. Debian manually, I’ve never seen instructions for it though as there was always the focus on the installer, and frankly I’m not a big fan of apt and all. It always seemed to be much more convoluted than pacman plus it does a lot of stuff for you, whether you want it or not was my impression.
The vast majority of people want to start by using Linux, they don’t want an in depth lecture about Linux. It’s like making someone take a course on bicycles instead of letting them get on the bicycle.
It appeals to a very specific niche who are already familiar with Linux and want that in-depth lecture. It’s not a good approach for beginners, and it’s not a good approach for experimented users who just want to install Linux fast.
Hey, I never said this is what people want, just that it is in fact a transferrable skill. I wouldn’t recommend it to anyone just trying to get their machine running, but if you’re looking to gain some insight, is not the worst choice.
What I meant by [non] transferrable is that the process is so highly specific to Arch that it won’t benefit you on any other distro. You will learn to connect to WiFi on Arch but this will not help you connect to WiFi on Ubuntu or Fedora. The Arch process does not tell you which concepts are generic and which are not. At the end of the day you’ve learned Arch Linux, but not necessarily “Linux”.
Hard disagree. Everything you learn on Arch is transferable because Arch is vanilla almost to a fault. The deep understandings of components I learned from Arch have helped me more times than I can count. It’s only non-transferable if you view each command as an arcane spell to be cast in that specific situation. I’ve fixed so many issues over the years using this knowledge, and it’s literally what landed me my current job and promotions.
Arch is why I know how encryption and TPM works at a deeper level, which helped me find and fix the issue a Windows Dell PC was having that kept tripping into Bitlocker recovery. Knowledge of Grub and kernel parameters that I learned from Arch’s install process is why I was able to effortlessly break into a vendor’s DNS server whose root password was lost by the previous sysadmin before me when everybody else was panicking. Hell, it even helps in installing other distros, because advanced disk partitioning is a hot mess on a lot of distro GUI installers, so intimate knowledge of what I actually need helps me work around their failings. Plus all the countless other times that knowledge has helped me solve little problems instantly, because I knew how it worked from implementing it manually. When my coworkers falter because the GUI fails them and they know nothing else, I simply fix it with a command.
If you use Arch and actually make the effort to learn, not just copy and paste commands from the wiki, you will objectively learn a lot about how Linux works. If you seek a career in Linux, there’s nothing I can recommend more than transitioning to using Arch (not Garuda, not Manjaro, Arch) full-time on your daily driver computer.
Anyways, after about a decade I’ve recently switched to NixOS. Now there’s a distro where the skills you learn can’t be transferred out, but the knowledge I gained from Arch absolutely transferred in and gave me a head start.
Interesting how similar our distro careers are. My switch was also after a long time (15 years). Wouldn’t go back to Arch. Still think it’s a good distro for what it’s trying to achieve.
If you seek a career in Linux, there’s nothing I can recommend more than transitioning to using Arch
A career doing what? Arch is not being used on servers or cloud…
You can learn Linux on any distro. This nonsense is why I can’t take the Arch crowd seriously.
We all have different definitions of “working system”. I call a first time boot into alpine linux (after installing docs and ditching busybox) or openbsd a fully working system.
10 minutes, that’s the time i need to configure my system from A to Z, and after that all i do most of the time is updating it.
Yeah, it is obvious hyperbole.
Quickly having a working system vs. Quick debugging if something inevitably doesn’t work.
I config like 30 mins a day its never good
I installed arch last night in less than 20 minutes. The longest part was figuring out how to connect WiFi from the terminal. But I googled it and it was easy.
2 days?
You guys stop configuring?
Immediately get to work with Manjaro✅
until it violently shits itself
-native Arch, probably
Imagine using an arch based distro that dies on try using the AUR lol, why even bother?
1.It doesn’t die
2.The issue is blown super out of proportion
3.Arch is more than AUR. It’s a bleeding edge, very lightweight distro. And both characteristics go into Manjaro - granted, there’s a two week review period and some stuff installed on top. At the end, you get a super snappy, super nice system with a lot of value added on top of it.
Well it died on me twice and then I gave up 😂
Died on me too, randomly stopped receiving package updates…
I’m a Linux noob, using Manjo for almost two years no prob One time an update needed manual intervention and I’ve fucked it up. But afaik on Arch this also happens so 🤷♂️
Manjaro is usable, but you might want to use something else. I use Arch, BTW.
Here is an alternative Piped link(s):
Manjaro is usable, but you might want to use something else
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
Good bot.
Never happened to me again since I use Arch and endeavorOS 🤷🏻♀️
I’m installing Debian next time. Arch is OK but it breaks too often and keeping everything working in an Arch installation is a full time job. Void Linux is like Arch but more stable. Voids weakness is that some of the underlying libraries are different (something about multilib and glibc I think) and there are certain Linux programs that can never run in void and you can’t get them. Monodevelop and virtual box for example. I might have to switch to something else soon just because I need this stuff. (yes I know about qemu and bochs, yes I know about compiling basic c# programs via the command line, and all of that is unsuitable for my use case). Void seems to be a great choice as long as you don’t need to use Monodevelop or virtualbox though. It’s great at gaming once you switch to x11.
There’s a good chance Debian will have a harder time playing steam games due to older mesa drivers or something but it might be a necessary tradeoff.
This isn’t actually true. They offer both glibc and musl these days. Glibc is the normal one most Linux distros use. Musl doesn’t work with some things, but is still desirable to some people for various reasons. Flatpak could be used to work around this, as it should pull in whatever libc that the program needs. Distrobox would also work. Though again this only applies of using the musl libc version.
Another potential sore point is not using systemd init. There are some things dependant on systemd, though generally there are packages which act as a replacement for whatever systemd functionality is needed.
I still have no idea what’s wrong with Voids fonts though. You are on your own there!
I use arch as a daily driver. Very seldom have any issues, and any issues I do have are from the software. I.e. mesa breaking vaapi, grub breaking boot, etc.
Use stagnant software if you can’t spare 5 minutes once in a while rolling back problematic packages.
I use Debian Stable as my daily driver. No issues with steam. No issues with old packages, everything just works and is, I’m not sure why I’m shocked at this, kinda stable.
I’ve had a Debian server in my basement for 4 or 5 years. I’ve encountered a total of 2 entire issues the entire time I’ve had that running. One of which was actual bullshit that I’m still pissed about but the other issue I eventually fixed on my own. It has worked well enough that Debian deserves a go at being a daily driver next time I do an os reinstall.
I really really wish I could come up with a command line script way to issue a command that makes the computer reconnect to the wifi without human intervention of any kind, without so much as even a single ui password dialog, but that’s not a distro specific thing. I use iwctl right now, it seems to be the most reliable and I’ve tried them all.
I didn’t spend 20 minutes setting up Arch.
I use Arch btw.
Only two days for arch btw? That’s nuts.
