#illumos — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #illumos, aggregated by home.social.
-
Right away this sounds like a task for a "declaratively defined" distros, based on nixpks, guix or any other similar toolkit. There are tools, but no ready-made distro that does that, as far as I know.
The second set that comes into my mind is the "immutable" distros that utilises CoW FS, snapshots of the initial state and some machinery to change it. I'm most familiar with the SUSE famliy, thus I'm thinking of MicroOS, Leap Micro and Aeon Desktop - with snapper and transaction-update one have an access to the post-install state and may replay it anyware.
This kinda similar to what FreeBSD and illumos distros achieve with the ZFS and a "boot environment" concept (administrated via bectl/beadm).
And in the devops world it'd be a packer image applied to a new device.
-
My first suspect for a #login not supporting -- would be something with a 1980s history pre-dating standard #getopt, such as Solaris, which is ironic given that #inetutils has its only -- present in conditionally compiled code targetting Solaris.
#FreeBSD, #NetBSD, and #OpenBSD login all use getopt(), pervasive in these worlds for decades, as do the util-linux login (used by Debian et al.), and the #Illumos and #BusyBox logins.
#suckless login supports -- via ARGBEGIN.