Date: Tue, 22 Oct 2019 14:33:53 +0700 From: Victor Sudakov <vas@sibptus.ru> To: freebsd-questions@freebsd.org Subject: boot1.efi and ZFS Message-ID: <20191022073353.GA67692@admin.sibptus.ru> In-Reply-To: <c19769d3-d1f8-0158-9cfe-49a2100a66b1@ShaneWare.Biz> References: <9fdcf15e-2f83-1cfd-1e04-cc08943485fa@networktest.com> <c19769d3-d1f8-0158-9cfe-49a2100a66b1@ShaneWare.Biz>
next in thread | previous in thread | raw e-mail | index | archive | help
--jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Dear Colleagues, Out of curiousity. UEFI(8) says that=20 "boot1.efi searches partitions of type freebsd-ufs and freebsd-zfs for loader.efi. The search begins with partitions on the device from which boot1.efi was loaded, and continues with other available partitions. If both freebsd-ufs and freebsd-zfs partitions exist on the same device the freebsd-zfs partition is preferred. boot1.efi then loads and executes loader.efi." This means that boot1.efi (with binary size 80k) includes a ZFS filesystem driver (even if just readonly)? Really, a ZFS implementation can be so small in size? Is _all_ the ZFS access code really in /src/stand/efi/boot1/zfs_module.c ?= =20 --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --jI8keyz6grp/JLjh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJdrrDhAAoJEA2k8lmbXsY0wg4H/2ewpgTgT2eLklv/Xmk9+gjs j1wPHrTuKV7jr9YFdsKFDMkmjSxAmZdWo9qTuO6sZDMoSo1lvmwKzxBs49bc8GNg 7tDCJ9ywMHofA3S64yVcV2YoSHqb900pqZFCsgBWm25b7N4Tz/rWF5qAybPBJBoK mkeZkaTB8vRkKAcOE/Nwn8QVhvBWpeXkungzvsSxZzTbmXRDbGmQQPGUgjfAYpOG +cg/iTKF+zyaX23cAnw1Lq6Dd942OwPzmkzK/jNLPAazsD85cePD+JLoxcqRI5aG r9FVi16MERKfEH4MeYAj7ljm3taYCkOueG1LaInVZSuTYqYGMDs8TJiMwmHjF8k= =Hxys -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191022073353.GA67692>