It doesn’t matter. Put it in ~/foo/bar/Baz for all the shell cares.
It doesn’t matter. Put it in ~/foo/bar/Baz for all the shell cares.
If you don’t have root is it really a VPS?
Anyway, unpack the binaries to ~/local/usr/bin
and add that to your PATH.
It’s not quite what you’ve asked for here, but as a Dev I’d be remiss if I didn’t shill for Gentoo.
It ticks your rolling release box, has fantastic docs, a huge package repository (and the community repo Guru), and by design enables almost infinite configurability and customisation. We also have a binary package repository now for popular architectures, so you can choose to avoid compiling if you don’t want to deviate from sane defaults (or only compile in cases where you do!)
On the hardware side, we have fantastic support for a number of architectures, I recently brought up a SPARC system and have some arch64 and riscv in the past.
Finally, even if you just decide to check the distro out, the process of installing, configuring, and maintaining a Linux system is outlined in detail within our handbook, and can provide a peek behind the scenes at what some other distros abstract; it’s a fantastic learning experience for those interested.
Finally, we have fantastic support through volunteers in official IRC channels and forums, as well as unofficial hubs like discord.
Hopefully I’ve planted a seed and you’ll check it out down the line. :)
Contrast that with CLI where if you forgot or don’t know any command there is little help or indicator of what’s available and what can be done without external help.
man
would like to have words with your strawman.
No, this is egregious, even for Dan. Don’t feel bad. I called him out on the forums/article comments.
I’m looking at bringing Dillo back into Gentoo atm. I had to read 15k lines of code, and that’s just what’s different since the last release…
I’m a huge proponent of Gentoo Linux as a learning experience. It’s a great way to learn how the components of a system work together and the distro enables an amazing amount of configurability for your system.
Even following a handbook install in a VM can be a good experience if you’re interested.
I once spent a month automating the production of repositories for each kernel version supported on our HPC and rested every step exhaustively in isolation.
When I was satisfied I ran it with root permissions and hosed the VMs it was running on because a recursive chmod evaluated to /.
Oops.
Pipewire is great .
Write out syslogs to disk or better yet mirror to grayling or something, there might be valuable information right before the reboot.
I’ve also had weirdness where the CPU/iGPU was just faulty and the IME would halt the system. That took weeks to diagnose.
Definitely reach out to support!
Some easy display rules, and a couple of plugins and it’s perfect.