Klemens Nanni wrote:
> On Tue, Jul 26, 2022 at 12:33:34AM +, Klemens Nanni wrote:
> > Some of my test machines only require IPv6 link-local addressing.
> > When SLAAC is available 'autoconf' will do as well, otherwise 'eui64'
> > is required to configure the interface as such.
>
> Sorry,
On Tue, Jul 26, 2022 at 12:33:34AM +, Klemens Nanni wrote:
> Some of my test machines only require IPv6 link-local addressing.
> When SLAAC is available 'autoconf' will do as well, otherwise 'eui64'
> is required to configure the interface as such.
Sorry, that's wrong.
I meant to say that
Some of my test machines only require IPv6 link-local addressing.
When SLAAC is available 'autoconf' will do as well, otherwise 'eui64'
is required to configure the interface as such.
Note this merely expands the list of answers for this specific question.
It does not change any of the
netstart(8) lost bridge specific functionality on 2009.
Replace "bridge" with "X" in the existent sentence and you'll get a
obvious unhelpful statement:
If the network interface is a bridge, the options described in
the bridge section of the ifconfig(8) manual page apply.
Since
netstart(8) lost bridge specific functionality in 2009.
$ grep bridge /etc/netstart
# interfaces (or bridges), add default routes and return.
This is dead unreached code.
OK?
Index: install.sub
===
RCS file:
On Mon, Jul 25, 2022 at 01:52:36PM +0200, Mark Kettenis wrote:
> > Date: Sun, 24 Jul 2022 19:33:57 -0500
> > From: Scott Cheloha
> >
> > On Sat, Jul 23, 2022 at 08:14:32PM -0500, Scott Cheloha wrote:
> > >
> > > [...]
> > >
> > > I don't have a powerpc64 machine, so this is untested. [...]
>
Samuel Venable wrote:
> Hello OpenBSD developers!
>
> I have a suggestion on how to get the current executable path in OpenBSD th=
> at might be reliable enough and not too costly that it might be accepted fo=
> r a future OpenBSD version.
Actually you don't have a suggestion. You are making
Hello OpenBSD developers!
I have a suggestion on how to get the current executable path in OpenBSD that
might be reliable enough and not too costly that it might be accepted for a
future OpenBSD version.
Even if it won't be accepted, I need a little help completing the solution I
have in
On Mon, Jul 25, 2022 at 7:20 AM Theo de Raadt wrote:
> I've been watching conversation on a mailing list, and it leads me to
> wonder if we should inform the userbase better.
>
Too true. Certification *is* the key thing that protects users, not
careful, well engineered designs.
We should be
On Mon, Jul 25, 2022 at 10:19:25AM -0600, Theo de Raadt wrote:
> +number generators, so the security properties cannot be gauranteed.
s/gauranteed/guaranteed
Otherwise OK.
For what It is worth I think the proposed ammendment makes sense.
On Mon, 25 Jul 2022 at 17:23, Theo de Raadt wrote:
> I've been watching conversation on a mailing list, and it leads me to
> wonder if we should inform the userbase better.
>
>
> Index: wg.4
>
I've been watching conversation on a mailing list, and it leads me to
wonder if we should inform the userbase better.
Index: wg.4
===
RCS file: /cvs/src/share/man/man4/wg.4,v
retrieving revision 1.10
diff -u -r1.10 wg.4
--- wg.4
Remove the obsolete "select collisions" count from vmstat(8) output.
Also, remove the reference of the now-nonexistent kernel variable
"nselcoll", and terminate the name list with a NULL as required by
kvm_nlist(3).
OK?
Index: vmstat.c
> Date: Mon, 25 Jul 2022 14:09:25 +
> From: Klemens Nanni
>
> Jul 23 14:43:02 t4 /bsd: out of order
>
> That's a pretty generic message and I currently see a few on my primary
> domain.
>
> I'd like a bit of context in dmesg; this will also turn it up if I grep
> for "vnet" which I often
Jul 23 14:43:02 t4 /bsd: out of order
That's a pretty generic message and I currently see a few on my primary
domain.
I'd like a bit of context in dmesg; this will also turn it up if I grep
for "vnet" which I often do.
Feedback? OK?
Index: vnet.c
On Mon, Jul 25, 2022 at 12:16:50PM +0200, Claudio Jeker wrote:
> The nexthop validation or actually invalidation is buggy in bgpd since
> revision 1.90 of rde_decide.c. When I removed re->active and replaced it
> with a value that is calculated on the spot I did not realize that this
> calculation
On Mon, Jul 25, 2022 at 12:21:00PM +0100, Chris Narkiewicz wrote:
> > to see ioctls you can use ktrace/kdump
>
> Thank you for the hints. I'll try ktrace/kdump and I'll come back with
> the results, probably somehere tomorrow.
>
> > what value do you mean by infinite?
>
> libiris sends ioctl()
> Date: Sun, 24 Jul 2022 19:33:57 -0500
> From: Scott Cheloha
>
> On Sat, Jul 23, 2022 at 08:14:32PM -0500, Scott Cheloha wrote:
> >
> > [...]
> >
> > I don't have a powerpc64 machine, so this is untested. [...]
>
> gkoehler@ has pointed out two dumb typos in the prior patch. My bad.
>
>
The nexthop validation or actually invalidation is buggy in bgpd since
revision 1.90 of rde_decide.c. When I removed re->active and replaced it
with a value that is calculated on the spot I did not realize that this
calculation depends on the current nexthop state and not on the state used
on the
On Sun, Jul 24, 2022 at 12:09:50PM +0100, Chris Narkiewicz wrote:
> Hi,
>
> Some time ago I posted a bug on bugs@ (subject: X11 hangs on StarLabs Mk IV -
> snapshot 06-06-2022).
> We did some checks with help of one of the developers, but we could not find
> a cause then.
>
> I started digging
Hi,
some changes to /share/misc/airport to treat german umlauts more
consistently, remove the "Flugplatz" (german for airport, which is kind
of redundant as it is all airports in the list), remove NRW which does
not exist as IATA code, remove THF which is gone since 2010.
-Thomas
Index:
21 matches
Mail list logo
