On 2020-Jul-13, at 13:18, Mark Millard wrote:
> [Just a correction to a side comment.]
>
> On 2020-Jul-13, at 12:46, Mark Millard wrote:
>
>> On 2020-Jul-13, at 12:03, John-Mark Gurney wrote:
>>
>>> Mark Millard wrote this message on Mon, Jul 13, 2020 at 00:44 -0700:
On 2020-Jul-12, at
On 2020-Jul-16, at 23:15, Mark Millard wrote:
> [Trying again: I missed removing a type of character (escape)
> beyond the [?25h removals. My choice of editor was not the
> best for the context and it was not obvious that the
> escapes were present.]
>
> I'll mostly just send the text that has
I've reproduced this on the latest snapshot build of stable/12 and
created a PR here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248046
On 7/16/20 6:26 PM, Daniel Dettlaff wrote:
On 17.07.2020, at 00:16, Daniel Dettlaff wrote:
Hello, I heard it's known?
I built recent system from stab
Hello
I would like to know if by chance in freeBSD there is some kind of log
when the command freebsd-update fetch / install is executed?
I looked in the documentation and found nothing about it.
Does anyone know if this exists?
___
freebsd-current@freeb
[Trying again: I missed removing a type of character (escape)
beyond the [?25h removals. My choice of editor was not the
best for the context and it was not obvious that the
escapes were present.]
I'll mostly just send the text that has the
additional removals. The boot text with the error
message
Note: The media involved (microsd card and USB SSD) is also
configured to boot a RPi3B and that is still working when
plugged into the RPi3B. This should have the implication
that EFI/BOOT/bootaa64.efi is okay for how the RPi3B ends
up using it, for example.
The failed boot attempts look like the
