summaryrefslogtreecommitdiffstats
path: root/sys/compat/linux/linux_socket.c
diff options
context:
space:
mode:
authorjsing <jsing@openbsd.org>2011-09-19 21:47:37 +0000
committerjsing <jsing@openbsd.org>2011-09-19 21:47:37 +0000
commit9a8b7afecec7e1ab0c7f48921d5a3704a3a0daff (patch)
tree5ba5fd4ec81db59ab387267136f62aa479e197a0 /sys/compat/linux/linux_socket.c
parentWhen installboot is run on a softraid volume, add boot optional metadata (diff)
downloadwireguard-openbsd-9a8b7afecec7e1ab0c7f48921d5a3704a3a0daff.tar.xz
wireguard-openbsd-9a8b7afecec7e1ab0c7f48921d5a3704a3a0daff.zip
If the rootduid matches a softraid chunk of a bootable softraid volume,
map the rootduid to the DUID of the softraid volume. This means that regardless of where the kernel is loaded from we always get the softraid volume as the root device, providing we booted from one of its chunks. If we boot from any other disk then the rootduid remains unchanged. With this diff it is now possible to have the root filesystem on softraid, however at this stage the kernel still needs to be loaded from a separate FFS partition. ok deraadt@
Diffstat (limited to 'sys/compat/linux/linux_socket.c')
0 files changed, 0 insertions, 0 deletions