<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in mtree.zfsroot</title>
    <link>http://nxr.netbsd.org/rss/src/distrib/common/mtree.zfsroot</link>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2005</copyright>
    <generator>Java</generator>
    
<item>
    <title>branches:  1.3.4;<br/>ramdisk-zfsroot: We no longer need to have /etc/zfs in mtree<br/><br/>Now that mountall doesn't rely on /etc/zfs/zpool.cache being present.</title>
    <description>/src/distrib/common/mtree.zfsroot - 1.3</description>
    <pubDate>Sun Feb 23 10:51:12 UTC 2020</pubDate>
    <dc:creator>roy</dc:creator>
</item>

<item>
    <title>zfs: Allow modules to be loaded once in the ZFS chroot<br/><br/>Rather than copying the needed modules from FFS to the ramdisk,<br/>load then directly from FFS instead.<br/><br/>This way, we can symlink ramdisk stand into /altroot and let nature take<br/>it's course like loading firmware.<br/><br/>Set shell exit on error rather than using chained commands.<br/>zpool import seems to SIGBUS randomly on amd64 and if we didn't do the<br/>former then zpool would hang the init. Now at least we exit to the shell.</title>
    <description>/src/distrib/common/mtree.zfsroot - 1.2</description>
    <pubDate>Sun Feb 23 05:15:54 UTC 2020</pubDate>
    <dc:creator>roy</dc:creator>
</item>

<item>
    <title>zfs: build a ramdisk on amd64 with enough to mount rpool/ROOT on /<br/><br/>Until we get ZFS integrated into our boot loader, this is the next best<br/>thing. The idea is simple - have a small FFS partition with a kernel,<br/>modules and this ramdisk. Once the ramdisk boots it will mount the FFS<br/>partition read only, copy the needed ZFS modules to the ramdisk and then<br/>unmount the partition. Then we import the ZFS root pool, mount the<br/>ZFS root filesystem and then pivot to it.<br/><br/>Because the initial FFS partition is not mounted at this point, we<br/>can mount it in /altroot so we can replace the kernel and modules with<br/>newer ones so it's easily maintainable.<br/><br/>This ZFS boot strapper currently makes the following assumptions:<br/> * The device NAME=boot is the FFS with kernel, modules and this ramdisk.<br/> * The ZFS root pool and root filesystem are called rpool/ROOT.<br/><br/>A boot.cfg menu entry can then be added like so:<br/>menu=Boot ZFS root:fs /ramdisk-zfsroot.fs;boot</title>
    <description>/src/distrib/common/mtree.zfsroot - 1.1</description>
    <pubDate>Sat Feb 22 09:53:47 UTC 2020</pubDate>
    <dc:creator>roy</dc:creator>
</item>

<item>
    <title>Merge changes from current as of 20200406</title>
    <description>/src/distrib/common/mtree.zfsroot - 1.3.4.2</description>
    <pubDate>Wed Apr 08 14:03:44 UTC 2020</pubDate>
    <dc:creator>martin</dc:creator>
</item>

<item>
    <title>file mtree.zfsroot was added on branch phil-wifi on 2020-04-08 14:03:44 +0000</title>
    <description>/src/distrib/common/mtree.zfsroot - 1.3.4.1</description>
    <pubDate>Sun Feb 23 10:51:12 UTC 2020</pubDate>
    <dc:creator>martin</dc:creator>
</item>
</channel></rss>

