AmazingQ

... ...

Public Key

npub1m83uxa2qs5nv8sm3ypa6558yu6dzla6e294rwxrvt9thxa0nxc8ss7n4dk

NIP-05 Address

Profile Code

nprofile1qqsdnc7rw4qg2fkrcdcjq7a22rjwdx307av4z63hrpk9j4mnwhenvrcpzamhxue69uhhyetvv9ujuen0w4h8gctfdchxvmgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg5waehxw309aex2mrp0yhxgctdw4eju6t0fxfymx

Publishing to

relay.fountain.fm

relay.primal.net

relay.damus.io

Author Public Key

npub1m83uxa2qs5nv8sm3ypa6558yu6dzla6e294rwxrvt9thxa0nxc8ss7n4dk

Show more details

Last Notes

2026-04-21 12:00:49 GMT

- reply

Longtime listner (circa 2018), first time booster,
You asked about PXE booted servers. For 3 years now I'm running my NAS diskless. Which sounds strange NASes need disks. This is what I mean, there is no disk or partition used for an OS.
It is based on Alpine Linux (NetBoot). The state is stored in a tar file, which is generated by the command `lbu`. This tar file is stored on a webserver.
During boot it does: fetching pxe related boot configuration, fetching kernel via tftp, booting kernel, during kernel boot it fetches the mod-loop via http (kernel modules) and finally fetches the tar file with server configuration.
Then it downloads the required packages and starts everything.
This also means that the NAS is stateless. If it doesn't respond as expected, reboot and it is back in a working state.
PS, the upgrades are automated via ansible playbooks.
https://fountain.fm/episode/4JGNHubSxMA84AgOFg0T
#nevent1q…qhjw