hrmpf VS void-mklive

I use zfsbootmenu with hrmph (https://github.com/leahneukirchen/hrmpf). You can see the list of packages here (https://github.com/leahneukirchen/hrmpf/blob/master/hrmpf.pa...). I usually build images based off this so they’re all there, otherwise you’ll need to ssh into zfsbootmenu and load the 2 gb separate distro. This is for home server, though if I had a startup I’d probably setup a “cloud setup” and throw a bunch of servers somewhere. About of times for internal projects and even non-production client research having your own cluster is a lot cheaper and easier then paying for a cloud provider. It also gets around when you can’t run k8s and need bare metal. I’d advised some clients on this setup with contingencies in case of catastrophic failure and more importantly test those contingencies but this is more so you don’t have developers doing nothing not to prevent overnight outages. A lot cheaper than cloud solutions for non critical projects and while larger companies will look at the numbers closely if something happened and devs can’t work for an hour the advantage of a startup is devs will find a way to be productive locally or simply have them take the afternoon off (neither has happened).

I imagine these problems described happen on big iron type hardware clusters that are extremely expensive and spare capacity isn’t possible. I might be wrong but especially with (sigh) AI setups with extremely expensive $30k GPUs and crazy bandwidth between planes you buy from IBM for crazy prices (hardware vendor on the line so quickly was a hint) you’re way past the commodity server cloud model. I have no idea what could go wrong with such equipment where nearly ever piece of hardware is close to custom built but I’m glad I don’t have to deal with that. The debugging on those things work hardware only a few huge pharma or research companies use has to come down to really strange things.

ZFSBootMenu or hrmpf.

hrmpf

I'm curious how that compares with this void live distro: https://github.com/leahneukirchen/hrmpf

void-mklive zbm-wiki hrmpf

As for recovery images, just download hrmpf and be done.

Hrmpf rescue system, built on Void Linux\ (18 comments)

You can always use void-mklive to create your own iso from the current git master.

You can build your own iso - void-mklive scripts

In https://github.com/void-linux/void-mklive there is ./mklive.sh -a x86_64-musl -r /path/to/host/binpkgs, in my search I found some references to /hostdir/binpkgs/, but I have no such path on my system.

Use the live image maker https://github.com/void-linux/void-mklive

the live isos have an autoinstaller, but it's not really documented. you can take this config file, edit it, and host it somewhere, then add auto autourl=http://example.com/your.cfg to the kernel command line when booting the iso to run the autoinstaller

Create a custom iso using mkive, with the lastest kernel version.

dbus elogind lxdm NetworkManager polkitd. (based on the void-mlive script)

try logging in as root, it may be this issue: https://github.com/void-linux/void-mklive/issues/306

The 2022 isos are broken (https://github.com/void-linux/void-mklive/issues/292. I wonder why they still haven't updated the isos...)