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.

I would think so as well. Possibly it’s because a local VM is harder for them to monitor.

If Windows, it requires a VM and currently infosec is not keen on virtualization in the hands of users.

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!

GUIX is a good example.

Don’t say ansible. It’s barely declarative.

True, but it uses a common language in its Playbooks, which is a significant advantage. I’d like nix if I didn’t need to use nix the language. It’s great concept and the portability is awesome.

To me, 1400 projects is just an insane number, and it’s only possible because they are all so trivial.

Holy shit. I’m going to have to go through my team’s dependencies. I don’t feel confident that someone “maintaining” that many projects is going to be able to keep all bad actors at bay. Not to mention, none of the examples of his libraries that I’ve seen SHOULD be libraries.

And anyone who has been around for a while should remember when left-pad broke node.js. Including unnecessary dependencies, instead of writing trivial code is just bad practice.

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