nickwitha_k (he/him)

The guitar binary has a dependency on the curser package which is a deprecated version of cursor with an accidental misspelling. Running the make with sudo replaced this at the system level. Best just to reinstall.

> sudo make guitar

Oh no. Do not build guitar as root.

Very understandable and valid. I find that Prometheus’ query language makes a lot of sense to me, so, I like it. Have you tried Cacti or Nagios?

What about switching to Prometheus for metrics and snagging some premade dashboards in Grafana? Since it’s pull-based, up is a freebie, especially if you expose the node_exporter via your reverse proxy.

Also a good choice. Just never had the need since I knew a bit of regex before learning vim.

The ability to use a powerful, standardized string query and transformation language if one wants? Yes, I do call it an advantage.

CLI text editors have their specific use cases.

Couldn’t agree more. My use cases tend to be:

• text editor
• note taking
• IDE
• config editor
• log viewer
• adhoc data prep
• json viewer

EMACS users sometimes add web browser and email client, among other things but, that’s a bit further than I go. The perf for either of the main two blows nearly any GUI editor out of the water and being able to pipe stdout/stderr to them is just the wonderful cherry on top.

Aww yeah. Feels good.

Getting used to vim has made nano unusable for me. The muscle memory is too strong. That and all of the regex and plugin features (ex. LSP) are just too useful.

It’s an electron app…

They’re both fine choices.

Does indeed sound likely to be an fstab issue, unless system services are being used in a really weird way.

the default is smart

Looking at the systems that are supported, it makes the greatest sense to have the safest failure mode as default. If fault tolerance is available, that can be handled in the entry but, it makes sense but to assume. Having that capability built into the default adds more complexity and reduces support for systems that are not tolerant of a missing mount.

Congrats on passing the exams!

No, this is Linux. Oh. B. D. S… Nevermind.

Depends on your priorities and DE preference. I’m using it as a baremetal hypervisor so, stability and maturity are my priorities. This made Silverblue my choice. If you want KDE, Kinoite would be a good place to start.

nix has a unique way of doing the underlying the logic which as is own benefits.

Honestly, this is what I like least about it. I do not like unique, single-purpose Domain Specific Languages. To me, requiring use of a DSL that is not like common languages used for similar purposes is a major detractor.

Yeah. I had a similar experience. My first successful install, following the docs, didn’t have a network stack. It turns out that the docs are not representative of what’s considered best practices at this point. I also don’t care for needing a new DSL for a single use case.

So, for me, it’s a non-starter. Fedora Atomic is meeting my needs nicely at this point. NixOS has brought some excellent ideas to the forefront and is a great match for some people. I’ll pass until I can use my JSON/YAML/TOML and the docs are useable.

I’d recommend trying out a Fedora Atomic distro. Similar idea but without the extremely niche DSL.

The only reason that I tend to use it is because of the included webserver. It’s not bad but the paywalling of functionality needed for it to be a proper LB left a bad taste in my mouth. That and HAProxy blows out of the water in all tests that I’ve done over the years where availability is at all a concern. HAProxy also is much more useful when routing TCP.