The example menu.lst
entry below assumes GRUB loads the binaries via the network. The loader is configured to use the TFTP server as its file provider which in turn requires the ORe network switch to perform its duties.
# menu.lst set ND = "(nd)/tftpboot/drops" set BIN_PATH = "$(ND)/bin" title Fiasco + Loader + L4Linux kernel $(BIN_PATH)/bootstrap modaddr 0x02000000 module $(BIN_PATH)/fiasco -nokdb -serial -serial_esc module $(BIN_PATH)/l4v2/sigma0 module $(BIN_PATH)/l4v2/roottask module $(BIN_PATH)/l4v2/names module $(BIN_PATH)/l4v2/log module $(BIN_PATH)/l4v2/dm_phys module $(BIN_PATH)/l4v2/simple_ts module $(BIN_PATH)/l4v2/l4io module $(BIN_PATH)/l4v2/ore module $(BIN_PATH)/l4v2/l4dope --l4io module $(BIN_PATH)/l4v2/tftp --l4io --server=192.168.0.2 module $(BIN_PATH)/l4v2/loader $(ND)/cfg/l4linux.conf vbeset 0x117
And here is the Loader config script for loading L4Linux assuming, that L4Linux starts in a RAM disk and is configured to use l4io
(omega0 protocol) for requesting IRQs:
# cfg/l4linux.conf verbose 0 modpath "(nd)/tftpboot/drops/bin/l4v2" task "vmlinuz26" "mem=64M load_ramdisk=1 ramdisk_size=16384 root=/dev/ram l4env_rd=(nd)/tftpboot/drops/rd/drops-rd.rd" all_sects_writable
L4Linux has to be compiled with the L4Linux option "Frame buffer driver for l4con and DOpE" (CONFIG_L4_FB_DRIVER=y).
The default file provider the loader communicates with is tftp. This server accepts filenames in the GRUB syntax. Therefore you must prepend "(nd)/"
. The binary must be accessible by the TFTP protocol (e.g. the binaries must be world-readable).