- Booting from USB
- Booting from PXE Boot Server
- Booting Zero-OS on a VM using QEMU
- Booting Zero-OS on VirtualBox
- Booting Zero-OS on Packet.net
- Booting Zero-OS on OVH
- Create a Bootable Zero-OS ISO File
Zero-OS handles the following kernel params:
debugsets the initial log level to debug, can be changed later via the client.organization=<org>When set, Zero-OS will only accept ItsYou.online signed JWT tokens that have theuser:memberof:<org>role set and are valid If not provided, zero-os will not require a passwordzerotier=<id>Join this zerotier network on bootztid=<identity>Full zerotieridentity.secret[optional]. If not provided a one will get generated for you. Zero-OS does the best effort to generate the same one every time it boots.developmentIf set, start the redis-proxy allow direct client connections, also opening the required client ports. If not set, no direct client connections will be allowedsupportIf set, gives unconditional access to our staff (threefold sysadmin) members. Please only add this if specially required
Different booting modes can be achieved by mixing and matching the boot params documented above.
zerotier=<network-id>
development [zerotier=<networkd-id>]
zerotier if not set, both the robot and the redis server can be reached over all interfaces
Adding
debugparam to any of the above flag combinations will output verbose logs.