Re: How to upgrade an EOL FreeBSD release or how to make it working again

Old packages are not retained after EOL, but ports are version agnostic (more or less, as the current ports tree is only ar tested to run on supported versions and some are marked as "BROKEN" for some versions). All ports are available from the GIT repo (cgit.freebsd.org). On Mon, Jan 15, 2024 at

Re: NFSv4 crash of CURRENT

On Mon, Jan 15, 2024 at 11:03 AM FreeBSD User wrote: > > Am Mon, 15 Jan 2024 11:53:31 +0100 > Peter Blok schrieb: > > > Hi, > > > > Forgot to mention I’m on 13-stable. The fix that is causing the crash with > > automounted NFS > > is: > > > > commit cc5cda1dbaa907ce52074f47264cc45b5a7d6c8b > >

Re: How to upgrade an EOL FreeBSD release or how to make it working again

Hello. Do you have deleted forever the set of packages and ports for FreeBSD 11 or you keep them stored in DVDs that I can buy or download for a small amount of money ? If yes,where ? To rebuild everything is out of my expertise. On Mon, Jan 15, 2024 at 7:15 PM David Chisnall wrote: > On 15

Re: How to upgrade an EOL FreeBSD release or how to make it working again

On 15 Jan 2024, at 16:46, Mario Marietto wrote: > > The ARM Chromebook is based on armv7,it is still recent. For reference, the ARMv7 architecture was introduced in 2005. The last cores that implemented the architecture were released in 2014. This is not a ‘recent’ architecture, it’s one

suspend to idle support

Hello, What is a status of support suspend to idle? I found only two related reviews D17675 and D17676 and no more any information. It is a very desirable thing on modern laptops, where s3 is not supported like my X1 Carbon gen11[1]. [1] https://wiki.freebsd.org/Laptops/Thinkpad_X1_Carbon

Re: How to upgrade an EOL FreeBSD release or how to make it working again

The ARM Chromebook is based on armv7,it is still recent. But let's change perspective for a moment,don't think about the ARM Chromebook. My question is : how to upgrade FreeBSD when it goes EOL. I ask this because there is a huge difference here between FreeBSD and Linux. Today if you need to use

Re: NFSv4 crash of CURRENT

Am Mon, 15 Jan 2024 16:59:07 +0100 Peter Blok schrieb: > Rick, > > I can confirm Kostik’s fix works on 13-stable. > > Peter Me, too. The patch fixed the reported problem. Thank you very much. oh > > > On 15 Jan 2024, at 16:13, Peter Blok wrote: > > > > I can give it a shot on one of my

Re: NFSv4 crash of CURRENT

Am Mon, 15 Jan 2024 11:53:31 +0100 Peter Blok schrieb: > Hi, > > Forgot to mention I’m on 13-stable. The fix that is causing the crash with > automounted NFS > is: > > commit cc5cda1dbaa907ce52074f47264cc45b5a7d6c8b > Author: Konstantin Belousov > Date: Tue Jan 2 00:22:44 2024 +0200 > >

Re: How to upgrade an EOL FreeBSD release or how to make it working again

Judging by a commit message BSD on the ARM Chromebook didn't work when support was removed in 2019. >RK* Exynos* and Meson*/Odroid* don't even work with current >source code, if someone wants to make them work again they >better use the Linux DTS.

Re: NFSv4 crash of CURRENT

Rick, I can confirm Kostik’s fix works on 13-stable. Peter > On 15 Jan 2024, at 16:13, Peter Blok wrote: > > I can give it a shot on one of my clients. > >> On 15 Jan 2024, at 16:04, Rick Macklem > > wrote: >> >> On Mon, Jan 15, 2024 at 2:53 AM Peter Blok >

Re: NFSv4 crash of CURRENT

I can give it a shot on one of my clients. > On 15 Jan 2024, at 16:04, Rick Macklem wrote: > > On Mon, Jan 15, 2024 at 2:53 AM Peter Blok > wrote: >> >> Hi, >> >> Forgot to mention I’m on 13-stable. The fix that is causing the crash with >> automounted NFS is: >>

Re: NFSv4 crash of CURRENT

On Mon, Jan 15, 2024 at 2:53 AM Peter Blok wrote: > > Hi, > > Forgot to mention I’m on 13-stable. The fix that is causing the crash with > automounted NFS is: > > commit cc5cda1dbaa907ce52074f47264cc45b5a7d6c8b > Author: Konstantin Belousov > Date: Tue Jan 2 00:22:44 2024 +0200 > >

Re: poudriere: swap_pager: out of swap space

On Jan 15, 2024, at 00:07, Lexi Winter wrote: > Mark Millard: >> You seem to be under the impression that "Inact" means "page is not >> dirty" and so can be freed without being written out to the swap >> space. > > indeed, i was, because this is how sysutils/htop displays memory usage: > >

Re: NFSv4 crash of CURRENT

Hi, Forgot to mention I’m on 13-stable. The fix that is causing the crash with automounted NFS is: commit cc5cda1dbaa907ce52074f47264cc45b5a7d6c8b Author: Konstantin Belousov Date: Tue Jan 2 00:22:44 2024 +0200 nfsclient: limit situations when we do unlocked read-ahead by nfsiod

Re: noatime on ufs2

On Jan 15, 2024, at 01:27, Tomoaki AOKI wrote: > On Sun, 14 Jan 2024 16:13:06 -0800 > Mark Millard wrote: > >> On Jan 14, 2024, at 14:27, Tomoaki AOKI wrote: >> >>> On Sun, 14 Jan 2024 10:53:34 -0800 >>> Mark Millard wrote: >>> On Jan 14, 2024, at 08:39, Olivier Certner wrote:

Re: noatime on ufs2

On Sun, 14 Jan 2024 16:13:06 -0800 Mark Millard wrote: > On Jan 14, 2024, at 14:27, Tomoaki AOKI wrote: > > > On Sun, 14 Jan 2024 10:53:34 -0800 > > Mark Millard wrote: > > > >> On Jan 14, 2024, at 08:39, Olivier Certner wrote: > >> > >>> Hi Mark, > >>> > I never use atime, always

Re: NFSv4 crash of CURRENT

Hi, I do have a crash on a NFS client with stable of today (4c4633fdffbe8e4b6d328c2bc9bb3edacc9ab50a). It is also autofs related. Maybe it is the same problem. I have ports automounted on /am/ports. When I do cd /am/ports/sys and type tab to autocomplete it crashes with the below stack trace.

Re: poudriere: swap_pager: out of swap space

Mark Millard: > You seem to be under the impression that "Inact" means "page is not > dirty" and so can be freed without being written out to the swap > space. indeed, i was, because this is how sysutils/htop displays memory usage: top(1) Mem: 8502M Active, 15G Inact, 1568M Laundry, 5518M