Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/distrib/common/list.zfsroot

36 lines
718 B
Plaintext
Raw Normal View History

zfs: Allow modules to be loaded once in the ZFS chroot Rather than copying the needed modules from FFS to the ramdisk, load then directly from FFS instead. This way, we can symlink ramdisk stand into /altroot and let nature take it's course like loading firmware. Set shell exit on error rather than using chained commands. zpool import seems to SIGBUS randomly on amd64 and if we didn't do the former then zpool would hang the init. Now at least we exit to the shell.
2020-02-23 08:15:54 +03:00
# $NetBSD: list.zfsroot,v 1.2 2020/02/23 05:15:54 roy Exp $
zfs: build a ramdisk on amd64 with enough to mount rpool/ROOT on / Until we get ZFS integrated into our boot loader, this is the next best thing. The idea is simple - have a small FFS partition with a kernel, modules and this ramdisk. Once the ramdisk boots it will mount the FFS partition read only, copy the needed ZFS modules to the ramdisk and then unmount the partition. Then we import the ZFS root pool, mount the ZFS root filesystem and then pivot to it. Because the initial FFS partition is not mounted at this point, we can mount it in /altroot so we can replace the kernel and modules with newer ones so it's easily maintainable. This ZFS boot strapper currently makes the following assumptions: * The device NAME=boot is the FFS with kernel, modules and this ramdisk. * The ZFS root pool and root filesystem are called rpool/ROOT. A boot.cfg menu entry can then be added like so: menu=Boot ZFS root:fs /ramdisk-zfsroot.fs;boot
2020-02-22 12:53:47 +03:00
#
# list file (c.f. parselist.awk) for ZFS on root.
#
SRCDIRS external/cddl/osnet/sbin
PROG sbin/zfs
PROG sbin/zpool
LINK sbin/zfs sbin/mount_zfs
ARGVLN zfs mount_zfs
# We need sysctl to set init.root=/altroot
PROG sbin/sysctl
zfs: Allow modules to be loaded once in the ZFS chroot Rather than copying the needed modules from FFS to the ramdisk, load then directly from FFS instead. This way, we can symlink ramdisk stand into /altroot and let nature take it's course like loading firmware. Set shell exit on error rather than using chained commands. zpool import seems to SIGBUS randomly on amd64 and if we didn't do the former then zpool would hang the init. Now at least we exit to the shell.
2020-02-23 08:15:54 +03:00
# We need modload as we cannot build CDDL modules in the kernel
PROG sbin/modload
PROG sbin/modunload
PROG sbin/modstat
zfs: build a ramdisk on amd64 with enough to mount rpool/ROOT on / Until we get ZFS integrated into our boot loader, this is the next best thing. The idea is simple - have a small FFS partition with a kernel, modules and this ramdisk. Once the ramdisk boots it will mount the FFS partition read only, copy the needed ZFS modules to the ramdisk and then unmount the partition. Then we import the ZFS root pool, mount the ZFS root filesystem and then pivot to it. Because the initial FFS partition is not mounted at this point, we can mount it in /altroot so we can replace the kernel and modules with newer ones so it's easily maintainable. This ZFS boot strapper currently makes the following assumptions: * The device NAME=boot is the FFS with kernel, modules and this ramdisk. * The ZFS root pool and root filesystem are called rpool/ROOT. A boot.cfg menu entry can then be added like so: menu=Boot ZFS root:fs /ramdisk-zfsroot.fs;boot
2020-02-22 12:53:47 +03:00
LIBS -lnvpair
LIBS -luutil
LIBS -lzfs
LIBS -lavl
LIBS -lm
LIBS -lpthread
LIBS -lumem
#LIBS -lutil # replaced by libhack
LIBS -lz
LIBS -lzfs_core
COPY ${NETBSDSRCDIR}/distrib/common/zfsroot.rc etc/rc
zfs: Allow modules to be loaded once in the ZFS chroot Rather than copying the needed modules from FFS to the ramdisk, load then directly from FFS instead. This way, we can symlink ramdisk stand into /altroot and let nature take it's course like loading firmware. Set shell exit on error rather than using chained commands. zpool import seems to SIGBUS randomly on amd64 and if we didn't do the former then zpool would hang the init. Now at least we exit to the shell.
2020-02-23 08:15:54 +03:00
# Make modules and firmware images available
SYMLINK altroot/stand stand
zfs: build a ramdisk on amd64 with enough to mount rpool/ROOT on / Until we get ZFS integrated into our boot loader, this is the next best thing. The idea is simple - have a small FFS partition with a kernel, modules and this ramdisk. Once the ramdisk boots it will mount the FFS partition read only, copy the needed ZFS modules to the ramdisk and then unmount the partition. Then we import the ZFS root pool, mount the ZFS root filesystem and then pivot to it. Because the initial FFS partition is not mounted at this point, we can mount it in /altroot so we can replace the kernel and modules with newer ones so it's easily maintainable. This ZFS boot strapper currently makes the following assumptions: * The device NAME=boot is the FFS with kernel, modules and this ramdisk. * The ZFS root pool and root filesystem are called rpool/ROOT. A boot.cfg menu entry can then be added like so: menu=Boot ZFS root:fs /ramdisk-zfsroot.fs;boot
2020-02-22 12:53:47 +03:00
SYMLINK altroot/libdata libdata