What about giving sysupgrade the same verbosity options as fw_update? This
would mean -v and -vv I sysupgrade would pass through the same options to
fw_update.
And for the installer, maybe another question: “Verbose download & install
progress?” Or no, as default.
On Sun, Aug 13, 2023, at
Hi,
Testing sec(4) between 2 end points with iperf3, iked has lost the associated
iface for the sec(4) point to point link. Specifically:
pfkey_sa: unsupported interface
Here is the surround log for the event:
Aug 14 11:30:54 terminator iked[93171]: spi=0x635987a83a22a13e: recv
I think that changing the behavior of the existing API in a way that
gratuitously increases the differences between BSDs is unwise. IMHO, we
should follow NetBSD on this and add kqueue1(), that being obviously
consistent with the previous 'add flags argument' extensions: pipe2(),
dup3(), and
Stuart Henderson wrote:
> On 2023/08/13 11:44, Andrew Hewus Fresh wrote:
> > My laptop doesn't have the fastest wifi and sysupgrade already uses a
> > progress bar to show what it's doing, so I'd really like to provide more
> > feedback on what it is doing:
>
> Does a single -v give enough
> CC'ed back the mailing list.
Oops, I thought I had replied to the list as well, my bad.
> Tested your patch. It works on my Chromebook.
Excellent. It's in!
Thanks,
Miod
On 2023/08/13 11:44, Andrew Hewus Fresh wrote:
> My laptop doesn't have the fastest wifi and sysupgrade already uses a
> progress bar to show what it's doing, so I'd really like to provide more
> feedback on what it is doing:
Does a single -v give enough feedback? It's a fair bit quieter (it
On 2023/08/13 16:10, Andrew Cagney wrote:
> On Sun, 13 Aug 2023 at 11:38, Tobias Heider wrote:
> >
> > On Sun, Aug 13, 2023 at 08:33:54AM -0400, Andrew Cagney wrote:
> > > > Hi Andrew,
> > > >
> > > > can you share the qemu cmd you are using in your tests?
> > > > I'd like to see if I can
On Sun, 13 Aug 2023 at 11:38, Tobias Heider wrote:
>
> On Sun, Aug 13, 2023 at 08:33:54AM -0400, Andrew Cagney wrote:
> > > Hi Andrew,
> > >
> > > can you share the qemu cmd you are using in your tests?
> > > I'd like to see if I can reproduce this.
> >
> > Here's pretty much everything. Thanks
Il Dom 13 Ago 2023, 21:17 Mikhail ha scritto:
This will be useful in the installer too, when I first installed OpenBSD
> with network connection I thought installation was stuck after
> "Multiprocessor machine; using bsd.mp instead of bsd.", only after
> some time I understood that the installer
On Sun, Aug 13, 2023 at 11:44:33AM -0700, Andrew Hewus Fresh wrote:
> My laptop doesn't have the fastest wifi and sysupgrade already uses a
> progress bar to show what it's doing, so I'd really like to provide more
> feedback on what it is doing:
>
> $ doas fw_update -d intel
> fw_update: deleted
This is the next patch in the clock interrupt reorganization series.
Before we continue breaking up the hardclock(9) we need to detour into
the MD code.
This patch divides the "initialization" parts of cpu_initclocks() from
the "start the clock interrupt" parts. Seprating the two parts leaves
My laptop doesn't have the fastest wifi and sysupgrade already uses a
progress bar to show what it's doing, so I'd really like to provide more
feedback on what it is doing:
$ doas fw_update -d intel
fw_update: deleted intel
$ time doas fw_update
fw_update: added intel; updated none; kept
CC'ed back the mailing list.
Tested your patch. It works on my Chromebook.
Le sam. 12 août 2023, 08:50, Miod Vallat a écrit :
> > > Have you checked that the Chromebook EC 8042 emulation returns
> 0xab/0x83
> > > to the 0xf2 command?
> > >
> > I've checked that it returns 0xab/0x83.
>
> Good!
>
On Sun, Aug 13, 2023 at 08:33:54AM -0400, Andrew Cagney wrote:
> > Hi Andrew,
> >
> > can you share the qemu cmd you are using in your tests?
> > I'd like to see if I can reproduce this.
>
> Here's pretty much everything. Thanks for looking at it.
Thank you, I managed to reproduce your crash.
I
On 2023/08/13 11:27:18 +0100, Jason McIntyre wrote:
> On Sun, Aug 13, 2023 at 11:21:39AM +0100, Stuart Henderson wrote:
> > On 2023/08/13 11:13, Omar Polo wrote:
> > > @@ -179,7 +179,8 @@ section starts with a declaration of the server
> > > Each
> > > .Ic server
> > > section starts with a
> Hi Andrew,
>
> can you share the qemu cmd you are using in your tests?
> I'd like to see if I can reproduce this.
Here's pretty much everything. Thanks for looking at it.
virt-install \
--connect=qemu:///system \
--check=path_in_use=off \
--graphics=none \
--virt-type=kvm \
--noreboot \
FreeBSD and NetBSD have variants of the kqueue(2) system call that
allow setting the close-on-exec flag on the returned file descriptor.
In general, I think it is good that the flag can be set atomically
for new descriptors. However, it seems to me that it is almost surely
a mistake if a kqueue
On Sun, Aug 13, 2023 at 11:21:39AM +0100, Stuart Henderson wrote:
> On 2023/08/13 11:13, Omar Polo wrote:
> > @@ -179,7 +179,8 @@ section starts with a declaration of the server
> > Each
> > .Ic server
> > section starts with a declaration of the server
> > -.Ar name :
> > +.Ar name .
> > +If
On Sun, Aug 13, 2023 at 11:13:28AM +0200, Omar Polo wrote:
> [moving to tech@, there's a diff for the manpage below]
>
hi. comments inline:
>
> diff /usr/src
> commit - a7b17fe845fceeb2940fa5924ec5843681aa2c64
> path + /usr/src
> blob - 16b086a9ee00cd6d8e796a890e9774968556f147
> file +
On 2023/08/13 11:13, Omar Polo wrote:
> @@ -179,7 +179,8 @@ section starts with a declaration of the server
> Each
> .Ic server
> section starts with a declaration of the server
> -.Ar name :
> +.Ar name .
> +If no one matches the request the first one defined is used.
> .Bl -tag -width Ds
>
On Sat, Aug 12, 2023 at 06:41:17PM -0400, Andrew Cagney wrote:
> On Sat, 12 Aug 2023 at 16:18, Stuart Henderson wrote:
>
> > > Is there a way to get an updated ISO or kernel with the fix?
> > > (we're already adding an installer config file to the ISO, so why not a
> > > kernel)
> > >
> > >
13.08.2023 12:13, Omar Polo пишет:
> [moving to tech@, there's a diff for the manpage below]
>
> On 2023/08/13 01:04:11 -0700, Alfred Morgan wrote:
>> I was surprised that `server "default"` didn't act like I expected. In this
>> example I expected `test1` to get 200 and everything else to get
[moving to tech@, there's a diff for the manpage below]
On 2023/08/13 01:04:11 -0700, Alfred Morgan wrote:
> I was surprised that `server "default"` didn't act like I expected. In this
> example I expected `test1` to get 200 and everything else to get 404 but
> this is not the case. In this
On Sat, Aug 12, 2023 at 02:40:31PM +0200, Martin Pieuchot wrote:
> So do we want to keep the existing requirement of being able to execute
> a thread on a CPU that has been removed from the scheduler? That's is
> what smr_flush() currently needs. I find it surprising but I can add
> that as a
24 matches
Mail list logo
