@bazkie well, you can to an extent.

• Just like #SysVinit and #Xorg got yeeted because they enshittified due to neglect...
  • See #toybox + #musl / #linux as in #mkroot, which is @OS1337's upstream…

@stilic @SRAZKVT yeah, but either of these basically implement either the same or a subset of #SystemD or #SysVinit.

• Even #toybox's #init [oneit] works by being a subset if the init by just running whatever script is under /etc/init…

But that's because essentially doing either manual (SysVinit) or hierachical-automated (SystemD) dependency resolution is the only way to make it any #Linux or #Unix'esque system work…

• Including #macOS which uses #LaunchD aka. the inspiration for SystemD that doesn't get hated by #BSD fans…

@requiem np.

It's basically a minimalist #toybox#musl / #linux distro designed on being brutally simple, reproduceable, auditable and efficient.

• Mostly for #FrugalComputing and targeting systems that current mainstream #distros don't serve.
  • Basically trying to be the "bare minimum I could use to work from as a sysadmin"...

@nmott consider #toybox then?

• It's done by a fmr. #BusyBox maintainer on a clean new codebase and is used as #Userland for #Android…

@mrmasterkeyboard @reiddragon I mean, that would be cool based upon the command it's called up.

• evi: basically vim minus #AIslop.
  • Basically loads the init.vim (like #vim does) configuration file and moves on from there`
• nevi: basically neovim minus #AI #slop.
  • Loads the init.lua configuration like #neovim would.
• neville: basically something to add/remove NvChad or other preconfigs.
  • In case someone wants to switch things...

It would also make it convienient to go between "basic mode", "comfort mode" and "perdormance mode"...

• So if one "riced too hard" they don't end up with a broken editor they can't fix themselves...
  • Which is desireable for a productivity tool.
  • Propably you'd even add something like a -noconf flag to ignore all configurations and just load the blank evidefaults...

After all, people accept that with "#StallmanOS" aka. #GNUemacs too. (See org mode)...

• And #toybox does the same with it's "single binary" mode where one calls up it's vi implementation buy calling the binary and then the vi subcommand like ./toybox vi ...
  • So it would be possible to do it, but I'm shure you'll figure out that once you want to cross that bridge...

@jack consider #neovim / #nvchad or just back to the basics with #nano & #ne?

• Or grab' yourself #toybox's #vi implementation for maximum "rawdogging"...

@arh consider @OS1337 (or rather #mkroot / #toybox)…

https://www.youtube.com/watch?v=Sk9TatW9ino video feat. @landley

https://landley.net/toybox/

@alina personally I can also recommend good #CLI tools that just work.

• #mc (#MidnightCommander)
• #neomutt
• #aewan (for designing #TUI interfaces)
• #enc
• #btop
• #ytdlp
• #lynx / #LynxBrowser
• #curl
• #toybox (which is a minimalist #userland for #Linux)
• #ne (nice editor)
• #nvChad (when you want to turn #neovim into an #IDE but don't know where to start)

And many more.

• Cuz I work on the idea of a #MDA / #80x25-centric Linux-distro (@OS1337) that is focussed on #FrugalComputing!

@decryption I guess you gonna provision said VMs with passthrough to the drive(s) paid for and just let it boot into a "ROM" with like a minimalist linux that barely runs like dropbear and only gets customized with the SSH-Pubkey of said client to allow only them to login.

• After all, people should use this as mere "data storage" and not much more.

Consider #mkroot (#toybox) and maybe add vsftpd or Pure-FTPd to it if you don't want a full phat debian on it?

• Certainly you don't want people to abuse your box for shitcoin mining...

• @OS1337 sadly isn't ready yet for such a setup...