distant VS kiss

The reason being is that I've written a service called distant with a companion neovim plugin, distant.nvim, and want to provide forms of authentication in the same vein as ssh.

I spent the whole day yesterday trying to cross compile distant for the Raspberry Pi 4 and now I am sure I can't do it without your help.

I needed something like this for distant and ended up writing a standalone crate to support parsing and manipulating typed paths.

Wanted to share a new crate I published today geared towards streamlining the setup process of turning a command line application into a service. I'm using this to power the service feature of distant (in an upcoming release) and thought I'd move it out into its own crate.

For something that's more of a prepackaged build-your-own-Linux kit, KISS Linux[0] is also interesting. It's kind of a microdistro with minimal abstraction over the raw guts, and "packages" are just pre-downloaded source code repos that you compile yourself.

The "package manager" is just a shell script. The installation process[1] is entirely manual, so you control every step as you bootstrap up to building your own kernel and installing each subsystem all the way up to compiling and running Firefox. It's pretty neat.

[0] https://kisslinux.org/

[1] https://kisslinux.org/install

kiss with kiss-xorg, nsxiv, st, dmenu with script, tewi, fet.sh

kisslinux.org

A good Bash code to read is some projects from GH user dylanaraps a creator of neofetch and KISS Linux (kiss is a package manager written in POSIX sh) another repo to explore is bashbox (forked from dylanaraps/bareutils) A coreutils written in pure bash.

See KISS for examples - this is a real desktop system used by some people (including me... hopefully)