awk is awesome! I love it, and I do not regret learning how to use it.
That said, my workflow invariably always shifts from starting with awk to do something simply with a tiny one-liner, to then doing that with perl or python, and sometimes even creating a file to make the by-now multi-line scripts more easily readable.
I do not recommend starting with awk, if you do not know other languages already such as Python.
I came across that earlier, and it has some neat utilities, however I wanted to make a mega list as it was missing some of my favorite utillitys . It is very interesting though,
Outside of the whole compiling from source thing, What are selling points of Gentoo over Arch?
Seems most Gentoo users I’ve ran into are either diehards about compiling their own packages or they’ve simply used it for over a decade and are super familiar with it.
My two cents; install uBlue’s Microsoft Surface Images. Here you can find the (WIP) documentation on how it differs from other uBlue images. I’m sure the following lines should pique your interest:
“Replaces the stock Fedora kernel with the Surface kernel
My personal take on what uBlue is, would be that it’s how Fedora would love to ship their Atomic variants if they could ship everything without worrying about those things they can’t (like hardware acceleration, codecs etc). Furthermore, uBlue even has device-specific images; which is just fantastic if you happen to own such a device.
Last, but definitely not least; it’s the best platform in which the transition to Ostree Native Container has been realized. As such, this allows some very unique ways to maintain a distro. For example; if something broke (for whatever reason) on vanilla Fedora Atomic, then… well, you (the uBlue-user) wouldn’t even have noticed it. Because that breakage simply never hit your device. Instead, uBlue’s maintainers noticed the issue -> somehow applied changes to the image so that the image doesn’t ship the issue (by either not shipping the breakage inducing update of the specific package or by shipping the workaround/fix with the image) -> the very next time you update your system (which happens automatically in the background by default) you just go on with your life as if nothing had happened in the first place 😅. So, in a sense, your system is managed such that breaking changes/updates don’t hit you; while they do hit non-uBlue users.
And I haven’t even touched upon how uBlue enhances tinkering or how it allows one to manage (a fleet of) self-customized images etc.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.