On Sun, Mar 05, 2023 at 03:01:02PM -, Michael van Elst wrote:
>
> - if (guid != NULL && len == 16)
> + if (guid == NULL || len == 16)
> +
Shouldn't that be "len != 16"?
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No
On Sun, 5 Mar 2023 at 22:03, Michael van Elst wrote:
>
> On Sun, Mar 05, 2023 at 10:56:31PM +0100, Michael van Elst wrote:
> > On Mon, Mar 06, 2023 at 07:44:20AM +1030, Brett Lymn wrote:
> > > On Sun, Mar 05, 2023 at 03:01:02PM -, Michael van Elst wrote:
> > > >
> > > > - if (guid !=
On Sun, Mar 05, 2023 at 10:56:31PM +0100, Michael van Elst wrote:
> On Mon, Mar 06, 2023 at 07:44:20AM +1030, Brett Lymn wrote:
> > On Sun, Mar 05, 2023 at 03:01:02PM -, Michael van Elst wrote:
> > >
> > > - if (guid != NULL && len == 16)
> > > + if (guid == NULL || len ==
On Mon, Mar 06, 2023 at 07:44:20AM +1030, Brett Lymn wrote:
> On Sun, Mar 05, 2023 at 03:01:02PM -, Michael van Elst wrote:
> >
> > - if (guid != NULL && len == 16)
> > + if (guid == NULL || len == 16)
> > +
>
> Shouldn't that be "len != 16"?
Yes, and another error. The
On Sun, 5 Mar 2023 at 15:01, Michael van Elst wrote:
>
> mlel...@serpens.de (Michael van Elst) writes:
>
> >On Sun, Mar 05, 2023 at 12:56:29PM +, Chavdar Ivanov wrote:
> >[ 1.3797015] dk0 at sd0: "EFI system", 262144 blocks at 2048, type:
> >msdos
> >[ 1.3897890] dk1 at sd0:
mlel...@serpens.de (Michael van Elst) writes:
>On Sun, Mar 05, 2023 at 12:56:29PM +, Chavdar Ivanov wrote:
>[ 1.3797015] dk0 at sd0: "EFI system", 262144 blocks at 2048, type:
>msdos
>[ 1.3897890] dk1 at sd0: "cc8f4a89-edc0-48d1-b9ce-b40d227a4a07",
>> netbsd,gpt-guid 894a8fcc
On Sun, Mar 05, 2023 at 12:56:29PM +, Chavdar Ivanov wrote:
[ 1.3797015] dk0 at sd0: "EFI system", 262144 blocks at 2048, type:
msdos
[ 1.3897890] dk1 at sd0: "cc8f4a89-edc0-48d1-b9ce-b40d227a4a07",
> netbsd,gpt-guid 894a8fcc c0edd148 b9ceb40d 227a4a07 .J.H"zJ.
Means,
On Sun, 5 Mar 2023 at 12:24, matthew green wrote:
>
> Chavdar Ivanov writes:
> > On Sat, 4 Mar 2023 at 23:30, Michael van Elst wrote:
> > >
> > > ci4...@gmail.com (Chavdar Ivanov) writes:
> > >
> > > >Since my last aarch64 build yesterday, 03/03/2023, my machine no
> > > >longer boots
Chavdar Ivanov writes:
> On Sat, 4 Mar 2023 at 23:30, Michael van Elst wrote:
> >
> > ci4...@gmail.com (Chavdar Ivanov) writes:
> >
> > >Since my last aarch64 build yesterday, 03/03/2023, my machine no
> > >longer boots automatically,
> >
> > sys/arch/evbarm/fdt/fdt_machdep.c 1.100
> >
> >
On Sat, 4 Mar 2023 at 23:30, Michael van Elst wrote:
>
> ci4...@gmail.com (Chavdar Ivanov) writes:
>
> >Since my last aarch64 build yesterday, 03/03/2023, my machine no
> >longer boots automatically,
>
> sys/arch/evbarm/fdt/fdt_machdep.c 1.100
>
> changed how the boot disk is determined.
ci4...@gmail.com (Chavdar Ivanov) writes:
>Since my last aarch64 build yesterday, 03/03/2023, my machine no
>longer boots automatically,
sys/arch/evbarm/fdt/fdt_machdep.c 1.100
changed how the boot disk is determined. Apparently it now fails for you.
On Sat, Mar 04, 2023 at 01:31:58PM +, Chavdar Ivanov wrote:
> So the kernel that boots OK says that the boot device is unknown,
> whereas the new one incorrectly identifies sd0 as the boot device - it
> should be dk1, or whatever the NAME is (the fstab has NAME=...
> identifying dk1).
I am
Hi,
I may have mentioned in some earlier mail to the list that I am
running a (free) instance on Oracle OCI of aarch64 NetBSD-current
machine. As there is no foreign OS support for the free instances
there, following a suggestion elsewhere on this list, I was able to
overwrite the boot disk of a
13 matches
Mail list logo
