On 28/01/2016 16:22, Doug Rabson wrote: > On 28 January 2016 at 15:03, Tomoaki AOKI <junchoon_at_dec.sakura.ne.jp> wrote: > >> It's exactly the NO GOOD point. The disk where boot1 is read from >> should be where loader.efi and loader.conf are first read. >> > I just wanted to note that gptzfsboot and zfsboot behaves this way. Boot1 > looks for loader in the pool which contains the disk that the BIOS booted. > It passes through the ID of that pool to loader which uses that pool as the > default for loading kernel and modules. I believe this is the correct > behaviour. For gptzfsboot and zfsboot, it is possible to override by > pressing space at the point where it is about to load loader. I believe I understand at least some of your issue now, could you please test the code on the following review to see if it fixes your issue please: https://reviews.freebsd.org/D5108 Regards SteveReceived on Fri Jan 29 2016 - 01:58:13 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:02 UTC