forked from daid/EmptyEpsilon
-
Notifications
You must be signed in to change notification settings - Fork 0
PXE Netboot
Oznogon edited this page Jun 23, 2026
·
1 revision
EmptyEpsilon can be set up to boot diskless clients via PXE (Preboot eXecution Environment), loading the game over the network from a central server. This is useful for running EmptyEpsilon in a lab or arcade setting without managing individual machines.
The netboot/ directory in the repository contains:
-
build_netboot_system.sh: A shell script that builds a PXE-bootable EmptyEpsilon system, preparing the network boot image with the game binary, resources, and required libraries. -
config_manager.py: A Python client-side script that manages connection configurations for PXE-booted clients. It can set up server connection details, including automatic connection to a specific server on boot.
See the README file in the netboot/ directory for more information.
PXE netboot allows multiple client machines to boot EmptyEpsilon from a single server over the local network. The general process:
- Set up a PXE server (DHCP, TFTP, and NFS or HTTP) on your network.
- Run
build_netboot_system.shto create the boot image containing EmptyEpsilon and its dependencies. - Configure
config_manager.pyto set autoconnect parameters and other client preferences. - Boot client machines via PXE, which then load EmptyEpsilon from the network server.
- Fallback content paths explains how content loading works in PXE environments, where only the binary is provided over the network and assets must be served separately.
- Home
- Building and installing the game
- Configuring the game
- Playing the game
- Officer roles and screens
- Captain
- Main screen
- Ship window
- Crews of 5-6 players
- Crews of 3-4 players
- Single-player crew
- Game Master (GM) screens
- Extra screens
- Minigames
- Weapon types
- Officer roles and screens
- Extending the game
- Troubleshooting
- Fork content