On Sun, Feb 27, 2022 at 05:33:17PM +0100, Mark Kettenis wrote:
> > Date: Sun, 27 Feb 2022 16:01:25 +0100
> > From: Anton Lindqvist
> >
> > On Sun, Feb 27, 2022 at 11:08:14AM +0100, Mark Kettenis wrote:
> > > > Date: Sun, 27 Feb 2022 09:56:38 +0100
> > > > From: Anton Lindqvist
> > > >
> > > > O
Todd Mortimer writes:
> I am fine with this, especially since it helps you with the lang/ghc
> port. I am not a fan of the code duplication, but this also code that
> doesn't change much, so I don't see it too much of a burden.
Maybe I can bribe somebody to get an OK before 7.1 then? It'd be
con
Thanks for the comment.
On 2/21/22 21:07, Stefan Sperling wrote:
On Mon, Feb 21, 2022 at 10:20:17AM +0100, Marc Espie wrote:
On Mon, Feb 21, 2022 at 05:36:16PM +0900, Yuichiro NAITO wrote:
Of course, all programs compiled without '-pg' work fine for me.
I found this issue when I profile my app
When you run sysupgrade, you want the firmwares matching what you are
installing.
The system you are running right now is irrelevant. It's drivers
have already loaded the firmwares they need, and a reboot into new
bsd.rd is about to happen.
So why does there continue to be conversation about the
On Mon, Feb 28, 2022 at 05:28:19PM +0100, Stefan Hagen wrote:
> Andrew Hewus Fresh wrote (2022-02-28 15:40 CET):
> > On Mon, Feb 28, 2022 at 02:47:24PM +0100, Stefan Hagen wrote:
> > > But now I see that NEXT_VERSION is set earlier and this should fix it:
> > >
> > > -if $RELEASE && [[ ${_KERNV[1]
Stefan Hagen wrote:
> Andrew Hewus Fresh wrote (2022-02-28 15:40 CET):
> > On Mon, Feb 28, 2022 at 02:47:24PM +0100, Stefan Hagen wrote:
> > > But now I see that NEXT_VERSION is set earlier and this should fix it:
> > >
> > > -if $RELEASE && [[ ${_KERNV[1]} == '-beta' ]]; then
> > > +if $RELEASE
On 2022-02-28 06:30 -08, Andrew Hewus Fresh wrote:
> On Mon, Feb 28, 2022 at 08:27:13AM +0100, Florian Obser wrote:
>> On 2022-02-27 21:33 -08, Andrew Hewus Fresh
>> wrote:
>> > So, sdk@ noticed that sysupgrade didn't get updated for the new logic in
>> > the firmware directories. Specifically
Ignore this report. My tree was out of sync.
> On Feb 28, 2022, at 8:59 AM, Brian Brombacher wrote:
>
On Mon, Feb 28, 2022 at 02:32:07PM +0100, Theo Buehler wrote:
> On Mon, Feb 28, 2022 at 12:35:09PM +0100, Claudio Jeker wrote:
> > From the start bgpd had prefix_link and prefix_unlink to link all the
> > various data objects together to build an actual prefix. Now prefix_move()
> > tries to be sma
On Mon, Feb 28, 2022 at 02:47:24PM +0100, Stefan Hagen wrote:
> But now I see that NEXT_VERSION is set earlier and this should fix it:
>
> -if $RELEASE && [[ ${_KERNV[1]} == '-beta' ]]; then
> +if $RELEASE || [[ ${_KERNV[1]} == '-beta' ]]; then
It would fix this particular case, but this code is
On Mon, Feb 28, 2022 at 08:27:13AM +0100, Florian Obser wrote:
> On 2022-02-27 21:33 -08, Andrew Hewus Fresh
> wrote:
> > So, sdk@ noticed that sysupgrade didn't get updated for the new logic in
> > the firmware directories. Specifically that the only time we use
> > "snapshots" directory is wit
Good morning,
The between 2/5 and 2/27 snapshots, some changes were introduced for vxlan. I
am unable to use a custom port by specifying the port on the end of the
destination tunnel.
ifconfig vxlan0 tunnel 1.2.3.4 5.6.7.8:12345
The packets originating from my host are addressed to port 4789,
On Mon, Feb 28, 2022 at 12:35:09PM +0100, Claudio Jeker wrote:
> From the start bgpd had prefix_link and prefix_unlink to link all the
> various data objects together to build an actual prefix. Now prefix_move()
> tries to be smart and reimplemented prefix_link and prefix_unlink as
> inline version
j...@bitminer.ca wrote in
<07cf90c2d8adab83ffd36ef69ebcd...@bitminer.ca>:
|On 2022-02-27 19:28, Solène wrote:
|> If I remember well, lighttpd will compress server side upon request if
|> a compressed version of that file doesn't exist.
|>
|> This is entirely different than how httpd behave,
On Mon, Feb 28, 2022 at 12:16:58PM +0100, Claudio Jeker wrote:
> rde_dump_adjout_upcall() and rde_dump_adjout_prefix_upcall() work only
> on prefixes that belong to the Adj-RIB-Out so check for the
> PREFIX_FLAG_ADJOUT to make sure it is set.
>
> Other code has the same 'assert' in rde_rib.c and I
>From the start bgpd had prefix_link and prefix_unlink to link all the
various data objects together to build an actual prefix. Now prefix_move()
tries to be smart and reimplemented prefix_link and prefix_unlink as
inline versions (with minimal differences). Later the prefix_adjout_*
functions were
rde_dump_adjout_upcall() and rde_dump_adjout_prefix_upcall() work only
on prefixes that belong to the Adj-RIB-Out so check for the
PREFIX_FLAG_ADJOUT to make sure it is set.
Other code has the same 'assert' in rde_rib.c and I think it makes most
sense to put it here as well.
--
:wq Claudio
Index
Hello,
>
> do you need ddb console ? if you want i can try to reproduce this panic
> without isakmpd, just hitting pfsync setup?
>
>
console might help. I won't be able to get to it before tonight/tomorrow.
I think you can leave isakmpd enabled. it still might be a contributing
On 28.2.2022. 10:49, Alexandr Nedvedicky wrote:
> Hello,
>
>
>>> i will still play with sasyncd setup, maybe something comes up
>>>
>>
>> And when I thought everything is fine.. after 2 days of hitting sasyncd
>> setup I've got this panic .. will stay in ddb if some other information
>> is needed
Hello,
> > i will still play with sasyncd setup, maybe something comes up
> >
>
> And when I thought everything is fine.. after 2 days of hitting sasyncd
> setup I've got this panic .. will stay in ddb if some other information
> is needed
>
I think you are hitting a different issue, whic
On 26.2.2022. 21:36, Hrvoje Popovski wrote:
> On 25.2.2022. 23:22, Alexander Bluhm wrote:
>> On Fri, Feb 25, 2022 at 10:21:50PM +0100, Hrvoje Popovski wrote:
>>> On 24.2.2022. 22:42, Alexander Bluhm wrote:
Hi,
Hrvoje reported some crashes with pfsync, IPsec and parallel
forwardi
21 matches
Mail list logo
