Hi, has anyone encountered the issue?
I literally used the same hotspot for sysupgrade from 7.4, that went nicely,
however after rebooting into 7.5 the PowerBook cannot see it anymore.
Wifi itself works: at least, ifconfig bwi0 scan shows other Wifi networks, but
not the iPhone one.
At the same
I used sysupgrade earlier today and it seems I was still getting
the old ld.so, but as of 30 minutes ago or so, snapshots are working
fine, on macppc.
I was looking forward to spend the day testing stuff in the kernel
so this is great
Thanks everyone.
> From: "Theo de Raadt"
> Date: Sun, 07 Apr 2024 14:00:57 -0600
>
> I am surprised that two of you have managed to mix parts from
> -current and 7.5.
>
> Can you two figure out how you did this?
The first snapshots after 7.5 still shipped an ld.so that called
msyscall(2). The diff to remove
jon@elytron.openbsd.amsterdam wrote:
> It's probably a thing with sysupgrade as you mention deraadt@, I
> did
>
> sysupgrade -nkfs https://cdn.openbsd.org/pub/OpenBSD
>
> Along with a freshly 'cvs update'd kernel tree.
>
> I always follow snapshots, and noticed that current macppc snapshots
>
It's probably a thing with sysupgrade as you mention deraadt@, I
did
sysupgrade -nkfs https://cdn.openbsd.org/pub/OpenBSD
Along with a freshly 'cvs update'd kernel tree.
I always follow snapshots, and noticed that current macppc snapshots
are fairly recent so I thought it'd be alright, but
I am surprised that two of you have managed to mix parts from -current and 7.5.
Can you two figure out how you did this?
Our development process has only very short compatibility windows; a recent
one was shorter than usual.
Thank you, understood.
(And apologies for the html. I'm struggling to get mobile Gmail to do
simple text.)
jon@elytron.openbsd.amsterdam wrote:
> I think the bad system call messages started a little after 7.5 was
> released, been getting them as well on macppc. Not sure why though,
> haven't digged into the recent commits
This is happening because you are mixing current and 7.5
There is an
I think the bad system call messages started a little after 7.5 was
released, been getting them as well on macppc. Not sure why though,
haven't digged into the recent commits
Eric Grosse wrote:
> On Sun, Apr 7, 2024, 11:43 Theo de Raadt wrote:
>
> > My usual workaround is to download the latest src tree, then sysupgrade,
> then
>
> I doubt your sysupgrade worked.
>
> It would explain why you had further trouble.
>
> I'm sure you're right and it is my error.
On Sun, Apr 7, 2024, 11:43 Theo de Raadt wrote:
> > My usual workaround is to download the latest src tree, then sysupgrade,
> then
>
> I doubt your sysupgrade worked.
>
> It would explain why you had further trouble.
I'm sure you're right and it is my error. But FWIW, the sysupgrade reported
> My usual workaround is to download the latest src tree, then sysupgrade, then
I doubt your sysupgrade worked.
It would explain why you had further trouble.
Many thanks, as always, to the folks behind 7.5 upgrading smoothly on my
two TalosII power9 machines, one of which is the test build machine for the
Go team's openbsd-ppc64.
As a security move, I put PCI Intel network cards in my machines because
the (presumed vulnerable) BMC is accessible from
13 matches
Mail list logo
