Re: Slow startup from D19488 (rtsol: sendmsg: Permission denied)
On Wed, Mar 30, 2022 at 08:59:24PM -0700, Kevin Oberman wrote: ! > ! I am a bit puzzled as after two years you are the first one to report ! > ! that problem to my knowledge for either base system or jails. ! > ! > This is what greatly wonders me, too. So I was stronly thinking ! > that I am doing something wrong or unusual. But I cannot figure ! > it out, it just seems that the detrimental effect of the change ! > cannot be avoided (e.g. "service jail start" takes quite long now - ! > there's a lot of them). ! This may be irrelevant, but updating to the stable branch is not ! recommended as it is not regularly tested. Updating to 13.0-Release and ! then to stable is less likely to be problematic. Hi Kevin, (You are Kevin Oberman the network guru ?!?) You're essentially right, and I would normally agree. And it is not irrelevant, but then, it's apparently not related to this specific issue. The point is: I am not interested in 13.0. I am interested in 13.1. So I put up a pilot early, in order to report potential issues (as I reported here the issue with the fix for PR 76398). At that point this had to be stable/13. Then on saturday I tried to use fib, and I figured that fib is not fully implenented in 12.3, but apparently it is in 13. So I decided to give it a try and move my backbone to 13 - and to the same version that is already running on the pilot system, so that there is some base to compare things. Now there are issues - but it doesn't appear that these issues would be very different between stable/13 and releng/13.1. And -as can be read above- it neither looks like these issues would just disappear by themselves in the release, without someone looking for them. (The broken "ipfw fwd" is probably also present in 13.0 and will very likely still be present in 13.1 - and I don't believe much in testing because you can only test what you already expect to fail.) I am indeed pondering about the best approach. Over the last years I was only doing release upgrades (after I had run into ugly ZFS problems somewhere in Rel.10, caused by an intermediately broken Stable *and* broken memory chips). Now I am considering to do upgrades some 2-3 months ahead of the release, so if there are problems that hit here, there is a chance to spare the general public one or two troubles. cheerio, PMc
Re: FreeBSD 13.1-RC1 Now Available
Hi! > The first RC build of the 13.1-RELEASE release cycle is now available. If I update my 13.1-BETA2 system to 13.1-RC1, this happens: poudriere jail -u -j 131 -t 13.1-RC1 freebsd-update.fixed: Cannot upgrade from 13.1-RC1 to itself But poudriere jail -l still says: 131 13.1-BETA2 amd64 http 2022-03-19 09:57:44 /pou/jails/131 -- p...@freebsd.org +49 171 3101372 Now what ?
Re: Considering stepping down from all of my FreeBSD responsibilities
In message <20220401064816.gs60...@eureka.lemis.com>, Greg 'groggy' Lehey write s: > > --TSQPSNmi3T91JED+ > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > > On Friday, 1 April 2022 at 5:58:39 +, Alexey Dokuchaev wrote: > > On Fri, Apr 01, 2022 at 02:20:31PM +0900, Yasuhiro Kimura wrote: > >> Hi Glen, > >> > >> From: Glen Barber > >> Subject: Considering stepping down from all of my FreeBSD responsibilities > >> Date: Fri, 1 Apr 2022 00:15:02 + > >> > >>> Dear community, > >>> > >>> Given the mental toll the past two years or so have taken on me, I have > >>> decided to step down from all of my "hats" within the Project, and take > >>> some time to sort out what my future looks like going forward. > >>> > >>> Happy April 1st. I'm not going anywhere. :-) > >> > >> We are waiting for the announce of FreeBSD 2.2.10-RELEASE. :-) > >> > >> Cf. https://lists.freebsd.org/pipermail/freebsd-announce/2006-April/001055 > .html > > > > I don't think 2.2.10 is warranted. > > Agreed. The upgrade isn't sufficiently important. > > How about 2.2.9.1? I had a different more sinister thought: Announcing that we've moved from BSDL to GPLv3 to be more like Linux. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few.
Re: Considering stepping down from all of my FreeBSD responsibilities
On Fri, 01 Apr 2022 09:38:07 -0700 Cy Schubert wrote: > In message <20220401064816.gs60...@eureka.lemis.com>, Greg 'groggy' > Lehey write > s: > > > > --TSQPSNmi3T91JED+ > > Content-Type: text/plain; charset=us-ascii > > Content-Disposition: inline > > > > On Friday, 1 April 2022 at 5:58:39 +, Alexey Dokuchaev wrote: > > > > > On Fri, Apr 01, 2022 at 02:20:31PM +0900, Yasuhiro Kimura wrote: > > >> Hi Glen, > > >> > > >> From: Glen Barber > > >> Subject: Considering stepping down from all of my FreeBSD > > >> responsibilities Date: Fri, 1 Apr 2022 00:15:02 + > > >> > > >>> Dear community, > > >>> > > >>> Given the mental toll the past two years or so have taken on > > >>> me, I have decided to step down from all of my "hats" within > > >>> the Project, and take some time to sort out what my future > > >>> looks like going forward. > > >>> > > >>> Happy April 1st. I'm not going anywhere. :-) > > >> > > >> We are waiting for the announce of FreeBSD 2.2.10-RELEASE. :-) > > >> > > >> Cf. > > >> https://lists.freebsd.org/pipermail/freebsd-announce/2006-April/001055 > > >> > > .html > > > > > > I don't think 2.2.10 is warranted. > > > > Agreed. The upgrade isn't sufficiently important. > > > > How about 2.2.9.1? > > I had a different more sinister thought: Announcing that we've moved > from BSDL to GPLv3 to be more like Linux. > > Take it to the next level. Since we're using git you can make the license change, do the commit, then send the commit email out, and it would have the valid hash and all. - Justin
Re: Considering stepping down from all of my FreeBSD responsibilities
On Fri, Apr 01, 2022 at 11:42:48AM -0500, Justin Hibbits wrote: > On Fri, 01 Apr 2022 09:38:07 -0700 > Cy Schubert wrote: > > > In message <20220401064816.gs60...@eureka.lemis.com>, Greg 'groggy' > > Lehey write > > s: > > > > > > --TSQPSNmi3T91JED+ > > > Content-Type: text/plain; charset=us-ascii > > > Content-Disposition: inline > > > > > > On Friday, 1 April 2022 at 5:58:39 +, Alexey Dokuchaev wrote: > > > > > > > On Fri, Apr 01, 2022 at 02:20:31PM +0900, Yasuhiro Kimura wrote: > > > >> Hi Glen, > > > >> > > > >> From: Glen Barber > > > >> Subject: Considering stepping down from all of my FreeBSD > > > >> responsibilities Date: Fri, 1 Apr 2022 00:15:02 + > > > >> > > > >>> Dear community, > > > >>> > > > >>> Given the mental toll the past two years or so have taken on > > > >>> me, I have decided to step down from all of my "hats" within > > > >>> the Project, and take some time to sort out what my future > > > >>> looks like going forward. > > > >>> > > > >>> Happy April 1st. I'm not going anywhere. :-) > > > >> > > > >> We are waiting for the announce of FreeBSD 2.2.10-RELEASE. :-) > > > >> > > > >> Cf. > > > >> https://lists.freebsd.org/pipermail/freebsd-announce/2006-April/001055 > > > >> > > > .html > > > > > > > > I don't think 2.2.10 is warranted. > > > > > > Agreed. The upgrade isn't sufficiently important. > > > > > > How about 2.2.9.1? > > > > I had a different more sinister thought: Announcing that we've moved > > from BSDL to GPLv3 to be more like Linux. > > > > > > Take it to the next level. Since we're using git you can make the > license change, do the commit, then send the commit email out, and it > would have the valid hash and all. > I was so very close to doing something similar, but I was more worried about screwing up my local trees. Glen signature.asc Description: PGP signature
Re: Considering stepping down from all of my FreeBSD responsibilities
Hi all, > Am 01.04.2022 um 18:38 schrieb Cy Schubert : > I had a different more sinister thought: Announcing that we've moved from > BSDL to GPLv3 to be more like Linux. Don't we need explicit consent from every contributor for such a major license change? Shouldn't we start over from 1.1.5.1 in that case to keep the number of people lower? Patrick -- punkt.de GmbH Patrick M. Hausen .infrastructure Kaiserallee 13a 76133 Karlsruhe Tel. +49 721 9109500 https://infrastructure.punkt.de i...@punkt.de AG Mannheim 108285 Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein
Re: Considering stepping down from all of my FreeBSD responsibilities
On Fri, Apr 01, 2022 at 06:56:27PM +0200, Patrick M. Hausen wrote: > Hi all, > > > Am 01.04.2022 um 18:38 schrieb Cy Schubert : > > I had a different more sinister thought: Announcing that we've moved from > > BSDL to GPLv3 to be more like Linux. > > Don't we need explicit consent from every contributor for such a major > license change? > Shouldn't we start over from 1.1.5.1 in that case to keep the number of > people lower? > You're joking, right? If so, amusing. If not, check the date... Glen signature.asc Description: PGP signature
Re: Considering stepping down from all of my FreeBSD responsibilities
Hi! > Am 01.04.2022 um 19:01 schrieb Glen Barber : > > On Fri, Apr 01, 2022 at 06:56:27PM +0200, Patrick M. Hausen wrote: >> Hi all, >> >>> Am 01.04.2022 um 18:38 schrieb Cy Schubert : >>> I had a different more sinister thought: Announcing that we've moved from >>> BSDL to GPLv3 to be more like Linux. >> >> Don't we need explicit consent from every contributor for such a major >> license change? >> Shouldn't we start over from 1.1.5.1 in that case to keep the number of >> people lower? >> > > You're joking, right? If so, amusing. If not, check the date... I'm German. I never make jokes. Of course!!! :-))) Patrick -- punkt.de GmbH Patrick M. Hausen .infrastructure Kaiserallee 13a 76133 Karlsruhe Tel. +49 721 9109500 https://infrastructure.punkt.de i...@punkt.de AG Mannheim 108285 Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein
Bug 262875 - em(4) driver fails to attach on Dell Latitude 5520 0A21
I submitted subject bug report a few days ago, but did not receive the usual email from bugzilla; and the issue has yet to be assigned. Could someone check to see if it's been overlooked somehow? Anyway, this is the first time I've seen a case where the em driver does not attach to generic Intel hardware. Has anyone else ever seen this? -- Greg
Re: Considering stepping down from all of my FreeBSD responsibilities
On Friday, 1 April 2022 at 9:38:07 -0700, Cy Schubert wrote: > In message <20220401064816.gs60...@eureka.lemis.com>, Greg 'groggy' Lehey > write > s: >> >> --TSQPSNmi3T91JED+ >> Content-Type: text/plain; charset=us-ascii >> Content-Disposition: inline >> >> On Friday, 1 April 2022 at 5:58:39 +, Alexey Dokuchaev wrote: >>> I don't think 2.2.10 is warranted. >> >> Agreed. The upgrade isn't sufficiently important. >> >> How about 2.2.9.1? > > I had a different more sinister thought: Announcing that we've moved from > BSDL to GPLv3 to be more like Linux. Well, since we have accepted (or at least put up with) git, why not? Of course, things go both ways. For those of you who missed it, www.lemis.com/grog/slashdot/ And that wasn't even 1 April. Greg -- Sent from my desktop computer. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php signature.asc Description: PGP signature
