On Sun, Dec 17, 2017 at 8:52 PM, Warner Losh wrote:
> Greetings
>
> If you are booting off UEFI and have a bit of an unusual setup, I'd like
> you to drop me a line.
>
> The setup that I'm looking for is any case where you load boot1.efi off one
> drive (cd, ssd, hdd, nvme,
[Just adding notes about what ubldr.bin does
with and without loaderdev being specified
(correctly). Overall it does not appear to
me that the ubldr.bin based contexts can
fully avoid the "systems with multiple
partitions that might be right" issue.]
On 2017-Dec-20, at 2:47 AM, Mark Millard
On 2017-Dec-19, at 9:10 PM, Warner Losh wrote:
> On Tue, Dec 19, 2017 at 9:06 PM, Mark Millard wrote:
> [The usdcard in my rpi2 example does not contain any kernel files,
> nor any dtb files. Only the USB SSD stick does. The kernel and dtb
> do not come from the usdcard. This is what I'm not
On Tue, Dec 19, 2017 at 9:06 PM, Mark Millard wrote:
> [The usdcard in my rpi2 example does not contain any kernel files,
> nor any dtb files. Only the USB SSD stick does. The kernel and dtb
> do not come from the usdcard. This is what I'm not sure if it is
> generally
[The usdcard in my rpi2 example does not contain any kernel files,
nor any dtb files. Only the USB SSD stick does. The kernel and dtb
do not come from the usdcard. This is what I'm not sure if it is
generally supported or not.]
On 2017-Dec-19, at 7:26 PM, Warner Losh wrote:
> On Dec 19, 2017
On Dec 19, 2017 4:26 PM, "Mark Millard" wrote:
On 2017-Dec-19, at 1:49 PM, Warner Losh wrote:
>
>
> On Dec 19, 2017 10:58 AM, "Mark Millard" wrote:
>> On 2017-Dec-18, at 2:37 PM, Warner Losh wrote:
>>
>> > . . .
>> >
>> > Or the following pseudo-code with all the weird
On Dec 19, 2017 3:38 PM, "Oliver Pinter"
wrote:
On Tuesday, December 19, 2017, Warner Losh wrote:
> On Dec 18, 2017 6:06 PM, "Rodney W. Grimes" <
> freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
>
> > On Mon, Dec 18, 2017 at 3:12 PM, Mark Millard
On 2017-Dec-19, at 1:49 PM, Warner Losh wrote:
>
>
> On Dec 19, 2017 10:58 AM, "Mark Millard" wrote:
>> On 2017-Dec-18, at 2:37 PM, Warner Losh wrote:
>>
>> > . . .
>> >
>> > Or the following pseudo-code with all the weird special cases removed for
>> > clarity
>> >
>> > load loader.efi
On 12/19/17 14:38, Oliver Pinter wrote:
On Tuesday, December 19, 2017, Warner Losh wrote:
[snip]
Or the following pseudo-code with all the weird special cases removed for
clarity
load loader.efi from ESP
if Boot uefi variable holds a second path, use that for
On Tuesday, December 19, 2017, Warner Losh wrote:
> On Dec 18, 2017 6:06 PM, "Rodney W. Grimes" <
> freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
>
> > On Mon, Dec 18, 2017 at 3:12 PM, Mark Millard
> wrote:
> >
> > > Warner Losh imp at bsdimp.com wrote on
> >
On Dec 19, 2017 12:26 PM, "Mark Millard" wrote:
[I forgot to list the .dtb file with the
kernel and world.]
On 2017-Dec-19, at 9:58 AM, Mark Millard wrote:
> On 2017-Dec-18, at 2:37 PM, Warner Losh wrote:
>
>> . . .
>>
>> Or the following pseudo-code with all the weird
On Dec 19, 2017 10:58 AM, "Mark Millard" wrote:
On 2017-Dec-18, at 2:37 PM, Warner Losh wrote:
> . . .
>
> Or the following pseudo-code with all the weird special cases removed for
clarity
>
> load loader.efi from ESP
> if Boot uefi variable holds a second path, use
On Dec 18, 2017 6:06 PM, "Rodney W. Grimes" <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> On Mon, Dec 18, 2017 at 3:12 PM, Mark Millard wrote:
>
> > Warner Losh imp at bsdimp.com wrote on
> > Mon Dec 18 20:29:45 UTC 2017 :
> >
> > > The specific thing we will stop doing is
[I forgot to list the .dtb file with the
kernel and world.]
On 2017-Dec-19, at 9:58 AM, Mark Millard wrote:
> On 2017-Dec-18, at 2:37 PM, Warner Losh wrote:
>
>> . . .
>>
>> Or the following pseudo-code with all the weird special cases removed for
>> clarity
>>
>> load loader.efi from ESP
On 2017-Dec-18, at 2:37 PM, Warner Losh wrote:
> . . .
>
> Or the following pseudo-code with all the weird special cases removed for
> clarity
>
> load loader.efi from ESP
> if Boot uefi variable holds a second path, use that for root/kernel
> otherwise if an override variable holds a
> On Mon, Dec 18, 2017 at 3:12 PM, Mark Millard wrote:
>
> > Warner Losh imp at bsdimp.com wrote on
> > Mon Dec 18 20:29:45 UTC 2017 :
> >
> > > The specific thing we will stop doing is that in the absence of
> > > instructions to the contrary, we will no longer search for
Warner Losh imp at bsdimp.com wrote on
Mon Dec 18 20:29:45 UTC 2017 :
> The specific thing we will stop doing is that in the absence of
> instructions to the contrary, we will no longer search for root on a device
> other than the one the loader.efi came from.
Warner Losh imp at bsdimp.com
On Mon, Dec 18, 2017 at 3:12 PM, Mark Millard wrote:
> Warner Losh imp at bsdimp.com wrote on
> Mon Dec 18 20:29:45 UTC 2017 :
>
> > The specific thing we will stop doing is that in the absence of
> > instructions to the contrary, we will no longer search for root on a
>
On Mon, Dec 18, 2017 at 1:21 PM, Maxim Sobolev wrote:
> Not really specific to UEFI, but when ZFS is in use the /boot might be
> partially or fully located on the drive that does not correspond to your
> boot drive. We've bumped into this issue on AWS recently when our
Not really specific to UEFI, but when ZFS is in use the /boot might be
partially or fully located on the drive that does not correspond to your
boot drive. We've bumped into this issue on AWS recently when our kernel
ended up on second drive after upgrade in a pool that were spanning two EBS
On 12/17/17 20:52, Warner Losh wrote:
Greetings
If you are booting off UEFI and have a bit of an unusual setup, I'd like
you to drop me a line.
The setup that I'm looking for is any case where you load boot1.efi off one
drive (cd, ssd, hdd, nvme, etc), but don't have a FreeBSD system on that
Greetings
If you are booting off UEFI and have a bit of an unusual setup, I'd like
you to drop me a line.
The setup that I'm looking for is any case where you load boot1.efi off one
drive (cd, ssd, hdd, nvme, etc), but don't have a FreeBSD system on that
drive, but on a different drive on the
22 matches
Mail list logo