Garuda. I tried it because it’s supposed to be “gamer” oriented. I thought it meant it would make it easier/smoother for gaming. What they actually meant was it felt like being locked inside a gaming PC with flashing and spinning RGB lights everywhere. No fucking thanks.
It’s funny, I was really excited for Ubuntu when it first released, and actually quite enjoyed it. On the other hand, RPM distros seemed like an absolute mess, at that time. Now it’s the exact opposite. At least in regards to Fedora, it’s a very well thought out and maintained distro if you want things to just work, and Ubuntu makes me uncomfortable.
No downvote here my friend. I love arch, but that doesn’t mean it’s for everyone. Plug-and-play distros are great too, they just have different strong points.
Haha, I’ve been daily driving slackware since the late 90s. I like to tinker and install a lot of stuff. I seem to break anything with an automated package manager and dependency resolution.
Nah, I’m just a hobbyist. I’m a n00b compared to all the regulars in the slackware channel on IRC. But I love tinkering and learning. I’d need your help to install vanilla arch, just like you’d probably need mine to get started on slackware. (The slackware install is actually super easy).
I’ve been trying to distrohop the past couple months, see what else is out there. I wasn’t paying attention installing Garuda and borked my EFI partition. I did manage to chroot into my still working slackware partition, but I couldn’t figure out how to re-install grub. So I formatted and did a fresh slackware install.
It is a great book, although a bit outdated. In particular, nowadays egrep is not recommended to use. grep -E is a more portable synonim.
Some notes on you script:
You don’t need to escape slashes in grep regex. In the sed s/// command better use another character like s### so you also can leave slashes unescaped.
You usually don’t need to pipe grep and sed, sed -n with regex address and explicit printing command gives the same result as grep.
You could omit leading slash in your egrep regex, so you won’t need to remove it later.
nowadays egrep is not recommended to use. grep -E is a more portable synonim
Not directed at you personally, but this is the kind of pointless pedantry from upstream developers that grinds my gears.
Like, I’ve used egrep for 25 years. I don’t know of a still relevant Unix variant in existence that doesn’t have the egrep command. But suddenly now, when any other Unix variant but Linux is all but extinct, and all your shell scripts are probably full of bashisms and Linuxisms anyway, now there is somehow a portability problem, and they deem it necessary to print out a warning whenever I dare to run egrep instead of grep -E? C’mon now … If anything, they have just made it less portable by spitting out spurious warnings where there weren’t any before.
GNU grep, the most widespread implementation, does not include egrep, fgrep and rgrep for years. Distributions (not all, but many) provide shell scripts that simply run grep with corresponding option for backward compatibility. You can learn this from official documentation.
Also, my scripts are not full of bashisms, gnuisms, linuxisms and other -isms, I try to keep them portable unless it is really necessary to use some unportable command or syntax.
GNU grep, the most widespread implementation, does not include egrep, fgrep and rgrep for years. Distributions (not all, but many) provide shell scripts that simply run grep with corresponding option for backward compatibility. You can learn this from official documentation.
It seems you need to read the official documentation yourself. While it’s new information to me that egrep is no longer a symlink, as it used to be a couple of years ago, but a shell script wrapper to grep -E instead, the egrep command is to this day still provided by upstream GNU grep and is installed by default if you run ./configure; make; make install from source. So it is not a backward compatibility hack provided by the distribution.
You can check for yourself. Download the source from ftp.gnu.org/gnu/grep/grep-3.11.tar.gz, unpack and look for src/egrep.sh or line 1756 of src/Makefile. Apparently the change from symlink to shell script was done in 2014, and the deprecation warning was added only last year.
In any case, my larger point is that the depreciation of egrep was a pointless and arbitrary decision that does not benefit users, especially not veterans like myself who have become accustomed to its presence. I don’t mind change, but let’s be honest, most people are not in the habit of checking the minutiae of every little command line utility they use, so a change like this violates the principle of least surprise. It’s one thing if things are changed with a good reason and the users do not only suffer the inconvenience of the change but get to reap the benefits of it as well, but so far I haven’t found any justification for it yet, nor can I think of any.
So if there is a portability problem with using egrep now, it’s a self-inflicted portability problem that they caused by deprecating egrep in the first place.
Also, my scripts are not full of bashisms, gnuisms, linuxisms and other -isms, I try to keep them portable unless it is really necessary to use some unportable command or syntax.
I’m sorry for your loss, however the egrep deprecation is a fact. Of course you can continue using it as a veteran, but it is not correct to recommend this to beginners.
You are strawmanning, and your links are not countering any point I made. I never disputed the depreciation as fact, and I never recommended that beginners should use egrep over grep -E
I disputed your claims that the egrep command has just been a distro hack all these years, when in fact GNU to this day still distributes egrep through its source tarballs and only very recently started to warn about it through the wrapper script. And again, the only “portability problem” here is the fact that they deprecated it in the first place, i.e. a self-inflicted one.
Then as a Linux and Unix veteran I gave my subjective opinion by lamenting and criticizing the fact that this depreciation happened, and how changes like this always feel like unnecessary pedantry to me. Yes it’s an expression of frustration, but I am allowed to feel frustrated about it. I don’t need people like you invalidating how I feel about breaking changes in software that I use daily.
Arch. Rolling release is too much maintenance and AUR can be a pain. I do like the minimalist approach though.
For those of a similar opinion and aren’t familiar with it, check out Void. Also a minimalist rolling release, but aims for more stable packages so less updating. Decent package selection in their repos as well.
pop!_os That’s what I run for desktop I like flatpak better than snap and it has some other nice enhancement over Ubuntu. For my servers I still use Ubuntu.
Ubuntu, after the third consecutive release that broke previously working hardware. That was a while ago and I haven’t tried it recently, but given snap I’m not really inclined to.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.