Date: Sun, 6 Mar 2022 14:11:28 -0700 From: Warner Losh <imp@bsdimp.com> To: "Eugene M. Zheganin" <eugene@zhegan.in> Cc: FreeBSD Stable ML <stable@freebsd.org> Subject: Re: custom install and missing kenv defaults Message-ID: <CANCZdfo_dv6E1ZHQk2t5EmCUBuNJbvC46YBEkVHRDu%2B7Tnma9Q@mail.gmail.com> In-Reply-To: <f956d9c7-ec15-7812-8717-665b67f73291@zhegan.in> References: <f956d9c7-ec15-7812-8717-665b67f73291@zhegan.in>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000966a3b05d99331ec Content-Type: text/plain; charset="UTF-8" On Sun, Mar 6, 2022 at 1:17 PM Eugene M. Zheganin <eugene@zhegan.in> wrote: > Hello, > > I'm using custom install script for setting up FreeBSD on large disks > (you know, that 10-years-ago-and-still-there issue with "cannnot read > MOS, all block copies unavailable" when book blocks migrate over 2TB), > but I was using it only on legacy gptzfsboot servers, Nowadays I > converted it to UEFI, and now I can see that this installation cannot > boot atomatically, because it searches for the kernel in /boot. I know > about loader.conf, for sure, but servers installed with bsdinstall don't > have kernel_path set there (along with module_path), yet it works fine. > I've also checked the kernel for the bundled env variables - none. > > So, my question is - where are the kernel_path and module path set when > the bsdinstall does the installation ? > They aren't. They default to the path that the boot loader reports to the kernel. /boot/loader.conf can, I believe, override them. Warner --000000000000966a3b05d99331ec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Sun, Mar 6, 2022 at 1:17 PM Eugene= M. Zheganin <<a href=3D"mailto:eugene@zhegan.in">eugene@zhegan.in</a>&g= t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p= x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,= <br> <br> I'm using custom install script for setting up FreeBSD on large disks <= br> (you know, that 10-years-ago-and-still-there issue with "cannnot read = <br> MOS, all block copies unavailable" when book blocks migrate over 2TB),= <br> but I was using it only on legacy gptzfsboot servers, Nowadays I <br> converted it to UEFI, and now I can see that this installation cannot <br> boot atomatically, because it searches for the kernel in /boot. I know <br> about loader.conf, for sure, but servers installed with bsdinstall don'= t <br> have kernel_path set there (along with module_path), yet it works fine. <br= > I've also checked the kernel for the bundled env variables - none.<br> <br> So, my question is - where are the kernel_path and module path set when <br= > the bsdinstall does the installation ?<br></blockquote><div><br></div><div>= They aren't. They default to the path that the boot loader reports to t= he kernel.</div><div>/boot/loader.conf can, I believe, override them.</div>= <div><br></div><div>Warner=C2=A0</div></div></div> --000000000000966a3b05d99331ec--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfo_dv6E1ZHQk2t5EmCUBuNJbvC46YBEkVHRDu%2B7Tnma9Q>