summaryrefslogtreecommitdiffstats
path: root/sys/kern/vfs_mountroot.c
Commit message (Collapse)AuthorAgeFilesLines
* Make RB_CDROM work. This should probably check for a disc in cd1 and acd1nwhitehorn2011-01-081-2/+2
| | | | as well.
* Add support for asterisk characters when filling in the GELI passworded2010-11-141-1/+1
| | | | | | | | | | | during boot. Change the last argument of gets() to indicate a visibility flag and add definitions for the numerical constants. Except for the value 2, gets() will behave exactly the same, so existing consumers shouldn't break. We only use it in two places, though. Submitted by: lme (older version)
* ZFS pool name is not a real device in devfs. Do not wait forae2010-10-191-1/+2
| | | | | | | device appear when mounting root from ZFS. Reviewed by: marcel Approved by: mav (mentor)
* Re-implement the root mount logic using a recursive approach, whereby eachmarcel2010-10-181-326/+738
| | | | | | | | | | | | | | | | | | | | | root file system (starting with devfs and a synthesized configuration) can contain directives for mounting another file system as root. The old root file system is re-mounted under the new root file system (with /.mount or /mnt as the mount point) to allow access to the underlying file system. The configuration allows for creating vnode-backed memory disks that can subsequently be mounted as root. This allows for an efficient and low- cost way to distribute and boot FreeBSD software images that reside on some storage media. When trying a mount, the kernel will wait for the device in question to arrive. The timeout is configurable and is part of the configuration. This allows arbitrarily complex GEOM configurations to be constructed on the fly. A side-effect of this change is that all root specifications, whether compiled into the kernel or typed at the prompt can contain root mount options.
* Split the root mount logic from the (generic) mount code and movemarcel2010-10-021-0/+626
it (the root mount code) into a new file called vfs_mountroot.c The split is almost trivial, as the code is almost perfectly non-intertwined. The only adjustment needed was to move the UMA zone allocation out of vfs_mountroot() [in vfs_mountroot.c] and into vfs_mount.c, where it had to be done as a SYSINIT [see vfs_mount_init()]. There are no functional changes with this commit.
OpenPOWER on IntegriCloud