A concerning commit which breaks compatibility

2020-07-23 Thread goldeneagle96
Hello OpenBSD devs. It has come to my attention that a mysterious commit , unlogged by CVS, has appeared. This commit changes language, breaking compatibility on header and source files. Thankfully, it was logged by the Github mirror. The commit's author is the Github username "djmdjm", and the one

Re: dhclient on carp

2020-07-23 Thread David Gwynne
> On 23 Jul 2020, at 22:28, Guy Godfroy wrote: > > Doesn't work better. > I guess Sebastian is right, carp has to be assigned an IP to come up. yeah, i just read the code a bit. they have to be able to communicate to be able to elect which one is the active and which is the backup. i suggest

Re: A concerning commit which breaks compatibility

2020-07-23 Thread Lucas
goldeneagle96 wrote: > Hello OpenBSD devs. It has come to my attention that a mysterious commit > , unlogged by CVS, has appeared. This commit changes language, breaking > compatibility on header and source files. > Thankfully, it was logged by the Github mirror. > The commit's author is the Githu

Re: A concerning commit which breaks compatibility

2020-07-23 Thread infoomatic
this is probably due to the recent social discussion about the black lives matter movement. engineers around the world show their support to this movement against racism by various measurs, e.g. adjusting their code of conduct/rules etc. In many cases, "blacklist" should not relate to something neg

Re: dhclient on carp

2020-07-23 Thread Guy Godfroy
Doesn't work better. I guess Sebastian is right, carp has to be assigned an IP to come up. Le 23/07/2020 à 03:15, David Gwynne a écrit : On 22 Jul 2020, at 22:59, Guy Godfroy wrote: Hello, So I read in 6.7 release note that it's finally possible to use dhclient on CARP interface. That's g