OmniBoot v1.5

Changing IPs of OmniBoot PXE-server

If you like to change the network settings you can edit the file /boot/server.cfg. If you change the server-ip you need to run /boot/make/omniboot> ./om cotherwise modules that depend on a NFS-server will have the wrong IP as part of their kernel-boot-commandline (If you use a module-selection of no-NFS modules as described below this remains obsolete!). However you can press [TAB] and edit that command-line during boot. You need to run this script from a Linux shell and cd to it's folder to run it from there. This script rewrites config-files, so a writable filesystem is needed.

Changing other values in server.cfg does not conflict with anything, so no reconfiguration is required. The variables exporta and exportb allow the setting of additional NFS-shares for the OmniBoot-server.

Yet running your own PXE-Server

Copy OmniBoot to your tftp-root, move the content of /boot/make/gpxe_root to tftp-root and configure your DHCP-server to serve the file lpxelinux.0 as bootfile.
In order to boot modules that depend on a NFS-server via netboot you also need to setup a NFS-Server that shares the content of OmniBoot at a NFS-share named "bootpxe".
Modules that need a NBD-server come with a file nbd.cfg in their menu-folder which is to be used as config file for their required NBD-server-process.

Special "nonfs" OmniBoot compilation

Aside of the OmniBoot PXE-server based on Slitaz (which allows to boot 100% of OmniBoot via pxe) there is a special compilation named "nonfs", created by bash ./om nonfs i All modules that do not depend on any network server after booting (during runtime) are compiled into one iso file, gpxe_root-content is yet moved to root as described above. From here you see the layout which can directly be used by any PXE-server.

Running ad-hoc Windows PXE-server (integrated into OmniBoot!)

There is a windows executable named pxesrv.exe in /boot/make/bin_win which is what it says: an ad-hoc windows-pxe-server which works directly without any configuration out of its folder (except it can be preconfigured with a config.ini aside it). It opens with the most basic config window. You can easily switch it on and off. It includes a simple DHCP and TFTP server and other goodies not needed here.
On the OmniBoot nonfs-compilation (as described above) you find pxesrv.exe copied to root including a configfile named config.ini (the latter yet configured to use lpxelinux.0 as bootfile)
If you like you can also try winnfsd.exe, an ad-hoc Windows NFS-server, also located in /boot/make/bin_win.

Also you might benefit from the following links if you want to setup your own PXE-server:

Setting up a server for PXE network booting (Linux)

TFTP as a service HOWTO (Windows)

Set up DHCP/BOOTP (Windows)

Set up Server for NFS in Windows Server 2003 R2

NBD-Server for Windows