On Sat, Oct 26, 2013 at 09:15:36AM -0500, Adam Thompson wrote: > On 13-10-25 01:29 PM, Ted Unangst wrote: > >With crypto softraid: installboot copies /boot into a reserved > >area at the beginning of the softraid partition. In this case, the > >/boot file isn't used during booting. Then it copies biosboot into > >place, with the block array filled in with the locations of the > >copy of /boot. /boot will ask for your passphrase and decrypt the > >disk before loading /bsd. The usual trick for dual booting is to > >jump to or copy the PBR somewhere. That doesn't change with > >crypto. > > Does it also function that way with RAID 1 softraid volumes?
Yes. > It would be nice to load the kernel directly off the root filesystem > instead of having two auxiliary filesystems just to hold the kernel. The kernel (/bsd) is always loaded from the root filesystem by /boot. But /boot itself is loaded from the softraid meta data area instead of the root filesystem, if installboot was run on a softraid volume. > (And, if it does work this way with RAID 1, when did that start happening?) In 2011 as per log of /usr/src/sys/arch/i386/stand/installboot/installboot.c. ---------------------------- revision 1.56 date: 2011/01/23 14:57:08; author: jsing; state: Exp; lines: +258 -34; Add support to installboot(8) for installing biosboot(8) and boot(8) on softraid volumes. If installboot is run on a softraid volume, a fake single inode FFS filesystem is constructed to contain boot(8). This is then installed onto the softraid volume via the BIOCINSTALLBOOT ioctl. biosboot(8) is then patched and installed onto each disk that is a member of the softraid volume. Joint work with otto@ who came up with the concept of constructing a fake FFS filesystem and wrote the code to do so. No objection from miod@ ----------------------------
