src/sys/boot/common/boot.c, branch release/9.3.0 FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F9.3.0 2012-06-29T10:22:20Z MFC r235330: zfs boot: try to set vfs.root.mountfrom from currdev as a 2012-06-29T10:22:20Z Andriy Gapon avg@FreeBSD.org 2012-06-29T10:22:20Z urn:sha1:37ae306bd4b04cb6b0d28293d6f08d689e834393 fallback Introduce a new option (BOOT_PROMPT_123) that lets enter the boot prompt 2009-11-12T01:30:17Z Attilio Rao attilio@FreeBSD.org 2009-11-12T01:30:17Z urn:sha1:909feda120d5690e8273b6180fc00925e80cbccf only when typing the sequence "123" (opposite to the standard 'push any button' approach). That results useful when using serial lines sending garbage and leading to unwilling boot prompt appearence. Obtained from: Sandvine Incorporated Reviewed by: emaste, jhb Sponsored by: Sandvine Incorporated MFC: 1 week sys/boot/common.c 2009-06-01T01:02:30Z Craig Rodrigues rodrigc@FreeBSD.org 2009-06-01T01:02:30Z urn:sha1:0c349f0856fb3fa3e73f67639e578f789e30145b ================= Extend the loader to parse the root file system mount options in /etc/fstab, and set a new loader variable vfs.root.mountfrom.options with these options. The root mount options must be a comma-delimited string, as specified in /etc/fstab. Only set the vfs.root.mountfrom.options variable if it has not been set in the environment. sys/kern/vfs_mount.c ==================== When mounting the root file system, pass the mount options specified in vfs.root.mountfrom.options, but filter out "rw" and "noro", since the initial mount of the root file system must be done as "ro". While we are here, try to add a few hints to the mountroot prompt to give users and idea what might of gone wrong during mounting of the root file system. Reviewed by: jhb (an earlier patch) Extend `autoboot_delay' handling - is this variable is set to -1 don't allow 2005-05-19T23:03:02Z Maxim Sobolev sobomax@FreeBSD.org 2005-05-19T23:03:02Z urn:sha1:4d87b291ad993a6d5bd6bef337fdff61d9b336be user to interrupt autoboot process at all. Currently, even when `autoboot_delay' is set to 0, loader(8) still allows autoboot process to be interrupted by pressing any key on the console when the loader reads kernel and modules from the disk. In some cases (i.e. untrusted environment) such behaviour is highly indesirable and user should not be allowed to interfere with the autoboot process at all. Sponsored by: PBXpress Inc. MFC after: 3 days Whitespace only: kill trailing spaces. 2005-05-19T05:15:08Z Maxim Sobolev sobomax@FreeBSD.org 2005-05-19T05:15:08Z urn:sha1:faf0d4eb71b00aad55a26a845d5e630d404dba8f Use __FBSDID(). 2003-08-25T23:30:41Z David E. O'Brien obrien@FreeBSD.org 2003-08-25T23:30:41Z urn:sha1:1809be3cd462d071c04e67a2648af4ed71925153 Also some minor style cleanups. Implement the long-awaited module->file cache database. A userland 2001-09-11T01:09:24Z Peter Wemm peter@FreeBSD.org 2001-09-11T01:09:24Z urn:sha1:505222d35fea6a81779095049a6e87ddb6d78db4 tool (kldxref(8)) keeps a cache of what modules and versions are inside what .ko files. I have tested this on both Alpha and i386. Submitted by: bp The default kernel filename is "kernel" again, not "kernel.ko". 2000-11-17T04:43:56Z Mike Smith msmith@FreeBSD.org 2000-11-17T04:43:56Z urn:sha1:1d6dc229163bea8ef8cc51eecb5f2b8083167c4a Submitted by: mckusick Don't indirect through a null pointer if we run out of kernel filenames. 2000-10-25T23:28:19Z Doug Rabson dfr@FreeBSD.org 2000-10-25T23:28:19Z urn:sha1:bcdb85b6b808d283a62c1e7ea9e6aa2042666a13 Start countdown only _after_ the kernel was loaded. Not very fair otherwise. 2000-09-15T07:54:10Z Daniel C. Sobral dcs@FreeBSD.org 2000-09-15T07:54:10Z urn:sha1:9f0c5de5f72926123427c93a6c852eb47577b2d8