freebsd-dev/sys/boot/userboot
Marcel Moolenaar 7fe0b4f160 Give loaders more control over the Forth initialization process. In
particular, allow loaders to define the name of the RC script the
interpreter needs to use. Use this new-found control to have the
PXE loader (when compiled with TFTP support and not NFS support)
read from ${bootfile}.4th, where ${bootfile} is the name of the
file fetched by the PXE firmware.

The normal startup process involves reading the following files:
1.  /boot/boot.4th
2.  /boot/loader.rc or alternatively /boot/boot.conf

When these come from a FreeBSD-defined file system, this is all
good. But when we boot over the network, subdirectories and fixed
file names are often painful to administrators and there's really
no way for them to change the behaviour of the loader.

Obtained from:	Juniper Networks, Inc.
2014-07-27 16:12:51 +00:00
..
ficl For libstand and sys/boot, split off gcc-only flags into CFLAGS.gcc. 2013-12-26 11:32:39 +00:00
libstand Remove ia64. 2014-07-07 00:27:09 +00:00
test copyin/copyout should return 0 if they are truly emulating copyin/copyout behavior. 2014-07-22 04:47:19 +00:00
userboot Give loaders more control over the Forth initialization process. In 2014-07-27 16:12:51 +00:00
zfs ZFS boot support for bhyveload. 2014-02-22 07:18:06 +00:00
Makefile ZFS boot support for bhyveload. 2014-02-22 07:18:06 +00:00
userboot.h Add a callback function to userboot.so to fetch a list of environment 2012-11-12 22:38:54 +00:00