On Sun, Dec 11, 2022 at 07:55:44PM -0700, Theo de Raadt wrote:
> The problem you have introduced is that so_state is copied from sockets
> to a sysctl record, where it also shows up as so_state.
>
> At least fstat(8) looks at this field, and uses the old SS_CANTSENDMORE
> bit you have deleted. Th
On Fri, Dec 09, 2022 at 09:32:13PM +, Jason McIntyre wrote:
> hi.
>
> two points about the recent ability to use lladdr:
>
> - the example of "bridge0" made sense when bridge was regarded as a
> separate entity and not integrated with ifconfig. plus a list of one
> example looks rubbish.
The problem you have introduced is that so_state is copied from sockets
to a sysctl record, where it also shows up as so_state.
At least fstat(8) looks at this field, and uses the old SS_CANTSENDMORE
bit you have deleted. The userland-visible name change is an API break.
Furthermore you moved it,
This diff changes the exposed API/ABI, and breaks userland --
which has obviously not experienced a test build.
This is really obvious. If you change a kernel .h file, you have to
check all uses of the file. kernel .h files are installed into /usr/include/sys
and all userland must.
So the mini
This continues previous "Introduce `sb_state' and move
SS_CANTSENDMORE..." diff.
Move socket's SS_CANTRCVMORE and SS_RCVATMARK bits to socket's `so_rcv'
buffer state bits. Moved separately of SS_CANTSENDMORE to make review
and check easier.
As with previous diff, left remaining SS_ bits as is.
I
This would be the diff to swap priority of name/lladdr as some folks
wanted to see. I still don't recommend having both as you can still
have surprising outcomes with more complex configurations.
The install.sub includes an "if_name_to_lladdr" function from the
diff to support creating a hostname
I have a laptop with these Transmeta devices:
pchb0 at pci0 dev 0 function 0 vendor "Transmeta", unknown product 0x0060 rev
0x00
ppb0 at pci0 dev 1 function 0 vendor "Transmeta", unknown product 0x0061 rev
0x00
NetBSD describes device 0061 as the integrated North Bridge, but I think
this is in
> Date: Sun, 11 Dec 2022 09:13:05 -0600
> From: Scott Cheloha
>
> On Sun, Dec 11, 2022 at 01:34:39PM +0100, Mark Kettenis wrote:
> > > Date: Fri, 9 Dec 2022 09:37:11 -0600
> > > From: Scott Cheloha
> > >
> > > On Thu, Dec 08, 2022 at 11:35:34AM +0100, Jeremie Courreges-Anglas wrote:
> > > > On
On Sun, Dec 11, 2022 at 01:34:39PM +0100, Mark Kettenis wrote:
> > Date: Fri, 9 Dec 2022 09:37:11 -0600
> > From: Scott Cheloha
> >
> > On Thu, Dec 08, 2022 at 11:35:34AM +0100, Jeremie Courreges-Anglas wrote:
> > > On Wed, Dec 07 2022, Scott Cheloha wrote:
> > > > ARMv7 has four interrupt clock
> Date: Fri, 9 Dec 2022 09:37:11 -0600
> From: Scott Cheloha
>
> On Thu, Dec 08, 2022 at 11:35:34AM +0100, Jeremie Courreges-Anglas wrote:
> > On Wed, Dec 07 2022, Scott Cheloha wrote:
> > > ARMv7 has four interrupt clocks available. I think it'll be easier to
> > > review/test if we do the clo
10 matches
Mail list logo
