Date: Sat, 17 Apr 2010 13:11:58 -0700 From: "Jason C. Wells" <jcw@speakeasy.net> To: Dan Naumov <dan.naumov@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: boot loader too large Message-ID: <4BCA160E.5090703@speakeasy.net> In-Reply-To: <j2hcf9b1ee01004170830tc6dfe066h5ec96d337bff6c75@mail.gmail.com> References: <j2hcf9b1ee01004170830tc6dfe066h5ec96d337bff6c75@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dan Naumov wrote: > Hey > > A 64kb freebsd-boot partition should be more than plenty for what you > want to do, see my setup at: http://freebsd.pastebin.com/QS6MnNKc > Interesting. I read somewhere that the boot partition should not be too large as the entire partition is loaded into memory. I re-partitioned my drive to create a 64KiB freebsd-boot partition and I no longer get the error. It would appear that there is an undocumented maximum size to the freebsd-boot partition. In my case, a 1MiB boot partition was too large. Now I need to teach gptboot in ad4p1 how to find my root partition in ad4p4 without manual intervention. Is there a GPT equivalent to boot0cfg? gptboot currently attempts to boot: 0:ad(0p2)/boot/kernel/kernel I'd like it to boot: 0:ad(4p4)/boot/loader How does the boot process discover the partition in which the gptboot loader resides? And GPT is pretty damn slick. Nice work FreeBSD hackers. Thanks, Jason C. Wells
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BCA160E.5090703>