From nobody Sat Oct 28 17:42:33 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SHn1H6Cq8z504Q8 for ; Sat, 28 Oct 2023 17:42:43 +0000 (UTC) (envelope-from zlei@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SHn1H5dyJz3cln; Sat, 28 Oct 2023 17:42:43 +0000 (UTC) (envelope-from zlei@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698514963; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ztMp6mjsN8LjbHNZmMAWYLlYQhmZiZhT5O8CCxTNwRc=; b=hbbiAFkF59ykS94mq7V87iqPlsJTKOywaFXu9+a7plUZfTXdpYO7lDdlWndmpYpkOcjXRP sFRSu2ZRsEqHEH5sUhdQT8Jm51D19pXXjmDK+mCr3PZFC/8UKSb/bbmULJE+Hji+C+gy3p U8hG3eDCurpoBcPhLqjNSlxji2NQrsqntaHaSAKrxVwjzzXSFiUkdLsOJJkL4gh9ikMTsg A1ImqNM3cZsFl4kV5yoG5Qs9pqjc0SNwa7vFcEHcKxI4WIwxjoPb5+lpbRL6YEywk5+l6w ikRnOJuAur6ODMCBsr2DK3dcdrLCTl65bJKEUy8xrwkt5wDw+yMFA7nGMWfnFg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698514963; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ztMp6mjsN8LjbHNZmMAWYLlYQhmZiZhT5O8CCxTNwRc=; b=LvhTFAbrFIFFHA2vIqwh/df/4/yrLqAEW3zRvuLzBMjRBB5LzOpsFCsr2TtVaEfnWIrfNS xuYMXQ5X7oah+hUkE82LGL3/KwHOwP+YUmG70L0dsfqxBaZubzr3Q1Z3jIkCv3OkNPKJLd Fu9Afl82k6ltEsL7FUnv5G6bh97bIKju3KO+Yx591K9s5aIpbZiousBxUSArbigtSuwLY+ PoalDNdVTI6KXNNVABDwCeJPUEpZk2JrbzgEE15PWbXOAVupAEqBt0D29nadcYEHhY9FQy XwAdlBVDKa5OnK1/gQbWMqh6x1//lV9H1jK+4JJu97xpUDWAh1OFvysL2wKkRQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1698514963; a=rsa-sha256; cv=none; b=BcqlIm/5dxQeqFy1eAbN79JaqFGF2454qpt33TAAFziVa1Fw1IM73WdKKFMgNSHEZYa+61 VxdLxItNNAW5HU8LsqSWCD58Wkwz4vq2XfsoGf5wWACm8iU95WZaDUhw0cj3G/iBlA4fx/ v+facX+oGTMVOMoiaqymuSVeL4hRCylTKJ6boTWCOXIjYicPGmV3Pi186xwKVE27VUmF5d C5xfqylS1J2BBueAPB3N0b0aOH2t4Sco5ptHVM9XwbxV/HCgUqzhCvNK+tDF+7wi8qzo/F F6M9zvcv5GigbrPIMhRzfY0lCxpkGk9g40w7bBZsc3wDll7Ycj2SkZbbLryDDw== Received: from smtpclient.apple (unknown [IPv6:2001:19f0:6001:9db:98f0:9fe0:3545:10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: zlei/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4SHn1G28fqz1JLX; Sat, 28 Oct 2023 17:42:42 +0000 (UTC) (envelope-from zlei@FreeBSD.org) From: Zhenlei Huang Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_8ABD1179-D785-417B-9867-9B1FE6D91C07" List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\)) Subject: Re: atrtc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 14 Date: Sun, 29 Oct 2023 01:42:33 +0800 In-Reply-To: Cc: Warner Losh , FreeBSD Current To: Warner Losh References: X-Mailer: Apple Mail (2.3696.120.41.1.4) --Apple-Mail=_8ABD1179-D785-417B-9867-9B1FE6D91C07 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Oct 29, 2023, at 1:22 AM, Warner Losh wrote: >=20 >=20 >=20 > On Sat, Oct 28, 2023, 11:04 AM Zhenlei Huang > wrote: > Hi Warner, >=20 > I see this from boot log of 14.0-RC3: >=20 > > FreeBSD 14.0-RC3 #0 releng/14.0-n265368-c6cfdc130554: Fri Oct 27 = 05:57:28 UTC 2023 > > ... > > atrtc0: non-PNP ISA device will be removed from GENERIC in FreeBSD = 14. >=20 > I guess atrtc(4) is still supported by FreeBSD 14. > So this should be bumped to 15 at least. Am I right ? >=20 > Yes. Someone, maybe you, submitted a pr to do that. Posted to https://reviews.freebsd.org/D42387 = . >=20 > Warner >=20 > Best regards, > Zhenlei >=20 --Apple-Mail=_8ABD1179-D785-417B-9867-9B1FE6D91C07 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii

On Oct 29, 2023, at 1:22 AM, Warner Losh <imp@bsdimp.com> wrote:



On Sat, Oct 28, 2023, 11:04 AM Zhenlei Huang <zlei@freebsd.org> wrote:
Hi Warner,

I see this from boot log of 14.0-RC3:

> FreeBSD 14.0-RC3 #0 releng/14.0-n265368-c6cfdc130554: Fri Oct 27 05:57:28 UTC 2023
> ...
> atrtc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 14.

I guess atrtc(4) is still supported by FreeBSD 14.
So this should be bumped to 15 at least. Am I right ?

Yes. Someone, maybe you, submitted a pr to do that.




Warner

Best regards,
Zhenlei




--Apple-Mail=_8ABD1179-D785-417B-9867-9B1FE6D91C07-- From nobody Sun Oct 29 09:43:06 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SJBKV3rd6z4yl3F for ; Sun, 29 Oct 2023 09:43:10 +0000 (UTC) (envelope-from gbe@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SJBKV2qxvz4dtm for ; Sun, 29 Oct 2023 09:43:10 +0000 (UTC) (envelope-from gbe@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698572590; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=M8lDIh+svHKSihnjyBmo+at8QOIYJe9tSc8b6d44gXU=; b=SEDNhk2rvpgnm6DJFIVx/6Qa8N2VSFGU8F/51EuTCdQK9/vj2eoh3RMeBRlGbENTIbzIrg U+FBv/QtmL7qhRz+9JLivhZSGeTSRcUbo9seJSXfS6R7Ya+VDUlH13Ff5JTvjy0+tsVIYG hiP9x/0jbHXSfPscuQV8Mq9PC6DpUEbHSco86kaSX8AAPefOGQUZ+hnUGVCKVwH+GuNmz+ WN/ICBdDyI3VRRnG0DiKX7MtWoisY/eWv6Zwwprz8Mx7acYuyxXSnNLt5Rx64KI2SoH7fe xlTXkdPOfAjjCeLWZQJgBooi5qOQ0G3FVOyx+YZjoUoDqzcsx7Mq9gAJNrRQjQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698572590; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=M8lDIh+svHKSihnjyBmo+at8QOIYJe9tSc8b6d44gXU=; b=cvi7w8CZYJiTPRLZIuXvB0xkvImLBr6TOm8gBuBjIPITq9nLQFDCizhUMpYJ+UP191WDAa ozXm/3pkv3IqLpQI3aLUZBLCfca88PUjlS+03DhcB6GUvU3n2K+B14ng44CtuXWE1APzG1 bAYFrTq32YEghvr/4+gwxrjzQ40Viq6h6lurS1+QL4gdjAqfcKN+Of7I4mvLtIA/VTGylv NUrO4qSkhe/76ZP7fs+GwU4SwerXdYPIUvAA3uqVxsPng5Cg0nopXS9t+pYMow1ZthlSdH YeZGMX9YUwll7Lp8rhMMYC4oAg3XDPLyK03SyeBhGriUq97X7Z84va0n+HSf+g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1698572590; a=rsa-sha256; cv=none; b=b4gc0stI15sa9JqeleVtY5lTkOrbRDqc4YmwQ9uQlyXs8ogKWXAelkfqJCPAH8aygvAdKe 6eea7MpY3SEE7WiJwRYR/kI1UbLvlJ4Jscj/zl79S1y+blesL21AhtaO60g2hkcdpdlNA7 KeMFTJ/lYZ0UKYG2L8AjJ1QkFZAfk+eN4WI/vuWfhKy0Vt3QssdsmMGoRKCEl/ToSCgvPT ppR6OXXjRG6IJ36Qb5yJxSeKEF20VMEpypDBZRC+RbqASl2ajbUlZvsRKlYw4DaPF0GjfJ kDKTGE2IO/dLTQ7gWMd7yL0U/hDBwxmekAV0mK3RshlcRxSR8lQEm1tYFJ+AlQ== Received: from localhost (p200300cb87090964f814e8f11b727bb7.dip0.t-ipconnect.de [IPv6:2003:cb:8709:964:f814:e8f1:1b72:7bb7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: gbe) by smtp.freebsd.org (Postfix) with ESMTPSA id 4SJBKT5yMQz9V2 for ; Sun, 29 Oct 2023 09:43:09 +0000 (UTC) (envelope-from gbe@freebsd.org) Date: Sun, 29 Oct 2023 10:43:06 +0100 From: Gordon Bergling To: current@freebsd.org Subject: KTLS thread on 14.0-RC3 Message-ID: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="TO7HEBFaguDenEwB" Content-Disposition: inline X-Url: X-Operating-System: FreeBSD 14.0-RC3 amd64 X-Host-Uptime: 10:35AM up 2:48, 1 user, load averages: 0.04, 0.17, 0.16 --TO7HEBFaguDenEwB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I am currently building a new system, which should be based on 14.0-RELEASE. Therefor I am tracking releng/14.0 since its creation and updating it currently via the usualy buildworld steps. What I have noticed recently is, that the [KTLS] is missing. I have a stable/13 system which shows the [KTLS] thread and a very recent -CURRENT that also shows the [KTLS] thread. The stable/13 and releng/14.0 systems both use the GENERIC kernel, without any custom modifications. Loaded KLDs are also the same. Did I miss something, or is there something in releng/14.0 missing, which is currenlty enabled in stable/13? Any help for getting an insight on this would be much appreciated. --Gordon --TO7HEBFaguDenEwB Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEYbWI0KY5X7yH/Fy4OQX2V8rP09wFAmU+KSgACgkQOQX2V8rP 09wd0wgArZrxO22qd0zPX/ro8EFC8aV2fVgsgq3jeYup3/E9AKFG8RKPlBPYLJB3 I8J31stUKCQ5Xw3n63h2KojDdCx8w777TkLkkg+D28mHyx8Bm0VndVfiCVLj9Cdu UFUk8Ly/K7BOmJc33yNPmBZiE3QWNqQe+hur5Jy62A5Hr0UhazZ/Vbsx6evH/4zo W9pFPded8PuOG/c4SkyQ1j9ZQLhCMFaQPy40zJpkE7WRwSNxGQ1zEE74HETmY8Hv AdMnLckMlb4QLZkkiB40gJsKoNNA1ajO/V1WbtF683OPvzf8ssMLYXPZUAm/vjCI Cx/fKnpPrZQdlFoiyl3J3E4GKEjSoA== =1mpa -----END PGP SIGNATURE----- --TO7HEBFaguDenEwB-- From nobody Mon Oct 30 04:09:00 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SJfsc6Jlhz4ycld for ; Mon, 30 Oct 2023 04:09:08 +0000 (UTC) (envelope-from zlei@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SJfsc5S6Rz3SpR; Mon, 30 Oct 2023 04:09:08 +0000 (UTC) (envelope-from zlei@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698638948; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YGmg6HCM3RoeVy5XYeGllr2NILw0vRhgknGxDnS4P54=; b=wOQbzVF7Y9078ecf2RvdPfDO8c2AjrB5G11EvGCYuxqDe7BqooY/qhR7PiAP58N6jHbx3m Uvh8KEhQTFRUVQ1zAhLjgTyhQ827S4RHUZHuuCEFDuLZWnNRJF06Bruyh3u41CsZ8gC4Q2 Pb35bxCGA0QQrVwT/UzWScZXAnN1laCz1hlTHzb2tYbQloDTeA2LgHn2YbQ8h3WNYqzEqk +E+NogsAFc0LMemLg0MuH2omN606PTT0GngdQ7qbMgc+QN14SP29wMldgXzqYNmTVG5A0N XnDv3HM7hBe2J3THsJfX4nVuSlHYJ4zOmkKU5wrUuMbudj8gxR0UybEesgInbA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698638948; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YGmg6HCM3RoeVy5XYeGllr2NILw0vRhgknGxDnS4P54=; b=CShixa7zaVbz0PQJOCrFwCB1gZfW9n1QnNAHM2jU77PD8NHctJIZwr8/YiBhZ/ampGkwoK FmAIJqn7jlcJrABNPjAMfIHsM6mw9mYtptd0gf9YxoTrkj4huRehr+n8VlzZCXkBFZBJl6 LeIM8jW9XPsaLRTBWVYB7mc4pZpQOhpNDbxSkaIrfRL4uodh5/12VJvYj+SlPiwslXIGrs CxQkWNveHA4VXrF3jGWlPy4VZFepCqQ6Oa3k28O3kHxtg54RTgvsgac7PsyaCTBkWX5J2r myhxyMMLfmdRbPngeWc2PSXY7NCVYodqZDmPwsW79SF/voGMnW7gp3WDbXe/wg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1698638948; a=rsa-sha256; cv=none; b=h/xl7kOT7Bn4Nln7ZmWPiCxWMCmP7pYz6XS+88tvNOm4k6Ml3U7tKAKep9X3MkZEprbKY4 w1ODekoYuQCJa+tbFE8Jxt6ZdeOCYz4q2QwErwchD9HjZqQWf9uJZ6mutZDXL+uNXIQ8/u Vc5aS5aDzca5JojrNXhkDyHdHOzKq3KkQOu+7EmhqF1+1QUK9rCbuOSuM0VvG8pTa93vWZ JAWGNgcrrTjgeV/ITQjTa+m0k2RlkGXtQNTDlMJcBx4oeaHY/xzAc6395NJgO1anUzDiMr s1C9syQ9E7hGd0kgbnynCQsjzHytLapCC2d35rTPkmleae3N2AuN/U1HfAwe9w== Received: from smtpclient.apple (ns1.oxydns.net [45.32.91.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: zlei/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4SJfsb3phQz11kJ; Mon, 30 Oct 2023 04:09:07 +0000 (UTC) (envelope-from zlei@FreeBSD.org) Content-Type: text/plain; charset=us-ascii List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\)) Subject: Re: KTLS thread on 14.0-RC3 From: Zhenlei Huang In-Reply-To: Date: Mon, 30 Oct 2023 12:09:00 +0800 Cc: FreeBSD Current , John Baldwin Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Gordon Bergling X-Mailer: Apple Mail (2.3696.120.41.1.4) > On Oct 29, 2023, at 5:43 PM, Gordon Bergling wrote: >=20 > Hi, >=20 > I am currently building a new system, which should be based on = 14.0-RELEASE. > Therefor I am tracking releng/14.0 since its creation and updating it = currently > via the usualy buildworld steps. >=20 > What I have noticed recently is, that the [KTLS] is missing. I have a = stable/13 > system which shows the [KTLS] thread and a very recent -CURRENT that = also shows > the [KTLS] thread. >=20 > The stable/13 and releng/14.0 systems both use the GENERIC kernel, = without any > custom modifications. >=20 > Loaded KLDs are also the same. >=20 > Did I miss something, or is there something in releng/14.0 missing, = which > is currenlty enabled in stable/13? KTLS shall still work as intended, the creation of it threads is = deferred. See a72ee355646c (ktls: Defer creation of threads and zones until first = use) > Run ktls_init() when the first KTLS session is created rather than > unconditionally during boot. This avoids creating unused threads and > allocating unused resources on systems which do not use KTLS. ``` -SYSINIT(ktls, SI_SUB_SMP + 1, SI_ORDER_ANY, ktls_init, NULL); ``` >=20 > Any help for getting an insight on this would be much appreciated. >=20 > --Gordon Best regards, Zhenlei From nobody Mon Oct 30 10:41:40 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SJqZh4xvwz4xlS2 for ; Mon, 30 Oct 2023 10:41:48 +0000 (UTC) (envelope-from zlei@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SJqZh4X1vz4Trm; Mon, 30 Oct 2023 10:41:48 +0000 (UTC) (envelope-from zlei@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698662508; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=rKr57jjqZMslwVZLiq8w8hnQDupGMrMtueXCmSsA4rI=; b=JsLiACILjCS9KTmqrmBcO5Z693CtCdwB10Zc/rFD4Aly1qSqbSorMzjCDFrb5H3OzTGAJO 2Mato3ht6SaQrqIy6stlC23inj++Tvwvl4MPrRn3h0wY+OUDU1HcVE4f8oZjdB3+3elTYK aGYwB6ahlxBBKjnkZ0QHEY4E2C1Ar/IpcR1iligT4TJfecti/ygRwm1ddYp/klhL+4pDeI bweTRQrW1v2rrC47cl5tzW/jiQtpGuBKA1pv/aihgXdb+VQDXpYRwGo6ITODqcTt1T/rNu 94TCyokqbEFVfSPjK5783jan25dBZropFIkvgliIlxwLGBKG4lqsFKJ6KuT2UQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698662508; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=rKr57jjqZMslwVZLiq8w8hnQDupGMrMtueXCmSsA4rI=; b=uqmFk6+2D4GeokIahBvCnWPfsycub47gyCbTF9HYy93OV+Pzgv2I5OPORVXorkhSV9hF4X E31BC+nlrR8q+WvKsbL48re3zH9KtnUS5ePLqBu9su+AEczanNV+HaaFs0zdya4S+qyJrX 07BBfHfIgb+nuk5fePkWNNDmJenIOLRFSwPwjkedXyUq1lL1r9n9+kqAZ9QCEY/KfU2PtX xCjG5i73RcBwFFx7ArtepB/8PRKv2Tjext2nlWmfGfISOMOg6uaZkGWQapmOJS6f+PlANb tM3wzQZ5z4cKWa4fCHOcdpnV0dtFb8qaIVdctQj0Ogg7ZKl//P8HvvdaFIdHfQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1698662508; a=rsa-sha256; cv=none; b=i/ZG+0kEtIdTK0Gi2ieKv5vQQyAoRV9mo5DZiCCIvJ69gA7V8QyoYnGSHrMcILDhDtNJY+ MGrP/zZBjVDHqAv5lXIys44jqaNs6rhNGhfsQsr589EEajYsUN4kQf8UyXKbMVc1DSWFzz NBdie/PFv7pgEUyeXhEZG2lVPNb4TjYGj/MWlQGVBhOAtwWCOui6NtUxWqf8DbgkdjS/K4 V9kDGMWTLunmM1/HEMbTaCLAQrJsKvkoV4wTgQHDGqStN5AGMQMCDkpNc0rBeRh50g/ekJ Yjs02aw8Ei0scLVTzt11p9m+T7FkGeaG8LreBlL8vCj27SnR0vbRJAyGa75eDg== Received: from smtpclient.apple (unknown [112.66.185.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: zlei/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4SJqZg07mpz18gS; Mon, 30 Oct 2023 10:41:46 +0000 (UTC) (envelope-from zlei@FreeBSD.org) From: Zhenlei Huang Message-Id: <53AC8651-141E-4950-84D9-FD94E8B353FD@FreeBSD.org> Content-Type: multipart/alternative; boundary="Apple-Mail=_35A4EFE7-AC3E-4F7D-AC0C-C61CB780B6B4" List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\)) Subject: Re: KTLS thread on 14.0-RC3 Date: Mon, 30 Oct 2023 18:41:40 +0800 In-Reply-To: Cc: FreeBSD Current , John Baldwin To: Gordon Bergling References: X-Mailer: Apple Mail (2.3696.120.41.1.4) --Apple-Mail=_35A4EFE7-AC3E-4F7D-AC0C-C61CB780B6B4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Oct 30, 2023, at 12:09 PM, Zhenlei Huang wrote: >=20 >=20 >=20 >> On Oct 29, 2023, at 5:43 PM, Gordon Bergling wrote: >>=20 >> Hi, >>=20 >> I am currently building a new system, which should be based on = 14.0-RELEASE. >> Therefor I am tracking releng/14.0 since its creation and updating it = currently >> via the usualy buildworld steps. >>=20 >> What I have noticed recently is, that the [KTLS] is missing. I have a = stable/13 >> system which shows the [KTLS] thread and a very recent -CURRENT that = also shows >> the [KTLS] thread. >>=20 >> The stable/13 and releng/14.0 systems both use the GENERIC kernel, = without any >> custom modifications. >>=20 >> Loaded KLDs are also the same. >>=20 >> Did I miss something, or is there something in releng/14.0 missing, = which >> is currenlty enabled in stable/13? >=20 > KTLS shall still work as intended, the creation of it threads is = deferred. >=20 > See a72ee355646c (ktls: Defer creation of threads and zones until = first use) >> Run ktls_init() when the first KTLS session is created rather than >> unconditionally during boot. This avoids creating unused threads and >> allocating unused resources on systems which do not use KTLS. >=20 > ``` > -SYSINIT(ktls, SI_SUB_SMP + 1, SI_ORDER_ANY, ktls_init, NULL); > ``` Seems 14.0 only create one KTLS thread. IIRC 13.2 create one thread per core. >=20 >>=20 >> Any help for getting an insight on this would be much appreciated. >>=20 >> --Gordon >=20 >=20 > Best regards, > Zhenlei --Apple-Mail=_35A4EFE7-AC3E-4F7D-AC0C-C61CB780B6B4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

On Oct 30, 2023, at 12:09 PM, Zhenlei Huang <zlei@FreeBSD.org> = wrote:



On Oct 29, 2023, at 5:43 PM, Gordon = Bergling <gbe@freebsd.org> wrote:

Hi,

I am currently building a = new system, which should be based on 14.0-RELEASE.
Therefor = I am tracking releng/14.0 since its creation and updating it = currently
via the usualy buildworld steps.
What I have noticed recently is, that the [KTLS] is missing. = I have a stable/13
system which shows the [KTLS] thread = and a very recent -CURRENT that also shows
the [KTLS] = thread.

The stable/13 and releng/14.0 = systems both use the GENERIC kernel, without any
custom = modifications.

Loaded KLDs are also the = same.

Did I miss something, or is there = something in releng/14.0 missing, which
is currenlty = enabled in stable/13?

KTLS shall still work as intended, the creation of it threads = is deferred.

See = a72ee355646c (ktls: Defer creation of threads and zones until first = use)
Run = ktls_init() when the first KTLS session is created rather than
unconditionally during boot.  This avoids creating = unused threads and
allocating unused resources on systems = which do not use KTLS.

```
-SYSINIT(ktls, = SI_SUB_SMP + 1, SI_ORDER_ANY, ktls_init, NULL);
```

Seems = 14.0 only create one KTLS thread.

IIRC= 13.2 create one thread per core.



Any help for getting = an insight on this would be much appreciated.

--Gordon


Best regards,
Zhenlei



= --Apple-Mail=_35A4EFE7-AC3E-4F7D-AC0C-C61CB780B6B4-- From nobody Tue Oct 31 17:06:13 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SKc433lNSz4ycy2 for ; Tue, 31 Oct 2023 17:06:27 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SKc433H6nz3f0h; Tue, 31 Oct 2023 17:06:27 +0000 (UTC) (envelope-from jhb@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698771987; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=nVQXcJvTo37mpcM+BubQzBH9z2UxmiQttWUvmSmE880=; b=hv9x3cCH7MXKeCu4RKnO4Q7T5/AlqhD81Gs8hWfEIhpLmAe1D3JG6No5hgm2E05huDchK5 11Pb7ApP4RLOfAYiksSsrUmkpVImG+aVLDh0UEFgGpcxw8kjv2cL91XJ+we1X04LAs0kkQ 8n2iUgkIkYNsAexbbkPAkK5cFPi5FWtC9dnyMsyOMveRt7LCTdnwGWcgprlQkj4EGuBg/D +7Z1ebk4dOSli+ghe9VMCcXzo7PNSRytqUFndSfnbwsOwBTh2/6EhbzMUPOwUWXjCX/Xz4 qjanZjUjFKHLaMlB2wZmtcYRkdFWPtpxJiFNUtdTa6vhdXP/QUwdapneZL64TA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698771987; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=nVQXcJvTo37mpcM+BubQzBH9z2UxmiQttWUvmSmE880=; b=BCJ0e/Esd4zCeFu1KIR1ZQ2T+4+qJqZzewgvEhvRI/4GYM0BnN1Ea4t0cOg+7hlegz5ZPd iJplsYVSMVCOVuzGHt5jTlOL3JCXpx14sAx+ieAg2Y4uQtDwj8RL4MUtdjMcmwtRwUCeXz ld9NgkH37TCrZym65MdOwea8CDPuLFTqEDgLWM4nAcLwc5nu9PGOxNofT0JxTYd3gBwWsD uzZW+5N+A3+JL61AIOj0DtuyBjEYYqiPYk7atIHQaN5EaxPafSiJh/FpAGMS7HfjLH6uT0 aBwOdiLWFslWcRM+KsCoUDjaOHnU/bA8mumCR/hVzwZLVGxtDPJcuX0+xaYuAA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1698771987; a=rsa-sha256; cv=none; b=pM08izAONSzSW7KqLHMVzLlioUhsUrbS7pA7i42ZHEbnm2ufLhsmmj8ttfa3XM6mR9G9og rvTSL7u3pfrfS8CEczRy0PAw7EZsuuJrW7ab132iwRDRCv7cDl2pTF/cndza/aJ9ngRfij 1yO2UhgngjzjN6gyDm5XOsPhTGs2rGySqAD8HZqZJcFzklxQb/Q7woOpZfhLyYGxasKfdG 5bdesqbkh8pqRPtcpeDA7sveY6IZsp/l5y5N70Jyl984piIZk6ISgsw1r7DInB9Q1oklJ9 sJ3PuzDdOVRRNCVspfB3Ts4YY1JOnqEGsGQZl8HhJoc+dKaLjzJo6iqmBVWlPQ== Received: from [10.0.0.43] (unknown [98.47.13.2]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: jhb) by smtp.freebsd.org (Postfix) with ESMTPSA id 4SKc426CxTzkxY; Tue, 31 Oct 2023 17:06:26 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Message-ID: <77952261-2fe0-428e-b72c-d805f0273a76@FreeBSD.org> Date: Tue, 31 Oct 2023 10:06:13 -0700 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: KTLS thread on 14.0-RC3 Content-Language: en-US To: Zhenlei Huang , Gordon Bergling Cc: FreeBSD Current , gallatin@FreeBSD.org References: <53AC8651-141E-4950-84D9-FD94E8B353FD@FreeBSD.org> From: John Baldwin In-Reply-To: <53AC8651-141E-4950-84D9-FD94E8B353FD@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 10/30/23 3:41 AM, Zhenlei Huang wrote: > > >> On Oct 30, 2023, at 12:09 PM, Zhenlei Huang wrote: >> >> >> >>> On Oct 29, 2023, at 5:43 PM, Gordon Bergling wrote: >>> >>> Hi, >>> >>> I am currently building a new system, which should be based on 14.0-RELEASE. >>> Therefor I am tracking releng/14.0 since its creation and updating it currently >>> via the usualy buildworld steps. >>> >>> What I have noticed recently is, that the [KTLS] is missing. I have a stable/13 >>> system which shows the [KTLS] thread and a very recent -CURRENT that also shows >>> the [KTLS] thread. >>> >>> The stable/13 and releng/14.0 systems both use the GENERIC kernel, without any >>> custom modifications. >>> >>> Loaded KLDs are also the same. >>> >>> Did I miss something, or is there something in releng/14.0 missing, which >>> is currenlty enabled in stable/13? >> >> KTLS shall still work as intended, the creation of it threads is deferred. >> >> See a72ee355646c (ktls: Defer creation of threads and zones until first use) >>> Run ktls_init() when the first KTLS session is created rather than >>> unconditionally during boot. This avoids creating unused threads and >>> allocating unused resources on systems which do not use KTLS. >> >> ``` >> -SYSINIT(ktls, SI_SUB_SMP + 1, SI_ORDER_ANY, ktls_init, NULL); >> ``` > > Seems 14.0 only create one KTLS thread. > > IIRC 13.2 create one thread per core. That part should not be different. There should always be one thread per core. -- John Baldwin From nobody Tue Oct 31 22:45:23 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SKlbM0G8Mz4y2Jw for ; Tue, 31 Oct 2023 22:45:35 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4SKlbK0Mnvz4cFM; Tue, 31 Oct 2023 22:45:32 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of jamie@catflap.org designates 2001:19f0:7400:8808:123::1 as permitted sender) smtp.mailfrom=jamie@catflap.org; dmarc=pass (policy=none) header.from=catflap.org X-Catflap-Envelope-From: X-Catflap-Envelope-To: bapt@freebsd.org Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 39VMjNus080966; Tue, 31 Oct 2023 22:45:23 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 39VMjNJB080965; Tue, 31 Oct 2023 22:45:23 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202310312245.39VMjNJB080965@donotpassgo.dyslexicfish.net> Date: Tue, 31 Oct 2023 22:45:23 +0000 Organization: Dyslexic Fish To: bapt@freebsd.org, freebsd-current@freebsd.org Subject: Freebsd 14+ -- tcsh incompatible with terminfo User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Tue, 31 Oct 2023 22:45:23 +0000 (GMT) X-Spamd-Result: default: False [0.25 / 15.00]; NEURAL_SPAM_LONG(0.96)[0.958]; DMARC_POLICY_ALLOW(-0.50)[catflap.org,none]; NEURAL_HAM_MEDIUM(-0.20)[-0.202]; R_SPF_ALLOW(-0.20)[+mx:dyslexicfish.net]; NEURAL_SPAM_SHORT(0.19)[0.193]; MIME_GOOD(-0.10)[text/plain]; RCVD_NO_TLS_LAST(0.10)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; ARC_NA(0.00)[]; BLOCKLISTDE_FAIL(0.00)[209.250.224.51:server fail,2001:19f0:7400:8808:123::1:server fail]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[jamie]; RCPT_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_ORG_HEADER(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4SKlbK0Mnvz4cFM X-Spamd-Bar: / Hi! The changes to FreeBSD base ncurses to use the terminfo db over termcap if it exists have caused a few issues with tcsh, which doesn't seem to grok terminfo. e.g. : install misc-terminfo switch to tcsh, and reinitialise terminal information: % setenv TERM dumb % setenv TERM xterm % echotc AF 1 echotc: `AF' requires 2 arguments. Deleting the relevent terminfo entry, and reinitialising the terminal information causes everything to work again. Tested on stock 14.0-RC3 I have some other locally grown stuff that complains for similar reasons, that I'll have to fix too, but in the meantime, what's the easiest way to force any program to use termcap over terminfo rather than the other way around, or is this the wrong approach? I considered kludging with environment variables TERMINFO/TERMCAP, but these are login based rather than program based, and if instead set inside a program, could cause spawned programs to also be polluted, if not careful, especially with a shell. Cheers, Jamie From nobody Tue Oct 31 22:59:48 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SKlvp2tqkz4y3G6 for ; Tue, 31 Oct 2023 22:59:50 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4SKlvp1cxmz4dvc; Tue, 31 Oct 2023 22:59:50 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; none X-Catflap-Envelope-From: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 39VMxm59081151; Tue, 31 Oct 2023 22:59:49 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 39VMxm6W081150; Tue, 31 Oct 2023 22:59:48 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202310312259.39VMxm6W081150@donotpassgo.dyslexicfish.net> Date: Tue, 31 Oct 2023 22:59:48 +0000 Organization: Dyslexic Fish To: jamie@catflap.org, freebsd-current@FreeBSD.org, bapt@FreeBSD.org Subject: Re: Freebsd 14+ -- tcsh incompatible with terminfo References: <202310312245.39VMjNJB080965@donotpassgo.dyslexicfish.net> In-Reply-To: <202310312245.39VMjNJB080965@donotpassgo.dyslexicfish.net> User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Tue, 31 Oct 2023 22:59:49 +0000 (GMT) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US] X-Rspamd-Queue-Id: 4SKlvp1cxmz4dvc Jamie Landeg-Jones wrote: > switch to tcsh, and reinitialise terminal information: > > % setenv TERM dumb > % setenv TERM xterm % setenv TERM xterm-256color Apologies, it seems this doesn't affect plain "xterm", but it does at least affect xterm-16color and xterm-256color. Is this, therefore, a terminfo.db issue? Thanks again, Jamie From nobody Wed Nov 1 00:18:05 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SKnfK0t5rz4y893 for ; Wed, 1 Nov 2023 00:18:17 +0000 (UTC) (envelope-from btv1==669c19df0ec==tom@invisible-island.net) Received: from smtp-2a.his.com (dc-16.his.net [108.56.65.16]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4SKnfJ3Zs9z3HYR for ; Wed, 1 Nov 2023 00:18:16 +0000 (UTC) (envelope-from btv1==669c19df0ec==tom@invisible-island.net) Authentication-Results: mx1.freebsd.org; none Received: from cuda501.his.com (cuda501.his.com [18.191.10.220]) by smtp-2a.his.com (Postfix) with ESMTPS id 45610C7 for ; Tue, 31 Oct 2023 20:18:10 -0400 (EDT) X-ASG-Debug-ID: 1698797889-1f26af249d3f0a30001-XDYc8F Received: from smtp-4a.his.com (smtp-4a.his.com [216.194.253.31]) by cuda501.his.com with ESMTP id h1fJzKKs4MtaSEXs (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 31 Oct 2023 20:18:09 -0400 (EDT) X-Barracuda-Envelope-From: tom@invisible-island.net X-Barracuda-RBL-Trusted-Forwarder: 216.194.253.31 Received: from zproxy101.his.com (zproxy101.his.com [18.218.2.49]) by smtp-4a.his.com (Postfix) with ESMTPS id 4439187; Tue, 31 Oct 2023 20:18:09 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by zproxy101.his.com (Postfix) with ESMTP id 1759D17753A; Tue, 31 Oct 2023 20:18:09 -0400 (EDT) X-Barracuda-RBL-Trusted-Forwarder: 18.218.2.49 Received: from zproxy101.his.com ([127.0.0.1]) by localhost (zproxy101.his.com [127.0.0.1]) (amavis, port 10032) with ESMTP id stK2o3iCQspt; Tue, 31 Oct 2023 20:18:09 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by zproxy101.his.com (Postfix) with ESMTP id F258A177538; Tue, 31 Oct 2023 20:18:08 -0400 (EDT) X-Virus-Scanned: amavis at zproxy101.his.com Received: from zproxy101.his.com ([127.0.0.1]) by localhost (zproxy101.his.com [127.0.0.1]) (amavis, port 10026) with ESMTP id tdz3yDpAKeQJ; Tue, 31 Oct 2023 20:18:08 -0400 (EDT) Received: from prl-debianold-64.jexium-island.net (static-96-255-221-90.washdc.fios.verizon.net [96.255.221.90]) by zproxy101.his.com (Postfix) with ESMTPSA id DBB8917753C; Tue, 31 Oct 2023 20:18:08 -0400 (EDT) Received: from tom by prl-debianold-64.jexium-island.net with local (Exim 4.94.2) (envelope-from ) id 1qxyvt-000I6S-1o; Tue, 31 Oct 2023 20:18:05 -0400 X-Barracuda-RBL-IP: 96.255.221.90 X-Barracuda-Effective-Source-IP: static-96-255-221-90.washdc.fios.verizon.net[96.255.221.90] X-Barracuda-Apparent-Source-IP: 96.255.221.90 Date: Tue, 31 Oct 2023 20:18:05 -0400 From: Thomas Dickey To: Jamie Landeg-Jones Cc: freebsd-current@freebsd.org, bapt@freebsd.org Subject: Re: Freebsd 14+ -- tcsh incompatible with terminfo Message-ID: X-ASG-Orig-Subj: Re: Freebsd 14+ -- tcsh incompatible with terminfo Reply-To: dickey@his.com References: <202310312245.39VMjNJB080965@donotpassgo.dyslexicfish.net> <202310312259.39VMxm6W081150@donotpassgo.dyslexicfish.net> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="XnAKLCn0WtGE0TZ3" Content-Disposition: inline In-Reply-To: <202310312259.39VMxm6W081150@donotpassgo.dyslexicfish.net> X-Barracuda-Connect: smtp-4a.his.com[216.194.253.31] X-Barracuda-Start-Time: 1698797889 X-Barracuda-Encrypted: TLS_AES_256_GCM_SHA384 X-Barracuda-URL: https://spam.his.com:443/cgi-mod/mark.cgi X-Barracuda-BRTS-Status: 1 X-Virus-Scanned: by bsmtpd at his.com X-Barracuda-Scan-Msg-Size: 1049 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=5.0 KILL_LEVEL=7.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.116147 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:701, ipnet:108.56.0.0/16, country:US] X-Rspamd-Queue-Id: 4SKnfJ3Zs9z3HYR --XnAKLCn0WtGE0TZ3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 31, 2023 at 10:59:48PM +0000, Jamie Landeg-Jones wrote: > Jamie Landeg-Jones wrote: >=20 > > switch to tcsh, and reinitialise terminal information: > > > > % setenv TERM dumb > > % setenv TERM xterm >=20 > % setenv TERM xterm-256color >=20 > Apologies, it seems this doesn't affect plain "xterm", but it does at lea= st=20 > affect xterm-16color and xterm-256color. actually it probably does affect "xterm"=20 Checking the source, tcsh is expecting a termcap string, while data read =66rom the terminfo database is going to be in terminfo format -- even if read via tgetent/tgetstr tcsh is expecting a termcap string, and in its EchoTC function it duplicates the termcap version of what's tparm in a terminfo program. (tcsh could be modified readily to use terminfo for the case you're describ= ing, but supporting $TERMCAP would be work) =20 > Is this, therefore, a terminfo.db issue? >=20 > Thanks again, Jamie >=20 --=20 Thomas E. Dickey https://invisible-island.net --XnAKLCn0WtGE0TZ3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAABCgAdFiEEGYgtkt2kxADCLA1WzCr0RyFnvgMFAmVBmTkACgkQzCr0RyFn vgPRlAv5Ac27UAjTp2Jl5DjsKm9b7GlNdsbS1UBmjiwXUigAo3jD7n4ptBxkSHro WHNzf909A9I41K3WpPSTYUmWu3mAfka/L35/vBvDZZbVAKAyGO1lyzxUzBMP5R9c DbtmbAlHI+92V3xZhqgkvRPBIV8XfycVrvFGQHPHcYWkvbDucyO+pE+6aBdFxn6T /Fj4byuAIlGBXdf/Xb4xfBFs3819ZMlpZuongpwwhF05u69RqHKfTutoxMAZqy7N nJ0mTQ19RqVRjb7p1wwHTxJjFw36UGCUNUNvImMH5Eosrp0Wg+XjeTQpE7lIcZeQ 7qysclmrXhlgpCJPeHVHwc6i09dNHYE0ZPI82Zxc5kXOig1JctiaZDq7eXdJnWIx 4+eIgZ82JgcZ8rraeB3V+24c++odb81ZckUfpZt1aWlTFhGFzyUgE4UDMtYCIH9b LNL3noa9WTDHWHGdUDt08FDsVIi28aS1WrrdB08E1jWklgiNheyy5BXy1Gq46UQN 72k4m1Xi =RqJ9 -----END PGP SIGNATURE----- --XnAKLCn0WtGE0TZ3-- From nobody Wed Nov 1 00:37:46 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SKp5258VNz4y98Z for ; Wed, 1 Nov 2023 00:37:58 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SKp5211pvz3Knk; Wed, 1 Nov 2023 00:37:58 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pl1-x62c.google.com with SMTP id d9443c01a7336-1cc3bc5df96so24899245ad.2; Tue, 31 Oct 2023 17:37:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698799077; x=1699403877; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=yQvUBb8eP5BIvwAjq6wCleLY88/yT2kiqS90RRtyZNU=; b=DUEfZz0oQATpxoAk6TGQduvaJ0LJJfc87+OopxxZgVV1XMSdbqW9nUYllmhDv3kWGT +bJngSt3kz+CEakcOC3s6U1yGXZyrlABU6w9JUrUMuSbhZhccwtqFSqUMHHrfxBcvF0u Yx0tTY+cey7shdK+bMG7LPA8X9Vy8qlPTekOQ1h497+c3Pt6rsWIW+lspXIKvHxZCPq0 NinsMnyl2yEbJ/3ql89uro6qg43wae6YEbjIzkVPJobm8IW2ZY1tdjPpzdVMXk46wbdy rkhihiqBC/3GRFBfjc71KW111Ggzc71j/tUSlDYTsh+lPaIirxuV5LYnS1/xiXiuKVxp mKog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698799077; x=1699403877; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=yQvUBb8eP5BIvwAjq6wCleLY88/yT2kiqS90RRtyZNU=; b=va2oPwge3bC4rJMgUXx21f/aKCNq11+hiSe3L68tKfb++M0xaXwXAinFZsnyuUneLJ cWFCoVLn60GVBauNuioeMrSwBmvnDaesIGJHnwhrhwCLcoYsxnAgwm2mPxceVXGUBYJ7 LBxwFtaTk82KK64INyhhUP8IfPPFne7uTL4lcXYA7mllFpqDjuseXObazP4LIS0l8vjl zQ6X/747VILKCuROcfW0J9MECJDtStQSFYUuPA7+ROU9lsFtYufRdiGD7f8i4uc7D4i6 Hrbg+HQl14UD39G2bUEtRKWYx32fcXhQVZbC3HR0GaNjJjcU2ALwqrBJe3/+E91G0/+T 7Kkg== X-Gm-Message-State: AOJu0Ywp/sLPWIhmc5IG5uiy3hhi7VZxvORvc8G8qjYFEHV5Jj0Q1Hld Aat4oMFOF/L7nQDQA8aOzh1yeiPHiy9GYIAbppRNhooe2A== X-Google-Smtp-Source: AGHT+IGprBf9kbnPiB4i8NpTkNYbfJDzTCgec6SHezl8Cw/QlQOaxDocrcpe5EmQuVwfxPdlqRQiL9n7xMmQv9eC7eQ= X-Received: by 2002:a17:90b:4a05:b0:280:99f0:4234 with SMTP id kk5-20020a17090b4a0500b0028099f04234mr2854767pjb.7.1698799076804; Tue, 31 Oct 2023 17:37:56 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <53AC8651-141E-4950-84D9-FD94E8B353FD@FreeBSD.org> <77952261-2fe0-428e-b72c-d805f0273a76@FreeBSD.org> In-Reply-To: <77952261-2fe0-428e-b72c-d805f0273a76@FreeBSD.org> From: Rick Macklem Date: Tue, 31 Oct 2023 17:37:46 -0700 Message-ID: Subject: Re: KTLS thread on 14.0-RC3 To: John Baldwin Cc: Zhenlei Huang , Gordon Bergling , FreeBSD Current , gallatin@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Queue-Id: 4SKp5211pvz3Knk On Tue, Oct 31, 2023 at 10:06=E2=80=AFAM John Baldwin wro= te: > > On 10/30/23 3:41 AM, Zhenlei Huang wrote: > > > > > >> On Oct 30, 2023, at 12:09 PM, Zhenlei Huang wrote: > >> > >> > >> > >>> On Oct 29, 2023, at 5:43 PM, Gordon Bergling wrote: > >>> > >>> Hi, > >>> > >>> I am currently building a new system, which should be based on 14.0-R= ELEASE. > >>> Therefor I am tracking releng/14.0 since its creation and updating it= currently > >>> via the usualy buildworld steps. > >>> > >>> What I have noticed recently is, that the [KTLS] is missing. I have a= stable/13 > >>> system which shows the [KTLS] thread and a very recent -CURRENT that = also shows > >>> the [KTLS] thread. > >>> > >>> The stable/13 and releng/14.0 systems both use the GENERIC kernel, wi= thout any > >>> custom modifications. > >>> > >>> Loaded KLDs are also the same. > >>> > >>> Did I miss something, or is there something in releng/14.0 missing, w= hich > >>> is currenlty enabled in stable/13? > >> > >> KTLS shall still work as intended, the creation of it threads is defer= red. > >> > >> See a72ee355646c (ktls: Defer creation of threads and zones until firs= t use) > >>> Run ktls_init() when the first KTLS session is created rather than > >>> unconditionally during boot. This avoids creating unused threads and > >>> allocating unused resources on systems which do not use KTLS. > >> > >> ``` > >> -SYSINIT(ktls, SI_SUB_SMP + 1, SI_ORDER_ANY, ktls_init, NULL); > >> ``` > > > > Seems 14.0 only create one KTLS thread. > > > > IIRC 13.2 create one thread per core. > > That part should not be different. There should always be one thread per= core. Just fyi, I see one thread/core. Did you happen to do something like "ps ax" instead of "ps axHl"? rick ps: I also see a reclaim_0 thread. > > -- > John Baldwin > > From nobody Wed Nov 1 01:01:32 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SKpcQ4n7Kz4yR9l for ; Wed, 1 Nov 2023 01:01:42 +0000 (UTC) (envelope-from zlei@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SKpcQ4L3jz3Mmf; Wed, 1 Nov 2023 01:01:42 +0000 (UTC) (envelope-from zlei@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698800502; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=FhmwNQxwUeEmBjqoRw200ufn2KYn0CbJx3yukAUk2gA=; b=NYlskJaxOtNv/7MpOJXQTtdiEEu6Svfr3qBdH5pYPeV61gkrJfQKZVIeVbhesBSaOxdR5t eBSNlHih6uXGBEO9jRUpkg5NjyKGi2ibpIps3DgDoxM6iddhlA9dtMX8W5jTynbw0MoODl THA/33KZyzWa37EJ+FA7ol2QGnzAOPx1W+uTsFag8EZcjtcWTG3+sBkMzx0nEsPG2RzhXS mF0H5//Cf1DnMcqUjhDd2xhzI5lerUHGwxXtbr+ec2znI9q1mzuSuRGZ7jqONKOz04Y173 r1QmU0jZcXqKWBNUvzLabylesT2IR0ULUYf86ugRS33R3JDuW5rAnxJVhmfR7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698800502; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=FhmwNQxwUeEmBjqoRw200ufn2KYn0CbJx3yukAUk2gA=; b=X2pLRyQZiSXnI7SrDa7EX+vEsIO9LgJknqa/hEhhPuLInK8mVzLu0VmVrBkz1t5RI42r3s kDezOK3+NyLCVgQzJWrYhJPYVnGflu0z0eXbs/z8KWg9tuI3bW6qkjk/rdRfTPqjE4CC9h cXldD/EdVWNmPFZNQU7qdk5LvkIzpHaOu32rmEtcfEO0u7goN1+U8kguzeyvNUjdfgX22h Br0ZXgP8DB5tVCCkKm3gHRVgt5v8REkfmeYMJhzV+Q9syzMKwhbvsWEoE6bzdMTYTDPdC5 CfvP9oOkCPuP3ycBEItHtqsRbZdCS9JYrgfKlG/Arwt8zEuF8x6tYkvJPEwNHQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1698800502; a=rsa-sha256; cv=none; b=QDZw33TSjY0Ic4ydHrnjPh/At88eWr8db3QSEpiPTKiBTCjXFYVNPiQXGp0OKY/g2wSDik xfaOFtAKQy/7+0zs/f10bR9jU/uebzCaPb0xjozV+RzR3HImcLHKnNmdwmlDp/ta0A00FX rnrDOF/jdbJ5REYgHaSNySILY+1uQMW5/rI+u+iGC2sHy/W3KBqouy0VdhPUOq4ncF2i/h Eh86N9Ocg7uiJAMif/egotHofzPwdf6+L1l/kpH6NBFgQnTA3Zl72n0rh/L5CmpqfTtEFN JwMu95jOu4xJ9rredWMsoDkdfv0atJDpggt6JE7owRFqIC9o6y10SnkMKZg+Jg== Received: from smtpclient.apple (unknown [IPv6:2001:19f0:6001:9db:98f0:9fe0:3545:10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: zlei/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4SKpcN4Fpmzsqs; Wed, 1 Nov 2023 01:01:40 +0000 (UTC) (envelope-from zlei@FreeBSD.org) From: Zhenlei Huang Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_E2A72CED-7518-44EF-9F30-A7D526AA07AC" List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\)) Subject: Re: KTLS thread on 14.0-RC3 Date: Wed, 1 Nov 2023 09:01:32 +0800 In-Reply-To: Cc: John Baldwin , Gordon Bergling , FreeBSD Current , gallatin@freebsd.org To: Rick Macklem References: <53AC8651-141E-4950-84D9-FD94E8B353FD@FreeBSD.org> <77952261-2fe0-428e-b72c-d805f0273a76@FreeBSD.org> X-Mailer: Apple Mail (2.3696.120.41.1.4) --Apple-Mail=_E2A72CED-7518-44EF-9F30-A7D526AA07AC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Nov 1, 2023, at 8:37 AM, Rick Macklem = wrote: >=20 > On Tue, Oct 31, 2023 at 10:06=E2=80=AFAM John Baldwin > wrote: >>=20 >> On 10/30/23 3:41 AM, Zhenlei Huang wrote: >>>=20 >>>=20 >>>> On Oct 30, 2023, at 12:09 PM, Zhenlei Huang = wrote: >>>>=20 >>>>=20 >>>>=20 >>>>> On Oct 29, 2023, at 5:43 PM, Gordon Bergling = wrote: >>>>>=20 >>>>> Hi, >>>>>=20 >>>>> I am currently building a new system, which should be based on = 14.0-RELEASE. >>>>> Therefor I am tracking releng/14.0 since its creation and updating = it currently >>>>> via the usualy buildworld steps. >>>>>=20 >>>>> What I have noticed recently is, that the [KTLS] is missing. I = have a stable/13 >>>>> system which shows the [KTLS] thread and a very recent -CURRENT = that also shows >>>>> the [KTLS] thread. >>>>>=20 >>>>> The stable/13 and releng/14.0 systems both use the GENERIC kernel, = without any >>>>> custom modifications. >>>>>=20 >>>>> Loaded KLDs are also the same. >>>>>=20 >>>>> Did I miss something, or is there something in releng/14.0 = missing, which >>>>> is currenlty enabled in stable/13? >>>>=20 >>>> KTLS shall still work as intended, the creation of it threads is = deferred. >>>>=20 >>>> See a72ee355646c (ktls: Defer creation of threads and zones until = first use) >>>>> Run ktls_init() when the first KTLS session is created rather than >>>>> unconditionally during boot. This avoids creating unused threads = and >>>>> allocating unused resources on systems which do not use KTLS. >>>>=20 >>>> ``` >>>> -SYSINIT(ktls, SI_SUB_SMP + 1, SI_ORDER_ANY, ktls_init, NULL); >>>> ``` >>>=20 >>> Seems 14.0 only create one KTLS thread. >>>=20 >>> IIRC 13.2 create one thread per core. >>=20 >> That part should not be different. There should always be one thread = per core. > Just fyi, I see one thread/core. > Did you happen to do something like "ps ax" instead of "ps axHl"? Yes, I typed "ps auxx". `ps axHl` is the right way to get kernel = threads. Sorry for the noise. >=20 > rick > ps: I also see a reclaim_0 thread. >=20 >>=20 >> -- >> John Baldwin --Apple-Mail=_E2A72CED-7518-44EF-9F30-A7D526AA07AC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On Nov 1, 2023, at 8:37 AM, Rick Macklem <rick.macklem@gmail.com> wrote:

On Tue, Oct 31, 2023 at 10:06=E2=80=AFAM John Baldwin = <jhb@freebsd.org> = wrote:

On 10/30/23 3:41 AM, Zhenlei Huang wrote:


On Oct 30, 2023, at = 12:09 PM, Zhenlei Huang <zlei@FreeBSD.org> wrote:



On Oct 29, 2023, at 5:43 PM, Gordon Bergling <gbe@freebsd.org> = wrote:

Hi,

I = am currently building a new system, which should be based on = 14.0-RELEASE.
Therefor I am tracking releng/14.0 since its = creation and updating it currently
via the usualy = buildworld steps.

What I have noticed = recently is, that the [KTLS] is missing. I have a stable/13
system which shows the [KTLS] thread and a very recent = -CURRENT that also shows
the [KTLS] thread.

The stable/13 and releng/14.0 systems both use = the GENERIC kernel, without any
custom modifications.

Loaded KLDs are also the same.
Did I miss something, or is there something in releng/14.0 = missing, which
is currenlty enabled in stable/13?

KTLS shall still work as = intended, the creation of it threads is deferred.

See a72ee355646c (ktls: Defer creation of threads and zones = until first use)
Run = ktls_init() when the first KTLS session is created rather than
unconditionally during boot.  This avoids creating = unused threads and
allocating unused resources on systems = which do not use KTLS.

```
-SYSINIT(ktls, SI_SUB_SMP + 1, SI_ORDER_ANY, ktls_init, = NULL);
```

Seems = 14.0 only create one KTLS thread.

IIRC 13.2 = create one thread per core.

That= part should not be different.  There should always be one thread = per core.
Just fyi, I see one thread/core.
Did you = happen to do something like "ps ax" instead of "ps axHl"?

Yes, I typed "ps auxx".  `ps = axHl` is the right way to get kernel threads.
Sorry for the = noise.


rick
ps: I also = see a reclaim_0 thread.


--
John = Baldwin



= --Apple-Mail=_E2A72CED-7518-44EF-9F30-A7D526AA07AC-- From nobody Wed Nov 1 03:49:33 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SKtLC2QWhz4yfGn for ; Wed, 1 Nov 2023 03:49:39 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4SKtLB3nq1z4Rjp; Wed, 1 Nov 2023 03:49:38 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; none X-Catflap-Envelope-From: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 3A13nX3d094464; Wed, 1 Nov 2023 03:49:33 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 3A13nX1M094463; Wed, 1 Nov 2023 03:49:33 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202311010349.3A13nX1M094463@donotpassgo.dyslexicfish.net> Date: Wed, 01 Nov 2023 03:49:33 +0000 Organization: Dyslexic Fish To: jamie@catflap.org, dickey@his.com Cc: freebsd-current@FreeBSD.org, bapt@FreeBSD.org Subject: Re: Freebsd 14+ -- tcsh incompatible with terminfo References: <202310312245.39VMjNJB080965@donotpassgo.dyslexicfish.net> <202310312259.39VMxm6W081150@donotpassgo.dyslexicfish.net> In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Wed, 01 Nov 2023 03:49:33 +0000 (GMT) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US] X-Rspamd-Queue-Id: 4SKtLB3nq1z4Rjp Thomas Dickey wrote: > actually it probably does affect "xterm" > > Checking the source, tcsh is expecting a termcap string, while data read > from the terminfo database is going to be in terminfo format -- even if > read via tgetent/tgetstr > > tcsh is expecting a termcap string, and in its EchoTC function it duplicates > the termcap version of what's tparm in a terminfo program. > > (tcsh could be modified readily to use terminfo for the case you're describing, > but supporting $TERMCAP would be work) Hi Thomas, thanks for the reply... from the ncurses man himself! I *thought* I'd seen issues with just "xterm" but after posting the first message, it seemed to start working, and so I doubted myself, but I must have messed up somewhere! What threw me about tcsh is it does mention terminfo in the man page and the source, so I wrongly assumed the problem wasn't there. Anyway, I'll raise it with the tcsh maintainers. To the FreeBSD release folk, I think it's great that we're moving off termcap, but is there a chance that base tcsh could be compiled with a private version of the terminfo-less ncurses in time for 14.0-RELEASE, if a proper fix to tcsh is going to take too long? Thanks again, Thomas. Cheers, Jamie From nobody Wed Nov 1 15:01:05 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SL9Dx5mB5z4yRSH; Wed, 1 Nov 2023 15:01:05 +0000 (UTC) (envelope-from salvadore@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SL9Dx5NPWz4YBT; Wed, 1 Nov 2023 15:01:05 +0000 (UTC) (envelope-from salvadore@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698850865; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=rZWnhkuO43bqOY2WC46VagOEZE7iAWVe8q+EEe6B6Q8=; b=Wo67U9/cjQCe53U9WZpEhdbM0GPnb6uaRL+asRosDtUUivFkBDVBbfGSouvUM2yCClKRnw TBkl3uCr9fWEGM2ehFtapMLFLSQ5WG6NXvnERN2/hyfD8fmQxzctAMBFomT5DBSRiyCgPe BXgnPJ880+9iOvccS4fA2RKY5jsMHzj6TdXf59mWIO7xqCKPVoe8c2TMbczTMwqzmdGYi7 2RUnW16DCwMvAZEeyEItEuVAB8O6oel8IcRcEk1RvdB/WDagbKWcF9RNHxOyeyQV5blMVx UmrLb1TPFRWzgwuf7lbwJEOdK9SxlFxFoFIGht+vefjWlB1OsOQkpcQP0tjEcQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698850865; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=rZWnhkuO43bqOY2WC46VagOEZE7iAWVe8q+EEe6B6Q8=; b=xZ/9YuwoI4HtdAn37TM0lemK354lajghxldtvTK8P3UQnQwcDfgurddDMkyQoaa6YioqFC hsOq4TNlNaiPf9eClLxgxPbAXQ9sNmDFPoc/8oKZeVbolIwk/7pt6GmYkSgrqGtE/9hG86 a/JqQGQjFYYEwwuCd7NJPldvWunQ4T7amniHd72YGjreS+MHnZwn6x7ra822NCJDWqzzEv 8Hca8Y682U2z1AvGyGHYyT0NR9M6scLj2TDhLEL9M1vZGfUHPmLnf5xFDClbOcLuRccU8w 2/GG8n/CP+etbkd+doh1Ac0w+jO9D0qGwsVounMYgUD9S+l+i3MHUoMqn/jbnQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1698850865; a=rsa-sha256; cv=none; b=JBMcQeqeR27cguN6traFrr6NskPAeVJ8adfAKRd+qxenNBNp4i6Iw6IvfbW9MhVpZ6emx1 qHFxb1yjgBUyyDpXr4U+ElwxrS/8AQaeCQB8mTa1qerG12wXDsrRB33k2Y98lW7Da981W5 Z7phn4iwXmomc0U8A8quJLiWk1mWWu5qlZOrKubFRJTwTxtqsSoCUSFrGnagQUgCkXB3u1 kX/cvi08SHTEOFxEyGq01yZqGR2PnZHhvjrQqqJcBqTSF7Jp0+fuG98ydLZA3NEWVtPJ3y ukBhdd+S/gEfnvRvaEBtpzSLuhjEEosQhM2p75ZQaqLF32PjSlZrfgjHZCfq/Q== Received: by freefall.freebsd.org (Postfix, from userid 1472) id 896E03A70; Wed, 1 Nov 2023 15:01:05 +0000 (UTC) Date: Wed, 1 Nov 2023 15:01:05 +0000 From: Lorenzo Salvadore To: freebsd-hackers@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: FreeBSD Status Report - Third Quarter 2023 Message-ID: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline; filename=report Content-Transfer-Encoding: 8bit FreeBSD Status Report Third Quarter 2023 Here is the third 2023 status report, with 32 entries. This is the summer quarter and thus it includes many interesting news from Google Summer of Code. Of course, we also have our usual team reports and many projects share with us their latest news. Much important work has been done for the first release of FreeBSD 14. Have a nice read. Lorenzo Salvadore, on behalf of the Status Team. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ A rendered version of this report is available here: https://www.freebsd.org/status/report-2023-07-2023-09/ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Core Team □ FreeBSD Foundation □ FreeBSD Release Engineering Team □ Continuous Integration □ Ports Collection • Projects □ Filling gaps in the FreeBSD desktop experience □ LLDB Kernel Module Improvement • Userland □ OpenSSL 3 in base — Improved □ Login Classes Fixes and Improvements □ Process Visibility Security Policies □ Linux compatibility layer update • Kernel □ Enabling Snapshots on Filesystems Using Journaled Soft Updates □ SquashFS driver for FreeBSD kernel • Architectures □ NXP DPAA2 support □ SIMD enhancements for amd64 □ Integrate mfsBSD into the Release Building Tools • Cloud □ OpenStack on FreeBSD □ FreeBSD on Microsoft HyperV and Azure □ FreeBSD on EC2 • Documentation □ Documentation Engineering Team □ FreeBSD Online Editor and Man Page Editor □ FreeBSD Expert System • Ports □ KDE on FreeBSD □ Pantheon desktop on FreeBSD □ FreeBSD Office Team □ Wifibox: Use Linux to Drive your Wireless Card on FreeBSD □ GCC on FreeBSD □ Valgrind: valgrind-devel updated for FreeBSD 15 □ GitLab 16.3 Available □ PortOptsCLI — Ports Collection Accessibility • Third Party Projects □ Introducing the BSD Cafe project □ Containers and FreeBSD: Pot, Potluck and Potman ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. Demise of Hans Petter Selasky The FreeBSD Core Team would like to thank Hans Petter Selasky for his years of service. We were saddened by his death and joined the community in mourning. In Memoriam. Meetings with The FreeBSD Foundation The Core Team and The FreeBSD Foundation continue to meet to discuss the next steps to take for the management, development, and future of FreeBSD. The Core Team had two meetings with the Board of Directors, and employees of, the Foundation. They discussed how the Foundation can help the Core Team and the Project in general. Portmgr termlimits The Core Team discussed with the Ports Management Team the introduction of a time limit in which a developer can belong to the team. The proposal was approved by the Ports Management Team and will take effect at the beginning of 2024, with regular lurker programs to have a steady stream of new Ports Management Team members. Deprecation of 32-bit platforms for FreeBSD 15 Work is underway to mark support for 32-bit platforms as "deprecated" for FreeBSD 15. Matrix IM The testing of the Matrix instance and the Element-web client is still in progress. The beta is planned to be released after EuroBSDCon in September. Improve Commit Bit Expiration Policy The Core Team will clarify how to update the PGP key once a developer has become Alumni. EuroBSDCon Core Team members met with the FreeBSD Foundation in Coimbra during EuroBSDcon to discuss the direction of the Project. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Foundation Links: FreeBSD Foundation URL: https://freebsdfoundation.org/ Technology Roadmap URL: https://freebsdfoundation.org/blog/technology-roadmap/ Donate URL: https://freebsdfoundation.org/donate/ Foundation Partnership Program URL: https://freebsdfoundation.org/our-donors/ freebsd-foundation-partnership-program/ FreeBSD Journal URL: https://freebsdfoundation.org/journal/ Foundation Events URL: https://freebsdfoundation.org/our-work/events/ Contact: Deb Goodkin The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide. Donations from individuals and corporations fund and manage software development projects, conferences, and developer summits. We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and cluster administration efforts. We publish marketing material to promote, educate, and advocate for FreeBSD, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity. This quarter we helped FreeBSD celebrate its 30th anniversary! This excitement has propelled us to accelerate our efforts to move FreeBSD forward in growth and innovation, which has focused us on identifying key areas we can invest our resources. At our board meeting in September, we refined our goals to focus on increasing FreeBSD adoption and visibility, diversifying our funding stream, and investing in the community health and long-term stability of the Project. We are in the process of identifying the key audiences and markets to target, while putting measurable outcomes to these goals. In this status report, you will read more about our work to help further FreeBSD’s growth and innovation. We will highlight all the technical work we are doing to improve FreeBSD, both by our internal staff of software developers, as well as external project funding efforts. You will read about our advocacy work to promote FreeBSD to audiences outside of our community. Finally, you will see the great efforts made to connect with current and potential commercial users. Fundraising We would like to express our sincere gratitude to all those who generously donated to support our work. In addition to numerous individual contributions, we are especially grateful for the significant donations from NetApp, Netflix, and ARM. In Q3 alone, we received $183,842, bringing our total for the year to $375,000. This year our budget is around $2,230,000, which includes increased spending toward FreeBSD advocacy and software development. More than half of our budget is allocated toward work directly related to improving FreeBSD and keeping it secure. By providing a dedicated individual focused on partnerships, we can effectively emphasize the significance of investing in our efforts and underscore the long-term viability of FreeBSD to companies. Your support is crucial to our mission, and we deeply appreciate your commitment to the FreeBSD community. Please consider making a donation toward our 2023 fundraising campaign! https://freebsdfoundation.org/donate/ For our larger commercial donors, check out our updated FreeBSD Foundation Partnership Program. Partnerships and Research For Partnerships and Research this quarter, progress was made in three key areas: First, the Enterprise Working Group started to gather steam with growth up to 58 participants and active projects in four work streams. These are cloud native, Samba, bhyve manageability, and support for AI workloads. There is interest in several additional areas and I expect that by the end of this year and Q1 of next year, we will see meaningful feature updates in multiple areas of focus. Second, we made good progress working with other open source community members and organizations, notably the Open Source Initiative, to advance proposals and technology from the FreeBSD community. Working with the Open Source Initiative’s Open Policy Alliance, we are submitting a response to the US government’s request for information on how the US government can support open source security and sustainability. As part of this, Greg Wallace participated on a panel organized by the Open Policy Alliance at the recent All Things Open conference in Raleigh, North Carolina. Greg Wallace has also been tracking how the US government incorporates CHERI into its policy recommendations for security by default, such as this recent report from US and global government security agencies. On Page 28, CHERI is listed right after Rust as a key 'Secure by Design' tactic. Finally, we continue to strengthen partnerships with a growing number of companies using FreeBSD. Several conferences aided these relationships, including EuroBSDCon, Open Source Summit, and All Things Open. We have also developed a new program to support vendor/cloud users that work with the US government. The program details will be announced at the FreeBSD Vendor Summit. Advocacy Much of our effort is dedicated to the FreeBSD Project advocacy. This may involve highlighting interesting FreeBSD work, producing literature and video tutorials, attending events, or giving presentations. The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier. Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables. The FreeBSD Foundation sponsors many conferences, events, and summits around the globe. These events can be BSD-related, open source, or technology events geared towards underrepresented groups. We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users. This all helps provide a healthy ecosystem. We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project. We continue to add new events to our yearly roster. This July, we held a workshop and staffed a table at FOSSY, a new open source conference in Portland, Oregon. In addition to attending and planning conferences, we are continually working on new training initiatives and updating our selection of how-to guides to facilitate getting more folks to try out FreeBSD. Check out some of our advocacy work: • Held a workshop and hosted a table at FOSSY, July 13-16, 2023, in Portland, Oregon. • Friend-level sponsor of COSCUP, July 27-29, 2023, in New Taipei, Taiwan • Presented at the EuroBSDCon FreeBSD Developer Summit, and sponsored and staffed a table at EuroBSDCon 2023, September 14-17, 2023 in Coimbra, Portugal • Attended the Open Source Summit, Europe, September 19-21, Bilbao, Spain • Continued planning the November 2023 FreeBSD Vendor Summit, taking place November 2-3, 2023, in San Jose, California • Continued to administer our Google Summer of Code program • Published the July Newsletter • Additional Blog Posts □ Advocating at Events: May 2023 FreeBSD Dev Summit and BSDCan □ Top Ten Reasons to Upgrade to FreeBSD 13.2 □ July 2023 Software Development Projects Update □ FreeBSD for Research: CHERI/Morello □ Meet the FreeBSD Google Summer of Code Students ☆ Soobin Rho ☆ Raghav Sharma ☆ Sudhanshu Mohan Kashyap ☆ Aymeric Wibo □ Meet The Summer 2023 University of Waterloo Co-Op Student: Naman Sood □ Meet FreeBSD Foundation 2023 Summer Intern: Jake Freeland • FreeBSD in the News □ FreeBSD Foundation Joins OSI’s Open Policy Alliance □ Hackernoon: 5 Reasons We Use Open Source FreeBSD as Our Enterprise OS □ What the Dev Podcast: The Evolution of the FreeBSD Project. We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal. As we mentioned previously, the FreeBSD Journal is now a free publication. Find out more and access the latest issues at https://www.freebsdfoundation.org/journal/. You can find out more about events we attended and upcoming events at https://freebsdfoundation.org/our-work/events/. OS Improvements During the third quarter of 2023, 282 src, 652 ports, and 24 doc tree commits identified The FreeBSD Foundation as a sponsor. Some of this Foundation-sponsored work is described in separate report entries: • Enabling Snapshots on Filesystems Using Journaled Soft Updates • Login Classes Fixes and Improvements • OpenSSL 3 in base — Improved • OpenStack on FreeBSD • Process Visibility Security Policies • SIMD enhancements for amd64. Members of the Technology Team attended EuroBSDCon 2023 in Coimbra, Portugal. Li-Wen Hsu gave a tutorial to help newcomers contribute to FreeBSD. Before the conference, the FreeBSD Developer Summit took place, where the team presented a short update on their recent work. Six summer internships or projects wrapped up. • Jake Freeland spent the summer working on a a Capsicum project to trace violations, adapt various daemons such as syslogd(8), and write documentation. • Naman Sood worked on various tasks, mostly related to networking. • En-Wei Wu completed another wireless internship to improve and extend wtap, the net80211(4) Wi-Fi simulator. • Yan-Hao Wang worked on a documentation and testing project to, e.g., build an online man page editor and add test cases for some userspace tools. • Christos Margiolis completed his project to improve the kinst DTrace provider by implementing inline function tracing and porting kinst to arm64 and riscv. • In preparation for FreeBSD 14.0, Muhammad Moinur (Moin) Rahman committed over 700 fixes or workarounds for ports affected by recent OpenSSL and LLVM updates. For more information about current and past Foundation-contracted work, visit the Foundation Projects page. Here is a sampling of other Foundation-sponsored work completed over the quarter: • Improved riscv64 CPU identity and feature detection • Rewrote intro(9) man page from scratch • Performed code maintenance and fixed bugs in the hwpmc(4) module and the pmc(3) library and tools • Committed various freebsd-update(8) fixes in preparation for FreeBSD 14.0 • Committed many (37) updates and fixes to the LinuxKPI, iwlwifi, and net802.11 code • Updated SSH first to OpenSSH 9.3p2, then 9.4p1 • Patched ssh-keygen to generate Ed25519 keys when invoked without arguments • Added a clean-room implementation of the Linux membarrier(2) system call • Increased MAXCPU to 1024 on amd64 and arm64 • Committed fixes for automatic Zenbleed misbehavior/data leaks prevention on affected machines (via chicken bit) • Reviewed the use of scheduling priorities throughout the kernel for work in progress to harden the rtprio() system call and make it more useful in some cases. Supporting FreeBSD Infrastructure The Foundation provides hardware and two staff members to help support the FreeBSD cluster. With your donations, the Foundation, in coordination with the Cluster Administration Team, purchased five new package builders, three new web servers, a new firewall/router, two package mirrors, and two new servers for continuous integration. With the exception of one of the package mirrors, all the new hardware will be located on the east coast of the USA. Continuous Integration and Quality Assurance The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project. You can read more about CI work in a dedicated report entry. Legal/FreeBSD IP The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them. We also provide legal support for the core team to investigate questions that arise. Go to https://freebsdfoundation.org to find more about how we support FreeBSD and how we can help you! ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Release Engineering Team Links: FreeBSD 14.0-RELEASE schedule URL: https://www.freebsd.org/releases/14.0R/ schedule/ FreeBSD releases URL: https://download.freebsd.org/releases/ISO-IMAGES/ FreeBSD development snapshots URL: https://download.freebsd.org/snapshots/ ISO-IMAGES/ Contact: FreeBSD Release Engineering Team, The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. During the third quarter of the year, the FreeBSD Release Engineering Team started work on the upcoming 14.0-RELEASE cycle. As of this writing, BETA3 had been released, with BETA4 to follow shortly after. The Release Engineering Team continued providing weekly development snapshot builds for the main and stable/13 branches. Sponsor: Tarsnap Sponsor: https://www.gofundme.com/f/gjbbsd/ Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Continuous Integration Links: FreeBSD Jenkins Instance URL: https://ci.FreeBSD.org FreeBSD CI Tinderbox view URL: https://https://tinderbox.freebsd.org FreeBSD CI artifact archive URL: https://artifact.ci.FreeBSD.org Hosted CI wiki URL: https://wiki.FreeBSD.org/HostedCI 3rd Party Software CI URL: https://wiki.FreeBSD.org/3rdPartySoftwareCI Tickets related to freebsd-testing@ URL: https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=open&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals FreeBSD CI Repository URL: https://github.com/freebsd/freebsd-ci dev-ci Mailing List URL: https://lists.FreeBSD.org/subscription/dev-ci Contact: Jenkins Admin Contact: Li-Wen Hsu Contact: freebsd-testing Mailing List Contact: IRC #freebsd-ci channel on EFNet In the third quarter of 2023, we worked with the project contributors and developers to address their testing requirements. Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD. Important completed tasks: • Add jobs for stable/14 branch • Update the "Tinderbox" view of the CI results, now includes test results and the "starting point" of the current failing or unstable series. • This is mainly done by the Foundation intern, Yan-Hao Wang. His other contributions are in the other entry of this report. Work in progress tasks: • Designing and implementing pre-commit CI building and testing and pull/ merged-request based system (to support the workflow working group) • Proof of concept system is in progress. • Designing and implementing use of CI cluster to build release artifacts as release engineering does • Simplifying CI/test environment setting up for contributors and developers • Setting up the CI stage environment and putting the experimental jobs on it • Improving the hardware test lab and adding more hardware for testing • Merge https://reviews.freebsd.org/D38815 • Merge https://reviews.freebsd.org/D36257 Open or queued tasks: • Collecting and sorting CI tasks and ideas • Setting up public network access for the VM guest running tests • Implementing use of bare-metal hardware to run test suites • Adding drm ports building tests against -CURRENT • Planning to run ztest tests • Helping more software get FreeBSD support in its CI pipeline (Wiki pages: 3rdPartySoftwareCI, HostedCI) • Working with hosted CI providers to have better FreeBSD support Please see freebsd-testing@ related tickets for more WIP information, and do not hesitate to join the effort! Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Ports Collection Links: About FreeBSD Ports URL:https://www.FreeBSD.org/ports/ Contributing to Ports URL: https://docs.freebsd.org/en/articles/contributing/#ports-contributing FreeBSD Ports Monitoring URL: http://portsmon.freebsd.org/ Ports Management Team URL: https://www.freebsd.org/portmgr/ Ports Tarball URL: http://ftp.freebsd.org/pub/FreeBSD/ports/ports/ Contact: René Ladan Contact: FreeBSD Ports Management Team The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters. Below is what happened in the last quarter. • According to INDEX, there are currently 34,600 ports in the Ports Collection. There are currently 3,000 open ports PRs of which some 730 are unassigned. The last quarter saw 11,454 commits by 130 committers on the main branch and 828 commits by 37 committers on the 2023Q3 branch. Compared to last quarter, this means a slight decrease in the number of unassigned PRs, a 10% increase in the number of commits on the main branch but also less backports to the quarterly branch. The number of ports also grew a bit. During Q3 we welcomed Joel Bodenmann (jbo@) as a new ports committer, granted a ports commit bit to mizhka@ who was already a src committer, and took the commit bits of knu@ and uqs@ in for safe-keeping after a year of inactivity. Portgmr discussed and worked on the following things during Q3: • Some progress has been made on sub-packages and a lightning talk was given by pizzamig@ at EuroBSDCon • Overhauling some parts of the ports tree (LIB_DEPENDS, PREFIX, MANPREFIX, MANPATH) Support for FreeBSD 13.1 was removed from the ports tree as it reached its end-of-life on August 1st. The following happened on the infrastructure side: • USES for ebur128 and guile were added • Default versions for Mono, Perl, and PostgreSQL were updated to respectively 5.20, 5.34, and 15 • Default versions for ebur128, guile, and pycryptography were added at respectively "rust", 2.2, and "rust" • Updates to major ports that happened were: □ pkg to 1.20.7 □ chromium to 117.0.5938.132 □ Firefox to 118.0.1 □ KDE to 5.27.8 □ Rust to 1.72.0 □ Wine to 8.0.2 During the last quarter, pgkmgr@ ran 18 exp-runs to test various ports upgrades, updates to default versions of ports, and changes to pycryptography. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Projects Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects. Filling gaps in the FreeBSD desktop experience Links: External media manager URL: https://github.com/outpaddling/qmediamanager devd-based automounter URL: https://github.com/outpaddling/devd-mount SUID mount tool URL: https://github.com/outpaddling/npmount Popup notification for updates URL: https://github.com/outpaddling/ freebsd-update-notify Contact: Jason Bacon The sysutils/desktop-installer port, available for over a decade now, quickly configures a bare FreeBSD system with any desktop environment or window manager. However, the FreeBSD base and ports collection has been missing some common features that end users expect from a desktop OS. The desktop-installer battery monitor script has been enhanced to display popup notifications at various levels of charge/discharge. deskutils/qmediamanager, in conjunction with sysutils/devd-mount and sysutils/npmount, mounts inserted media upon notification from devd, and displays a popup window offering the user options to show filesystem information, open a file manager, reformat, copy a disk image to the device, or unmount. It provides a convenient and secure way to work with external media such as USB sticks. A fourth new port — deskutils/freebsd-update-notify — displays a popup when new base updates are available, or when a configurable time limit has elapsed. If the user chooses to proceed with updates, the entire system is updated (packages, ports, and base) with auto-update-system(1) (a feature of sysutils/auto-admin). These new tools bring the FreeBSD desktop experience a step closer to the convenience of the most popular desktop operating systems. The tools are effectively prototypes, stable and reliable, but in need of review. Feedback from users regarding default behavior and configuration options will be appreciated. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ LLDB Kernel Module Improvement Links: GSoC Wiki Project URL: https://wiki.freebsd.org/SummerOfCode2023Projects/LLDBKernelModuleImprovement Project Codebase URL: https://github.com/aokblast/freebsd-src/tree/lldb_dynamicloader_freebsd_kernel LLVM PullRequest URL: https://github.com/llvm/llvm-project/pull/67106 Contact: Sheng-Yi Hong The LLDB Kernel Module Improvement Project described in the previous quarter report implements DynamicLoader Plugin for FreeBSD Kernel on LLDB. All of the work is done — that is, this plugin can correctly load all kernel modules and their debug files extracted from kernel coredump. This plugin has been tested on both x86-64 for relocatable type kernel module and arm64(EC2) for shared library type kernel module. Both of these platforms show this plugin works well. Currently, this plugin prepares to be landed to LLVM codebase in LLVM PullRequest Sponsor: The Google Summer of Code '23 program ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Userland Changes affecting the base system and programs in it. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ OpenSSL 3 in base — Improved Links: OpenSSL Downloads URL: https://www.openssl.org/source/ Contact: Pierre Pronchery This is a follow-up to the previous quarterly report on the integration of OpenSSL 3 into the base system. The most obvious updates since the previous report are certainly the 3.0.10 and then 3.0.11 releases, fixing CVE issues with low to medium severity ( CVE-2023-2975, CVE-2023-3446, CVE-2023-3817, CVE-2023-4807). However these are not the only changes, and this quarter some issues specific to the integration were fixed, most of which were found while building ports with OpenSSL 3 in the base system. Fixes included: • Linking the engines and the legacy provider with the libcrypto.so shared object, for proper visibility of symbols, and for which a hack was required in the build system. • Correcting the list of source files for the FIPS provider. • Ensuring backward compatibility for the deprecated 0.9.8 API, which was notably helpful for the PAM authentication module from security/ pam_ssh_agent_auth, based on OpenSSH’s ssh-agent(1) authentication mechanism. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Login Classes Fixes and Improvements Links: Start of the reviews stack URL: https://reviews.freebsd.org/D40339 Contact: Olivier Certner Context Login classes are a mechanism mainly used to set various process properties and attributes at login, depending on the user logging in and the login class he is a member of. A login class typically specifies resource limits, environment variables and process properties such as scheduling priority and umask. See login.conf(5) for more information. Changes The priority and umask capabilities now accept the inherit special value to explicitly request property inheritance from the login process. This is useful, e.g., when temporarily logging in as another user from a process with a non-default priority to ensure that processes launched by this user still have the same priority level. Users can now override the global setting for the priority capability (in /etc/ login.conf) in their local configuration file (~/.login_conf). Note however that they cannot increase their priority if they are not privileged, and that using inherit in this context makes no sense, since the global setting is always applied first. Fixes: • Fix a bug where, when the priority capability specifies a realtime priority, the final priority used was off-by-one (and the numerically highest priority in the real time class (31) could never be set). • Security: Prevent a setuid/setgid process from applying directives from some user’s ~/.login_conf (directives there that cannot be applied because of a lack of privileges could suddenly become applicable in such a process). We have also updated the relevant manual pages to reflect the new functionality, and improved the description of the priority and umask capabilities in login.conf(5). Status Some of the patches in the series have been reviewed thanks to Konstantin Belousov and Warner Losh. Other patches are waiting for reviews (and reviewers, volunteers welcome!), which are not expected to be labored. We plan to improve consistency by deprecating the priority reset to 0 when no value for the capability priority is explicitly specified, which has been the case for umask for 15+ years. Sponsor: Kumacom SAS (for development work) Sponsor: The FreeBSD Foundation (for some reviews) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Process Visibility Security Policies Links: Start of the reviews stack URL: https://reviews.freebsd.org/D40626 Contact: Olivier Certner Context FreeBSD implements three built-in security policies that limit which processes are visible to particular users, with the goal of preventing information leaks and unwanted interactions. The first one can prevent an unprivileged user from seeing or interacting with processes that do not have the user’s UID as their real UID. It can be activated by setting the sysctl security.bsd.see_other_uids to 0 (default is 1). The second one can prevent an unprivileged user from seeing or interacting with processes whose credentials do not have any group that the user is a member of. It can be activated by setting the sysctl security.bsd.see_other_gids to 0 (default is 1). The third one can prevent an unprivileged user’s process from seeing or interacting with processes that are in a jail that is a strict sub-jail of the former. The jail subsystem already prevents such a process to see processes in jails that are not descendant of its own (see jail(8) and in particular the section "Hierarchical Jails"). One possible use of this policy is, in conjunction with the first one above, to hide processes in sub-jails that have the same real UID as some user in an ancestor jail, because users having identical UIDs in these different jails are logically considered as different users. It can be activated by setting the sysctl security.bsd.see_jail_proc to 0 (default is 1). After a review of these policies' code and real world testing, we noticed a number of problems and limitations which prompted us to work on this topic. Changes The policy controlled by the security.bsd.see_jail_proc sysctl has received the following fixes and improvements: • Harden the security.bsd.see_jail_proc policy by preventing unauthorized users from attempting to kill, change priority of or debug processes with same (real) UID in a sub-jail at random, which, provided the PID of such a process is guessed correctly, would succeed even if these processes are not visible to them. • Make this policy overridable by MAC policies, as are the others. The policy controlled by security.bsd.see_other_gids was fixed to consider the real group of a process instead of its effective group when determining whether the user trying to access the process is a member of one of the process' groups. The rationale is that some user should continue to see processes it has launched even when they acquire further privileges by virtue of the setgid bit. Conversely, they should not see processes launched by a privileged user that temporarily enters the user’s primary group. This new behavior is consistent with what security.bsd.see_other_uids has always been doing for user IDs (i.e., considering some process' real user ID and not the effective ID). We have updated manual pages related to these security policies, including security(7), sysctl(8), and ptrace(2). Several manual pages of internal functions either implementing or leveraging these policies have also been revamped. Status Thanks to the help of Mitchell Horne, Pau Amma, Benedict Reuschling and Ed Maste, most of the submitted changes have been reviewed and approved, so they should reach the tree soon. The patch series starts with review D40626. From there, click on the "Stack" tab to see the full list of reviews implementing the changes. As a later step, we are considering turning the security.bsd.see_jail_proc policy on by default (i.e., the default value of the sysctl would become 0) unless there are objections. Sponsor: Kumacom SAS (for development work) Sponsor: The FreeBSD Foundation (for most of the reviews) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Linux compatibility layer update Links: Linuxulator status Wiki page URL: https://wiki.freebsd.org/Linuxulator Linux app status Wiki page URL: https://wiki.freebsd.org/LinuxApps Contact: Dmitry Chagin The goal of this project is to improve FreeBSD’s ability to execute unmodified linux(4) binaries. As of 22dca7acf775, xattr system calls are implemented. That makes it possible to use Linux rsync. As of bbe017e0415a, ioprio system calls are implemented. That makes it possible to debootstrap Ubuntu 23.04. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Kernel Updates to kernel subsystems/features, driver support, filesystems, and more. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Enabling Snapshots on Filesystems Using Journaled Soft Updates Contact: Marshall Kirk McKusick This project has made UFS/FFS filesystem snapshots available when running with journaled soft updates. The details of this project were described in the 2022 fourth quarter report. This project had two milestones: The first milestone of this project was to make it possible to take snapshots when running with journaled soft updates and to use them for doing background dumps on a live filesystem. Background dumps are requested by using the -L flag to dump(8). This milestone was completed in Q4 of 2022 and was made available in the 13.2 release as described in the 2023 first quarter report. The second milestone of this project was to do a background check using a snapshot on a filesystem running with journaled soft updates. This milestone was completed in the third quarter of 2023 in time to be included as part of the 14.0 release. It was also made available in the 13.2-STABLE release. Sponsored by: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SquashFS driver for FreeBSD kernel Links: Wiki page URL: https://wiki.freebsd.org/SummerOfCode2023Projects/PortSquashFuseToTheFreeBSDKernel Source code URL: https://github.com/Mashijams/freebsd-src/tree/gsoc/testing Contact: Raghav Sharma This quarter we finished SquashFS driver work for the kernel. We now can mount SquashFS archives on FreeBSD 13.2-RELEASE or greater, and perform all basic read-only filesystem operations. Code work includes: • Implementing vop_lookup() and vop_readdir() hooks for directory read support. • Implementing vop_read() and vop_strategy() hooks for files read support. • Implementing vop_readlink() hook for symlinks read support. We also implemented extended attributes interface functions for SquashFS. All that remains is to implement their kernel interface hooks. There were a lot of bug fixes as well. One major issue was to find out why we can not list the first entry of the root directory, it transpires that SquashFS could have inode_number as zero, which the kernel, for some reason, skips while listing dirents. For now, we fixed it by passing dummy inode_number, instead of zero, to dirent. The code review is currently ongoing with my mentor Chuck Tuffli. I am happy to say that SquashFS will find its place in upcoming FreeBSD releases. Sponsor: The Google Summer of Code 2023 program ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Architectures Updating platform-specific features and bringing in support for new hardware platforms. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ NXP DPAA2 support Links: DPAA2 in the FreeBSD source tree URL: https://cgit.freebsd.org/src/tree/sys/dev/dpaa2 DPAA2 on Github URL: https://github.com/mcusim/freebsd-src Contact: Dmitry Salychev Contact: Bjoern A. Zeeb What is DPAA2? DPAA2 is a hardware-level networking architecture found in some NXP SoCs which contains hardware blocks including Management Complex (MC, a command interface to manipulate DPAA2 objects), Wire Rate I/O processor (WRIOP, packets distribution, queuing, drop decisions), Queues and Buffers Manager (QBMan, Rx/ Tx queues control, Rx buffer pools) and others. The Management Complex runs NXP-supplied firmware which provides DPAA2 objects as an abstraction layer over those blocks to simplify access to the underlying hardware. Changes from the previous report • Isolation between DPAA2 channels improved. • Panic under heavy network load fixed. • FDT/ACPI MDIO support. • NFS root mount do not hang on netboot over DPAA2 anymore. • Drivers started to communicate with MC via their own command portals (DPMCP). • List of all closed issues. Work in Progress Work on dev/sff started to support SFF/SFP modules in order to test DPAA2 drivers on links above 1 Gbit/s. Plan • Heavy network load tests (2.5 Gbit/s, 10 Gbit/s) and bottlenecks mitigation. • Cached memory-backed software portals. • Driver resources de-allocation to unload dpaa2.ko properly. • Further parts (DPSW, DCE, etc.) supported by the hardware. Sponsor: Traverse Technologies (providing Ten64 HW for testing) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SIMD enhancements for amd64 Links: Project proposal URL: http://fuz.su/~fuz/freebsd/2023-04-05_libc-proposal.txt simd(7) URL: https://man.freebsd.org/cgi/man.cgi?query=simd&sektion=7&manpath=FreeBSD+15.0-CURRENT Contact: Robert Clausecker SIMD instruction set extensions such as SSE, AVX, and NEON are ubiquitous on modern computers and offer performance advantages for many applications. The goal of this project is to provide SIMD-enhanced versions of common libc functions (mostly those described in string(3)), speeding up most C programs. For each function optimised, up to four implementations will be provided: • a scalar implementation optimised for amd64, but without any SIMD usage, • either a baseline implementation using SSE and SSE2, or an x86-64-v2 implementation using all SSE extensions up to SSE4.2, • an x86-64-v3 implementation using AVX and AVX2, and • an x86-64-v4 implementation using AVX-512F/BW/CD/DQ. Users will be able to select which level of SIMD enhancements to use by setting the ARCHLEVEL environment variable. While the current project only concerns amd64, the work may be expanded to other architectures like arm64 in the future. During the last few months, significant progress has been made on this project. SIMD-enhanced versions of bcmp(3), index(3), memchr(3), memcmp(3), stpcpy(3), strchr(3), strchrnul(3), strcpy(3), strcspn(3), strlen(3), strnlen(3), and strspn(3) have landed. Functions memcpy(3), memmove(3), strcmp(3), timingsafe_bcmp(3) (see D41673), and timingsafe_memcmp(3) (see D41696) are work in progress. Unfortunately, the work has not made the cut for FreeBSD 14.0, but it is slated to be part of FreeBSD 14.1. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Integrate mfsBSD into the Release Building Tools Links: Wiki Article URL: https://wiki.freebsd.org/SummerOfCode2023Projects/IntegrateMfsBSDIntoTheReleaseBuildingTools Code Review on Phabricator URL: https://reviews.freebsd.org/D41705 FreeBSD Foundation Blog Post URL: https://freebsdfoundation.org/blog/meet-the-2023-freebsd-google-summer-of-code-students-soobin-rho/ Contact: Soobin Rho What is mfsBSD? "mfsBSD is a toolset to create small-sized but full-featured mfsroot based distributions of FreeBSD that store all files in memory (MFS) [Memory File System] and load from hard drive, USB storage device, or optical medium. It can be used for a variety of purposes, including diskless systems, recovery partitions and remotely overwriting other operating systems." Martin Matuška is the creator of mfsBSD. He is also author of the original (2009) mfsBSD white paper, from which the excerpt above is taken. Upstream mfsBSD is maintained in the repository on GitHub. Purpose of this Project This project integrates mfsBSD into the FreeBSD release tool set, creating an additional target of mfsBSD images (.img and .iso files) in /usr/src/release/ Makefile. Prior to integration, mfsBSD only existed outside the FreeBSD release tool chain, and only -RELEASE versions were produced. With this project, mfsBSD images will be available at the official FreeBSD release page. You will also be able to build mfsBSD yourself by invoking cd / usr/src/release && make release WITH_MFSBSD=1, which will then create mfsbsd-se.img and mfsbsd-se.iso at /usr/obj/usr/src/${ARCH}/release/. Changes from last quarter The code is ready, and is currently under review. If you would like to get involved with the review process, please feel free to do so! Here is my revision. Sponsor: Google, Inc. (GSoC 2023) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Cloud Updating cloud-specific features and bringing in support for new cloud platforms. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ OpenStack on FreeBSD Links: OpenStack URL: https://www.openstack.org/ OpenStack on FreeBSD URL: https://github.com/openstack-on-freebsd Contact: Chih-Hsin Chang Contact: Li-Wen Hsu OpenStack, an open-source cloud operating system, has been a valuable resource for deploying various resource types on cloud platforms. However, the challenge has been running OpenStack’s control plane on FreeBSD hosts. Our project’s mission is to enable FreeBSD to function seamlessly as an OpenStack host. Throughout this quarter, we focused on the last bit of the entire proof of concept (POC), the VM console integration. The goal is to let users get serial consoles via the OpenStack client to access the VM instances running on the FreeBSD-based OpenStack cluster. This is also important because right now we do not have a port for the managed DHCP service in Neutron. Users need to manually configure the correct IP addresses for the VM instances to have network connectivity. However, bhyve(8) does not natively expose serial consoles, so we need to instead export the nmdm(4) device over the network. This is done by a custom proxy called socat-manager, and yes, we leverage socat(1) to listen on specific ports allocated by OpenStack nova-compute to be integrated into their workflow. With the aid of another critical part, the custom Libvirt hook for bhyve, we can connect the two endpoints and make the consoles accessible to the users. During development of the hook script, we found that the hook interface provided by Libvirt specifically for bhyve was not well implemented. Fortunately, the Libvirt developer fixed the issue promptly, and we plan to refine our hook script when the fix is released in the future. We also addressed the nested bhyve issue (running bhyve VMs on top of Linux KVM) in our development environment mentioned in the last quarterly report. It is caused by the APIC emulation of the two VT-x features: VID and PostIntr. Our host’s CPUs have these two features so we need to disable them at the L1 guest, which acts as a bhyve host, in /boot/loader.conf to make L2 guests not hanging. It is crucial for us to be able to work on the project in a fully virtualized environment due to the lack of physical resources. This could be equally important for people interested in the project, lowering the bar for them to try out or validate the entire POC on their environment without too demanding setup requirements. Looking ahead to Q4, our focus is wrapping up the POC with revised documentation and porting to FreeBSD 14.0-RELEASE. Dependencies that lack the corresponding FreeBSD packages will be ported one by one. We also aim to rebase our work with OpenStack 2023.1 Antelope. We invite those interested to explore our documentation and contribute to this project’s success. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD on Microsoft HyperV and Azure Links: Microsoft Azure article on FreeBSD wiki URL: https://wiki.freebsd.org/ MicrosoftAzure Microsoft HyperV article on FreeBSD wiki URL: https://wiki.freebsd.org/HyperV Contact: Microsoft FreeBSD Integration Services Team Contact: freebsd-cloud Mailing List Contact: The FreeBSD Azure Release Engineering Team Contact: Wei Hu Contact: Souradeep Chakrabarti Contact: Li-Wen Hsu In this quarter, we have worked mainly on ARM64 architecture support and building and publishing both UFS and ZFS based images to Azure community gallery. There are some testing images available in the project’s testing public gallery, named FreeBSDCGTest-d8a43fa5-745a-4910-9f71-0c9da2ac22bf: • FreeBSD-CURRENT-testing • FreeBSD-CURRENT-gen2-testing • FreeBSD-CURRENT-arm64-testing • FreeBSD-CURRENT-zfs-testing • FreeBSD-CURRENT-zfs-gen1-testing To use them, when creating a virtual machine: 1. In Select an Image step, choose Community Images in Other items 2. Search FreeBSD We are aiming to provide all those images for 14.0-RELEASE. Work in progress tasks: • Automating the image building and publishing process and merge to src/ release/. • Building and publishing all supported VM images to Azure Marketplace • Building and publishing snapshot builds to Azure community gallery The above tasks are sponsored by The FreeBSD Foundation, with resources provided by Microsoft. Wei Hu and Souradeep Chakrabarti have fixed several critical bugs in arm64: • https://bugs.freebsd.org/267654 • https://bugs.freebsd.org/272461 • https://bugs.freebsd.org/272666 The root cause was identified and fixed in e7a9817b8d32: Hyper-V: vmbus: implementat bus_get_dma_tag in vmbus And continue working on improving Microsoft Azure Network Adapter (MANA) support. Open tasks: • Update FreeBSD related doc at Microsoft Learn • Support FreeBSD in Azure Pipelines • Update Azure agent port to the latest version • Upstream local modifications of Azure agent Sponsor: Microsoft for people in Microsoft, and for resources for the rest Sponsor: The FreeBSD Foundation for everything else ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD on EC2 Links: FreeBSD/EC2 Patreon URL: https://www.patreon.com/cperciva Contact: Colin Percival FreeBSD is available on both x86 (Intel and AMD) and ARM64 (Graviton) EC2 instances. Work continues to ensure that upcoming instance types will be supported. Weekly FreeBSD snapshots now include experimental ZFS-root AMIs for 14.0 and 15.0. This change will be present in FreeBSD 14.0-RELEASE. Work is underway to start publishing experimental "cloud-init" AMIs. This is expected to arrive in time for FreeBSD 14.0-RELEASE. This work is supported by Colin’s FreeBSD/EC2 Patreon. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Documentation Noteworthy changes in the documentation tree, manual pages, or new external books/documents. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Documentation Engineering Team Link: FreeBSD Documentation Project URL: https://www.freebsd.org/docproj/ Link: FreeBSD Documentation Project Primer for New Contributors URL: https://docs.freebsd.org/en/books/fdp-primer/ Link: Documentation Engineering Team URL: https://www.freebsd.org/administration/#t-doceng Contact: FreeBSD Doceng Team The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see the FreeBSD Doceng Team Charter. During this quarter: • The search functionality of the documentation portal was moved from DuckDuckGo to our own search engine; for more information, see this commit • grahamperrin@'s doc commit bit was taken for safekeeping as per his request • pluknet@'s doc commit bit was taken for safekeeping as per his request. Porter’s Handbook New USES knobs have been added to the Handbook: • USES= ebur128. • USES= guile. FreeBSD Translations on Weblate Link: Translate FreeBSD on Weblate URL: https://wiki.freebsd.org/Doc/Translation/Weblate Link: FreeBSD Weblate Instance URL: https://translate-dev.freebsd.org/ Q3 2023 Status • 17 team languages • 189 registered users Four new translators joined Weblate: • minso in Korean (ko) and French (fr_FR) • strgalt-t in German (de_DE) • bsdmeg in German (de_DE) • mvsf in Portuguese (pt_BR) Languages • Chinese (Simplified) (zh-cn) (progress: 7%) • Chinese (Traditional) (zh-tw) (progress: 3%) • Dutch (nl) (progress: 1%) • French (fr) (progress: 1%) • German (de) (progress: 1%) • Indonesian (id) (progress: 1%) • Italian (it) (progress: 5%) • Korean (ko) (progress: 33%) • Norwegian (nb-no) (progress: 1%) • Persian (fa-ir) (progress: 2%) • Polish (progress: 1%) • Portuguese (progress: 0%) • Portuguese (pt-br) (progress: 22%) • Spanish (es) (progress: 35%) • Turkish (tr) (progress: 2%) We want to thank everyone that contributed, translating or reviewing documents. And please, help promote this effort on your local user group, we always need more volunteers. FreeBSD Handbook Working Group Contact: Sergio Carlavilla • The Network chapter has been rewritten • The Jails chapter has been rewritten • The next section to work on will be the file systems part: UFS, OpenZFS, Other File Systems. FAQ Working Group Contact: Sergio Carlavilla The idea is to write a new FAQ. Will be released alongside FreeBSD 14.0. FreeBSD Website Revamp — WebApps Working Group Contact: Sergio Carlavilla Working group in charge of creating the new FreeBSD Documentation Portal and redesigning the FreeBSD main website and its components. FreeBSD developers can follow and join the working group on the FreeBSD Slack channel #wg-www21. The work will be divided into three phases: 1. Redesign of the Manual Pages on web Scripts to generate the HTML pages using mandoc. (Complete, Approved by Doceng, Deploy Date Not Decided Yet) Public instance on https://man-dev.FreeBSD.org 2. Redesign of the FreeBSD main website New design, responsive and dark theme. (Almost Complete, Presented at EuroBSDCon) 3. Redesign of the Ports page on web Ports scripts to create an applications portal. (Work in progress) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Online Editor and Man Page Editor Links: FreeBSD Online Document Editor URL: https://github.com/Wang-Yan-Hao/ FreeBSD-Online-Document-Editor FreeBSD Online Man Page Editor URL: https://github.com/Wang-Yan-Hao/ man_page_editor Contact: Yan-Hao Wang Contact: Li-Wen Hsu Currently, our document translation process involves using Weblate and direct editing of the doc repository. We acknowledge that this process can be somewhat cumbersome, so we are striving to offer a more convenient alternative, similar to what the wiki community does. Introducing the Online Document Editor and Man Page Editor, a user-friendly, WYSIWYG static site designed for translating documents and man pages. Our goal is to consolidate all translation functions within a single platform, making the translation process as straightforward as possible. However, we still require assistance with these two projects, as follows: 1. The Document editor and Man page editor were developed using simple JavaScript. We are seeking a web developer to assess the code’s efficiency since I (Yan-Hao Wang) am not well-versed in front-end development. 2. We are also seeking a cybersecurity developer to assist us in identifying and addressing security issues within these two projects. This is crucial to ensure the secure hosting of these projects and mitigate any potential vulnerabilities. 3. As there is currently no existing JavaScript library to render mandoc, I had to create my own. However, there are still some concealed errors during the editing process. We are in need of a JavaScript developer to help rectify these rendering issues. Sponsor: FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Expert System Links: FreeBSD Expert System URL: https://github.com/Wang-Yan-Hao/ freebsd_expert_system Contact: Yan-Hao Wang Contact: Li-Wen Hsu Machine Learning and Deep Learning technologies have become increasingly prevalent in today’s world, much like the proliferation of ChatGPT. We are working on developing a ChatGPT plugin that can access the latest FreeBSD data, transforming ChatGPT into a FreeBSD expert system. We have already scripted data cleaning and built an embedded model to search for relevant information. Nevertheless, we require assistance for the following aspect of this project: • While I am not an expert in Machine Learning or Deep Learning, we encounter numerous challenges in these domains, such as the adequacy of data cleaning and uncertainties in the final plugin development process. We would appreciate guidance in this regard. Sponsor: FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Ports Changes affecting the Ports Collection, whether sweeping changes that touch most of the tree, or individual ports themselves. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ KDE on FreeBSD Links: KDE/FreeBSD initiative URL: https://freebsd.kde.org/ FreeBSD — KDE Community Wiki URL: https://community.kde.org/FreeBSD Contact: Adriaan de Groot The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree. The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine. The KDE team (kde@) is part of desktop@ and x11@, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphical desktop workstation. The notes below describe mostly ports for KDE, but also include items that are important for the entire desktop stack. Infrastructure Qt5 is now on long-term support and updates only rarely. There was an update to 5.15.10 in this quarter. Qt6 is now updated with the regular upstream releases, with the 6.5.2 release landing at the end of July and 6.5.3 following later. CMake saw no updates this quarter, so we are now lagging by at least one minor release. The changelog for the latest releases does not have much for FreeBSD, so there is no special reason to upgrade. sysutils/polkit and sysutils/consolekit2 were both updated, bringing improved security policy and console handling to the FreeBSD desktop. x11/sddm was updated to provide a better graphical login manager. multimedia/pipewire was updated to version 0.3.81. This provides multimedia support for desktops such as KDE and GNOME. KDE Stack KDE Gear releases happen every quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release every month as well. These (large) updates land shortly after their upstream release and are not listed separately. • KDE Frameworks reached version 5.110. The KDE Frameworks 5 series is winding down, although it will be six months or so before it enters long-term support upstream. • KDE Plasma Desktop was updated to version 5.27.8. Just like frameworks, work on KDE Plasma 5 is winding down upstream in favor of KDE Plasma 6. • KDE Gear updated to 23.08.1. Related Ports The KDE ecosystem includes a wide range of ports — most maintained by kde@, all building on a shared base of Qt and KDE Frameworks. The kde@ team updates them all as needed. This quarter, for instance, tcberner@ and arrowd@ updated or fixed (much more than) this selection of ports: • astro/merkaartor • devel/massif-visualizer • finance/alkimia • irc/quassel • net-im/kaidan • sysutils/bsdisks • sysutils/k3b Thanks to jhale@, devel/qtcreator was updated to 11.0.3, providing another featureful integrated development environment for creating Qt and KDE applications. Deprecations Web browsers are huge, and have a considerable security surface. The venerable www/qt5-webkit WebKit port has been slated for removal and consumers have been moved to WebEngine. The fork of WebKit that we relied on is no longer actively maintained. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Pantheon desktop on FreeBSD Links: elementary OS URL: https://elementary.io/ Development repository URL: https://codeberg.org/olivierd/ freebsd-ports-elementary Contact: Olivier Duchateau The Pantheon desktop environment is designed for elementary OS. It builds on GNOME technologies (such as Mutter, GTK 3 and 4) and it is written in Vala. The goal is to have a complete desktop environment for end users. 13.2-RELEASE or higher is required, because several core components depend on deskutils/xdg-desktop-portal. The repository contains a file called elementary.mk for the Mk/Uses framework, official applications, and curated ports which depend on x11-toolkits/granite7. I have submitted several patches in order to keep these ports up-to-date: • deskutils/iconbrowser • multimedia/elementary-videos • x11-themes/gnome-icons-elementary • editors/elementary-code The bug reports for updating the following ports are still open on bugzilla: • x11-toolkits/granite7: Update to 7.3.0 • deskutils/elementary-calendar: Update to 7.0.0 • x11/elementary-terminal: Update to 6.1.2 In the same time, I have also worked on updating the GNOME stack (especially WebKitGTK, libwnck, Mutter, Vala). I noticed several regressions particularly with x11/plank (it is related to monitoring open applications). Three new applications have been added to the development repository: • deskutils/atlas, a map viewer • deskutils/nimbus, a weather applet • audio/leopod, podcasts client ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Office Team Links: The FreeBSD Office project URL: https://wiki.freebsd.org/Office The FreeBSD Office mailing list URL: https://lists.freebsd.org/subscription/freebsd-office Contact: FreeBSD Office team ML Contact: Dima Panov Contact: Li-Wen Hsu The FreeBSD Office team works on a number of office-related software suites and tools such as OpenOffice and LibreOffice. Work during this quarter was focused on providing the latest stable release of LibreOffice suite and companion apps to all FreeBSD users. During the 2023Q3 period we pushed maintenance patches for the LibreOffice port and brought the latest, 7.6.2, release and all companion libraries such as MDDS, libIxion and more to the ports tree. All prerelease development of LibreOffice ports is carried out in the in LibreOffice WIP repo. Together with LibreOffice, we also updated Boost to the latest, 1.83 release. Everyone interested in Boost porting can submit patches to the Boost WIP repository. We are looking for people to help with the open tasks: • The open bugs list contains all filed issues which need some attention • Upstream local patches in ports Patches, comments and objections are always welcome in the mailing list and Bugzilla. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Wifibox: Use Linux to Drive your Wireless Card on FreeBSD Links: Project GitHub Page URL: https://github.com/pgj/freebsd-wifibox net/wifibox port URL: https://cgit.freebsd.org/ports/tree/net/wifibox Contact: PÁLI Gábor János Wifibox is an experimental project for exploring the ways of deploying a virtualized Linux guest to drive wireless networking cards on the FreeBSD host system. There have been guides to describe how to set this up manually, and Wifibox aims to implement those ideas as a single easy-to-use software package. • It uses bhyve(8) to run the embedded Linux system. This helps to achieve low resource footprint. It requires an x64 CPU with I/O MMU (AMD-Vi, Intel VT-d), ~150 MB physical memory, and some disk space available for the guest virtual disk image, which can be even ~30 MB only in certain cases. It works with FreeBSD 12 and later, some cards may require FreeBSD 13 though. • The guest is constructed using Alpine Linux, a security-oriented, lightweight distribution based on musl libc and BusyBox, with some custom extensions and patches imported from Arch Linux most notably. It is shipped with a number of diagnostic tools for better management of the hardware in use. The recent version features Linux 6.1, but Linux 6.5 is also available as an alternative. • Configuration files are shared with the host system. The guest uses wpa_supplicant(8) or hostapd(8) (depending on the configuration) so it is possible to import the host’s wpa_supplicant.conf(5) or hostapd.conf(5) file without any changes. • When configured, wpa_supplicant(8) and hostapd(8) control sockets could be exposed by the guest, which enables use of related utilities directly from the host, such as wpa_cli(8) or wpa_gui(8) from the net/wpa_supplicant_gui package, or hostapd_cli(8). • Everything is shipped in a single package that can be easily installed and removed. This comes with an rc(8) system service that automatically launches the guest on boot and stops it on shutdown. • It can be configured to forward IPv6 traffic, which is currently an experimental option but turned on by default. Wifibox has been mainly tested with Intel chipsets, and it has shown great performance and stability. Therefore, it might serve as an interim solution whilst FreeBSD matures its support for these chipsets. It was confirmed that Wifibox works with Atheros, Realtek, and Mediatek chipsets too, and feedback is more than welcome about others. Broadcom chips (that are often found in MacBook Pros) can also work, but there are known stability issues. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ GCC on FreeBSD Links: GCC Project URL: https://gcc.gnu.org/ GCC 10 release series URL: https://gcc.gnu.org/gcc-10/ GCC 11 release series URL: https://gcc.gnu.org/gcc-11/ GCC 12 release series URL: https://gcc.gnu.org/gcc-12/ GCC 13 release series URL: https://gcc.gnu.org/gcc-13/ Contact: Lorenzo Salvadore The process to update GCC default version to GCC 13 has started with an exp-run . Thanks to Antoine Brodin who ran the exp-run and to all other developers and ports maintainers involved. The same exp-run contains additional patches as anticipated in last quarterly status report. In particular, it contains patches to update • lang/gcc11 to version 11.4.0; • lang/gcc12 to version 12.3.0; • lang/gcc13 to version 13.2.0. The reader might remember that I had planned to update GCC default version to GCC 13 as soon as 13.1.0 was out, but as it can be noted the GCC developers were faster to release 13.2.0 than I was working on the GCC ports. Most of the bugs reported in the exp-run are due to the same error: error: expected identifier before '__is_convertible'. It seems that the issue is an incompatibility between FreeBSD 12’s libcxx and GCC 13 headers. Please check the discussion in the exp-run for more information and to provide your feedback. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Valgrind: valgrind-devel updated for FreeBSD 15 Links: Valgrind Home Page URL: https://www.valgrind.org/ Valgrind News URL: https://www.valgrind.org/docs/manual/dist.news.html Contact: Paul Floyd devel/valgrind-devel is in the process of being updated. This contains most of what will be in the official release of Valgrind 3.22 due out in October. memcheck has been enhanced with some more checks. It will now report usage of realloc with a size of zero. Such usage is not portable and is deprecated (C23 will make it Undefined Behaviour). memcheck now validates the values used for alignment and sized delete for memalign, posix_memalign, aligned_alloc and all aligned and sized overloads of operator new and operator delete. Reading DWARF debuginfo is now done in a lazy manner which can improve performance. As usual there are numerous small bugfixes. Specific to FreeBSD there is now support for FreeBSD 15. Two extra _umtx_op operations are now supported, UMTX_OP_GET_MIN_TIMEOUT and UMTX_OP_SET_MIN_TIMEOUT. There is a fix for the use of sysctl kern proc pathname with the guest pid or -1, which previously returned the path of the Valgrind host. The sysctl will now return the path of the guest. Support for the close_range system call has been added. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ GitLab 16.3 Available Link: Gitlab 16.3 New Features URL: https://about.gitlab.com/releases/2023/08/22/gitlab-16-3-released/ Contact: Matthias Fechner GitLab is a DevOps platform. It brings velocity with confidence, security without sacrifice, and visibility into DevOps success. Version 16.3 is now available on FreeBSD: please check the www/gitlab-ce port. The upgrade is very important as version 16.3 will be required for all further upgrades. Upgrade to 16.4 is only possible from GitLab 16.3. Documentation for installation can be found at https://gitlab.fechner.net/ mfechner/Gitlab-docu/-/blob/master/install/16.3-freebsd.md?ref_type=heads. Documentation for upgrading is available at https://gitlab.fechner.net/mfechner /Gitlab-docu/-/blob/master/update/16.1-16.3-freebsd.md?ref_type=heads. I will wait for the upgrade to 16.4 (which will be released around 20.9. or 22.9., not sure) until ports quarterly branch 2023Q4 is created, to avoid breaking systems that do not use the main branch (latest). GitLab users should always choose the main branch, as described in the installation manual. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ PortOptsCLI — Ports Collection Accessibility Link: Project repository URL: https://gitlab.com/alfix/portoptscli Contact: Alfonso Sabato Siciliano Contact: FreeBSD Accessibility mailing list FreeBSD provides the Ports Collection to give users and administrators a simple way to install applications. It is possible to configure a port before the building and installation. The command make config uses ports-mgmt/dialog4ports and ports-mgmt/portconfig to set up a port interactively via a text user interface (TUI). Unfortunately, screen readers perform poorly with a TUI; it is a well-known accessibility problem. FreeBSD provides tens of thousands of ports; port configuration is a key feature, but it is inaccessible to users with vision impairment. PortOptsCLI (Port Options CLI) is a new utility for setting port options via a command line interface. Properly, PortOptsCLI provides commands to navigate configuration dialogues (checklists and/or radio buttons) and set up their items interactively. It is also suitable for a speech synthesizer; currently it is tested with accessibility/orca. PortOptsCLI can be installed via the ports-mgmt/portoptscli port or package. Tips and new ideas are welcome. If possible, send reports to the FreeBSD Accessibility mailing list, to share and to track discussions in a public place. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Third Party Projects Many projects build upon FreeBSD or incorporate components of FreeBSD into their project. As these projects may be of interest to the broader FreeBSD community, we sometimes include brief updates submitted by these projects in our quarterly report. The FreeBSD project makes no representation as to the accuracy or veracity of any claims in these submissions. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Introducing the BSD Cafe project Links: BSD Cafe project homepage URL: https://wiki.bsd.cafe/ BSD Cafe Mastodon instance URL: https://mastodon.bsd.cafe/ Contact: Stefano Marinelli We are thrilled to unveil the inaugural component of the BSD Cafe project! Months ago, when I first registered the bsd.cafe domain, I envisioned a themed bar where friends, acquaintances, and patrons could gather for casual conversations about *BSD systems, Linux, and open-source technology. Just like any bar, our discussions can encompass a wide array of topics, all while maintaining a spirit of mutual respect. BSD Cafe is poised to become a hub for a variety of tools and services, all powered by *BSD. Our initial offering is a brand-new instance of Mastodon (open-source microblogging software and service), serving as a gateway to the fediverse — a federation of services, many of which use the ActivityPub decentralised social networking protocol. Registration is now open. The server operates under clearly defined guidelines that promote positive conduct and unequivocally prohibit any form of hate. Inclusiveness, respect, and constructive dialogue stand as the cornerstones of this instance. Our primary server is currently hosted in Finland on a small VM, running on FreeBSD. Services are partitioned into VNET jails, interconnected within a local area network through a dedicated bridge. Additionally, we implement a VPN system and have the flexibility to migrate individual jails to more robust machines. For multimedia data and cache hosting, we employ a separate physical server (also FreeBSD-based, within a jail), fronted by Cloudflare. The goal here is to cache and geodistribute data, effectively reducing network congestion on the main VPS. Our reverse proxy (frontend), mail server, media server, and the instance itself are all accessible via IPv6. At its inception, this Mastodon instance was devoid of preloaded content. Our intention is for it to grow organically, based on the interests and followers of its users. At this stage, we have refrained from preemptive blocks. We strongly encourage users to promptly report anything that they believe requires attention. We invite you to join us at https://mastodon.bsd.cafe/ in order to cultivate a community that values constructive interactions and embraces inclusiveness — a secure and serene space meant for all. Furthermore, we have established a website at https://wiki.bsd.cafe/, which will provide an overview of our tools, services, rules, uptime, and more. Recently, a Miniflux installation has been performed, so the BSD Cafe users can use it as a personal RSS Feed Reader. More information: https://wiki.bsd.cafe/ miniflux-bsd-cafe. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Containers and FreeBSD: Pot, Potluck and Potman Links: Pot organization on GitHub URL: https://github.com/bsdpot Contact: Luca Pizzamiglio (Pot) Contact: Bretton Vine (Potluck) Contact: Michael Gmelin (Potman) Pot is a jail management tool that also supports orchestration through Nomad. During this quarter, Pot 0.15.6 was finished, adding custom pf(4) rule configuration hooks. Additionally, Nomad Pot Driver 0.9.1 that allows setting Pot attributes in Nomad job descriptions was released. Potluck aims to be to FreeBSD and Pot what Dockerhub is to Linux and Docker: a repository of Pot flavours and complete container images for usage with Pot and in many cases Nomad. Quite a few new container images were made available, e.g. a Caddy S3 proxy, a Mastodon instance, and a Redis container. In total there are now 50 containers available that can either be downloaded as ready-made images at the Potluck image registry, if you trust our build process, or that you can build yourself from the Pot flavour files stored in the Potluck GitHub repository. The July/August 2023 edition of the FreeBSD Journal contains Luca’s Jail Orchestration with pot and nomad article, explaining how to use Pot and Potluck together with Nomad to orchestrate containers on multiple hosts. Last but not least, a patch (90b1184d93c8) added build cluster support to the devel/sccache port. As always, feedback and patches are welcome. Sponsors: Nikulipe UAB, Honeyguide Group From nobody Wed Nov 1 19:37:26 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SLHMs14m0z4yw2G for ; Wed, 1 Nov 2023 19:37:29 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SLHMr6wLQz3Y4S; Wed, 1 Nov 2023 19:37:28 +0000 (UTC) (envelope-from bapt@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698867449; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=m20E5s4OT6AFpO8rFCOTROgwRgmZU28CN6UcYTyS5Ww=; b=JzI4wBVy1HmOeBHP+9rmij/QMzBC0jvFWL9EdTDCA9gBoAdbVwiDBtp67slK4u58okCjbE 13oWouCB57OI8XwNuH4TQlfdxOq1L6ah5amR+KWamlbbOscRTB2qjiuiSUubroMQ+nUfT2 UgP2P9ZZSSmspL1HofzHHl+Ev+AQ48I6kU/F2DWBd4TGQLPQU4IW2QixABo1iyUSzVxepW BUgC0yWE5bfZqToOQ8nSecFUzQpsAoQvXiYk6ilFLa7yf4ewYUHHZZGf59Ku3/3ycExEMF anqDQTJbs4Xa0y6bIfFEWLLmbeMxOFp9o5YtNiJCl0M8Dwtxn1rNfbIQf6ZvmQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698867449; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=m20E5s4OT6AFpO8rFCOTROgwRgmZU28CN6UcYTyS5Ww=; b=C2kytCARMB9u+QucaxZGD6IbjhMqaOe8LNi1ZUBUADveyIQIHcKhAcu2Y71uy62TQUPa8T 5Mz2cVduWdTKA9QY8Pisf0jgWimmbdYKRdhZeivz/RwqZsUdqcpfUhprngP/lR41WNDvSU CAGXS4gbZawOqEXSuk2ZN3ChYFkCL9iBilY/awrL01SebWAfzqssopiTKpJWqlpTUpYrb1 pSJ4sihvxnecXO6rP3TqIwti2sH+6ZtYI2Vfzc/tJFtEkwRWC1exRD1U4/1yCaIixSkn+z Knqh/Mc1vowU/T1x2PgrMcCUaPEGkzAvsUdBaUUGbTnrM2oQyvAY0522ofjRXg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1698867449; a=rsa-sha256; cv=none; b=ySXVSFJD1gtpFHdGq2rMVNdv8k5MmJWz0hZzISXxlO/V9JBkOgRaOR7EUdbhPUctqadIB0 xGzJP3zy+oA61YBoj+KmZ6SC09P1/qmLlMi4zlrbby6lj5iwpGhl/jQ5Kh3D4VVa0GT8+S vAdUu+PbbwrqOrISPBtG7M0oM6wjXQfhCInREWZFvEqV6EAj6eRuHYqW16ZOW+xG4rRFU0 GLDIyfpQazWxKVRwrrDDgB9CQHQm/ScNCwjn50DHSpUxnnBCLAKGgsa7ZR+b78O+9HGd0b RLgCOor4WQEbqyLWElEZzDAbJzB9tjZoS+f+nK0+ssLPtslXJ7RhLZ3a7+bFbw== Received: from aniel.nours.eu (nours.eu [176.31.115.77]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) (Authenticated sender: bapt) by smtp.freebsd.org (Postfix) with ESMTPSA id 4SLHMr5Kn2z1GMR; Wed, 1 Nov 2023 19:37:28 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: by aniel.nours.eu (Postfix, from userid 1001) id D91C711E485; Wed, 1 Nov 2023 20:37:26 +0100 (CET) Date: Wed, 1 Nov 2023 20:37:26 +0100 From: Baptiste Daroussin To: Jamie Landeg-Jones Cc: dickey@his.com, freebsd-current@freebsd.org Subject: Re: Freebsd 14+ -- tcsh incompatible with terminfo Message-ID: References: <202310312245.39VMjNJB080965@donotpassgo.dyslexicfish.net> <202310312259.39VMxm6W081150@donotpassgo.dyslexicfish.net> <202311010349.3A13nX1M094463@donotpassgo.dyslexicfish.net> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202311010349.3A13nX1M094463@donotpassgo.dyslexicfish.net> On Wed, Nov 01, 2023 at 03:49:33AM +0000, Jamie Landeg-Jones wrote: > Thomas Dickey wrote: > > > actually it probably does affect "xterm" > > > > Checking the source, tcsh is expecting a termcap string, while data read > > from the terminfo database is going to be in terminfo format -- even if > > read via tgetent/tgetstr > > > > tcsh is expecting a termcap string, and in its EchoTC function it duplicates > > the termcap version of what's tparm in a terminfo program. > > > > (tcsh could be modified readily to use terminfo for the case you're describing, > > but supporting $TERMCAP would be work) > > Hi Thomas, thanks for the reply... from the ncurses man himself! > > I *thought* I'd seen issues with just "xterm" but after posting the first > message, it seemed to start working, and so I doubted myself, but I must > have messed up somewhere! > > What threw me about tcsh is it does mention terminfo in the man page and > the source, so I wrongly assumed the problem wasn't there. > > Anyway, I'll raise it with the tcsh maintainers. > > To the FreeBSD release folk, I think it's great that we're moving off termcap, > but is there a chance that base tcsh could be compiled with a private version > of the terminfo-less ncurses in time for 14.0-RELEASE, if a proper fix to tcsh > is going to take too long? > > Thanks again, Thomas. > > Cheers, Jamie If you don't install (terminfo-db which nothing should pull in by default), then you are on the default behaviour which is termcap, this has been made like this on purpose, by default you have the behaviour you have always expected, and if you want another behaviour and larger support you install terminfo-db. The fact that tcsh does not play nicely with terminfo, is nother problem. Best regards, Bapt From nobody Wed Nov 1 22:02:47 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SLM4c2DBJz50C1y for ; Wed, 1 Nov 2023 22:24:32 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4SLM4c0BDSz4KBM; Wed, 1 Nov 2023 22:24:32 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Authentication-Results: mx1.freebsd.org; none Date: Wed, 01 Nov 2023 23:02:47 +0100 Author: Steffen Nurpmeso From: Steffen Nurpmeso To: Jamie Landeg-Jones Cc: dickey@his.com, freebsd-current@FreeBSD.org, bapt@FreeBSD.org Subject: Re: Freebsd 14+ -- tcsh incompatible with terminfo Message-ID: <20231101220247.HGrrB%steffen@sdaoden.eu> In-Reply-To: <202311010349.3A13nX1M094463@donotpassgo.dyslexicfish.net> References: <202310312245.39VMjNJB080965@donotpassgo.dyslexicfish.net> <202310312259.39VMxm6W081150@donotpassgo.dyslexicfish.net> <202311010349.3A13nX1M094463@donotpassgo.dyslexicfish.net> Mail-Followup-To: Jamie Landeg-Jones , dickey@his.com, freebsd-current@FreeBSD.org, bapt@FreeBSD.org User-Agent: s-nail v14.9.24-545-gbd87680ac8 OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15987, ipnet:217.144.128.0/20, country:DE] X-Rspamd-Queue-Id: 4SLM4c0BDSz4KBM List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Jamie Landeg-Jones wrote in <202311010349.3A13nX1M094463@donotpassgo.dyslexicfish.net>: |Thomas Dickey wrote: ... |To the FreeBSD release folk, I think it's great that we're moving off \ |termcap, Why? (That is to say: why -- if it is a *real* termcap? If it is only a translation layer to terminfo, i am with you. But otherwise not, i think a real termcap is much, much smaller, while offering anything a (simple) console program needs.) That is not to talk small the efforts of Mr. Dickey. But for example the mailer i maintain *can* directly use BSD termcap if so desired, and it works just nice. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) From nobody Thu Nov 2 00:25:37 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SLPmQ0L5cz4yRGQ for ; Thu, 2 Nov 2023 00:25:42 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4SLPmP4pB8z4Y39; Thu, 2 Nov 2023 00:25:41 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; none X-Catflap-Envelope-From: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 3A20Pcgg034164; Thu, 2 Nov 2023 00:25:38 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 3A20Pb3P034163; Thu, 2 Nov 2023 00:25:37 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202311020025.3A20Pb3P034163@donotpassgo.dyslexicfish.net> Date: Thu, 02 Nov 2023 00:25:37 +0000 Organization: Dyslexic Fish To: jamie@catflap.org, bapt@freebsd.org Cc: freebsd-current@freebsd.org, dickey@his.com Subject: Re: Freebsd 14+ -- tcsh incompatible with terminfo References: <202310312245.39VMjNJB080965@donotpassgo.dyslexicfish.net> <202310312259.39VMxm6W081150@donotpassgo.dyslexicfish.net> <202311010349.3A13nX1M094463@donotpassgo.dyslexicfish.net> In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Thu, 02 Nov 2023 00:25:38 +0000 (GMT) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US] X-Rspamd-Queue-Id: 4SLPmP4pB8z4Y39 Baptiste Daroussin wrote: > If you don't install (terminfo-db which nothing should pull in by default), then > you are on the default behaviour which is termcap, this has been made like this > on purpose, by default you have the behaviour you have always expected, and if > you want another behaviour and larger support you install terminfo-db. > > The fact that tcsh does not play nicely with terminfo, is nother problem. Thanks for the clarification. I had mistakingly thought many things pulled in terminfo-db, but it appears to be only deskutils/arttime that does so, so it's not as serious as I thought. As for tcsh, I'll work on getting it fixed upstream. Cheers, Jamie From nobody Thu Nov 2 02:41:04 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SLSmf4Dd9z4ygCr for ; Thu, 2 Nov 2023 02:41:06 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4SLSmf1Drlz3KHM; Thu, 2 Nov 2023 02:41:06 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; none X-Catflap-Envelope-From: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 3A22f49H042182; Thu, 2 Nov 2023 02:41:04 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 3A22f4o3042181; Thu, 2 Nov 2023 02:41:04 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202311020241.3A22f4o3042181@donotpassgo.dyslexicfish.net> Date: Thu, 02 Nov 2023 02:41:04 +0000 Organization: Dyslexic Fish To: steffen@sdaoden.eu, jamie@catflap.org Cc: freebsd-current@FreeBSD.org, dickey@his.com, bapt@FreeBSD.org Subject: Re: Freebsd 14+ -- tcsh incompatible with terminfo References: <202310312245.39VMjNJB080965@donotpassgo.dyslexicfish.net> <202310312259.39VMxm6W081150@donotpassgo.dyslexicfish.net> <202311010349.3A13nX1M094463@donotpassgo.dyslexicfish.net> <20231101220247.HGrrB%steffen@sdaoden.eu> In-Reply-To: <20231101220247.HGrrB%steffen@sdaoden.eu> User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Thu, 02 Nov 2023 02:41:04 +0000 (GMT) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US] X-Rspamd-Queue-Id: 4SLSmf1Drlz3KHM Steffen Nurpmeso wrote: > Why? > (That is to say: why -- if it is a *real* termcap? If it is only > a translation layer to terminfo, i am with you. But otherwise > not, i think a real termcap is much, much smaller, while offering > anything a (simple) console program needs.) > That is not to talk small the efforts of Mr. Dickey. But for > example the mailer i maintain *can* directly use BSD termcap if so > desired, and it works just nice. I agree that termcap does most of what we need already, so my main reason is that there are 2 different systems in use to do the same job, which is annoying. (FreeBSD doesn't exist in a vacuum) As terminfo exists, is supported, and has terminal entries that our termcap doesn't have, it seems to be better to switch to that. I'm sure it would mean less maintenance for the FreeBSD committers too. If terminfo didn't exist, I'd live with termcap. There are also benefits to terminfo: https://invisible-island.net/ncurses/ncurses.faq.html#extended_term We don't even run with a "proper" termcap anyway! "The base system's terminal database is referred to as “termcap.db” but is actually an ncurses terminfo hashed database." - https://invisible-island.net/ncurses/ncurses.faq.html#what_platforms So, yeah, despite Mr Dicky's success in making working with both as seamless as possible ,it would still just be nice to not have to deal with 2 different standards, that's all. "setaf or AF, that is the question." Cheers, Jamie From nobody Thu Nov 2 17:58:55 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SLtDX6f4Rz503k5 for ; Thu, 2 Nov 2023 18:48:12 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4SLtDW68YQz3YT0; Thu, 2 Nov 2023 18:48:11 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Authentication-Results: mx1.freebsd.org; none Date: Thu, 02 Nov 2023 18:58:55 +0100 Author: Steffen Nurpmeso From: Steffen Nurpmeso To: Jamie Landeg-Jones Cc: freebsd-current@FreeBSD.org, dickey@his.com, bapt@FreeBSD.org Subject: Re: Freebsd 14+ -- tcsh incompatible with terminfo Message-ID: <20231102175855.A1pj0%steffen@sdaoden.eu> In-Reply-To: <202311020241.3A22f4o3042181@donotpassgo.dyslexicfish.net> References: <202310312245.39VMjNJB080965@donotpassgo.dyslexicfish.net> <202310312259.39VMxm6W081150@donotpassgo.dyslexicfish.net> <202311010349.3A13nX1M094463@donotpassgo.dyslexicfish.net> <20231101220247.HGrrB%steffen@sdaoden.eu> <202311020241.3A22f4o3042181@donotpassgo.dyslexicfish.net> Mail-Followup-To: Jamie Landeg-Jones , freebsd-current@FreeBSD.org, dickey@his.com, bapt@FreeBSD.org User-Agent: s-nail v14.9.24-545-gbd87680ac8 OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15987, ipnet:217.144.128.0/20, country:DE] X-Rspamd-Queue-Id: 4SLtDW68YQz3YT0 Jamie Landeg-Jones wrote in <202311020241.3A22f4o3042181@donotpassgo.dyslexicfish.net>: |Steffen Nurpmeso wrote: |> Why? |> (That is to say: why -- if it is a *real* termcap? If it is only |> a translation layer to terminfo, i am with you. But otherwise |> not, i think a real termcap is much, much smaller, while offering |> anything a (simple) console program needs.) |> That is not to talk small the efforts of Mr. Dickey. But for |> example the mailer i maintain *can* directly use BSD termcap if so |> desired, and it works just nice. | |I agree that termcap does most of what we need already, so my main |reason is that there are 2 different systems in use to do the same |job, which is annoying. (FreeBSD doesn't exist in a vacuum) As terminfo |exists, is supported, and has terminal entries that our termcap doesn't |have, it seems to be better to switch to that. I'm sure it would mean |less maintenance for the FreeBSD committers too. I do understand that a bit. Other than that plain termcap was so small and i would assume essentially unchanged for decades, that i do not. Termcap entries, yes. I could imagine vt220, xterm, screen-256color, and take one of st-256color, whatever KDE and GNOME terminal, and rxvt-unicode. Makes seven. Likely automatically extractable via "infocmp -C" of Dickey's terminfo. Let's just try that: $ rm .TCAP;\ for f in vt220 xterm screen-256color st-256color \ rxvt-256color gnome-256color konsole-256color; do \ infocmp -C $f >> .TCAP;\ done;\ ls -l .TCAP -rw-r----- 1 steffen steffen 7145 Nov 2 18:40 .TCAP Not that i come over as a sarcastic person. |If terminfo didn't exist, I'd live with termcap. | |There are also benefits to terminfo: No. It is not "also", it is that there are. And that programs which use facilities of modern terminfo require terminfo anyway. Yet it is that many console programs do not (by far), nor do they know how to use all the amazing things that are possible with a UNIX terminal (just by glancing over ECMA-48, plus some OSC extension, plus superficial glancing over tmux console interaction). A real (non-wrapper) termcap library is very (very) small, so small that it could be a header-only thing that is included in every program (statically that is). |https://invisible-island.net/ncurses/ncurses.faq.html#extended_term | |We don't even run with a "proper" termcap anyway! | |"The base system's terminal database is referred to as =E2=80=9Ctermcap.d= b=E2=80=9D |but is actually an ncurses terminfo hashed database." - https://invisib\ |le-island.net/ncurses/ncurses.faq.html#what_platforms | |So, yeah, despite Mr Dicky's success in making working with both as \ |seamless |as possible ,it would still just be nice to not have to deal with 2 \ |different |standards, that's all. | |"setaf or AF, that is the question." So to say. For example the MUA i maintain needs 12 commands at maximum (then also 2 for ca_mode and 2 for keypad on/off, 8 otherwise). This is sufficient for complete control over command line editing. If it would, like bash, would implement multi-line editing it would add i think one or two on top, for vertical movement. All these commands are several decades old and exist everywhere. Add some queries for auto_right_margin, eat_newline_glitch, max_colors etc, and several dozen special-key bindings. The same is true for those. You get away without them, of course. But i tell you what. Instead of, i do not know, 50 or so kilobyte, on this Linux system we indeed end up linking against libncursesw.so.6.4 that is almost half a megabyte and has lots of symbols and other linker work to be done. The *complete* ncursesw library! O tempora, o mores! --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) From nobody Fri Nov 3 01:08:22 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SM2gN1RCdz507tR for ; Fri, 3 Nov 2023 01:08:32 +0000 (UTC) (envelope-from btv1==671aa5fb66c==tom@invisible-island.net) Received: from smtp-1a.his.com (smtp-1a.his.com [216.194.253.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4SM2gM1785z3YZP for ; Fri, 3 Nov 2023 01:08:31 +0000 (UTC) (envelope-from btv1==671aa5fb66c==tom@invisible-island.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of "btv1==671aa5fb66c==tom@invisible-island.net" designates 216.194.253.2 as permitted sender) smtp.mailfrom="btv1==671aa5fb66c==tom@invisible-island.net"; dmarc=none Received: from cuda501.his.com (cuda501.his.com [18.191.10.220]) by smtp-1a.his.com (Postfix) with ESMTPS id C38AA1E5 for ; Thu, 2 Nov 2023 21:08:24 -0400 (EDT) X-ASG-Debug-ID: 1698973703-1f26af249c4948e0001-XDYc8F Received: from smtp-4a.his.com (smtp-4a.his.com [216.194.253.31]) by cuda501.his.com with ESMTP id IRcXZrQbogCVQGyI (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 02 Nov 2023 21:08:23 -0400 (EDT) X-Barracuda-Envelope-From: tom@invisible-island.net X-Barracuda-RBL-Trusted-Forwarder: 216.194.253.31 Received: from zproxy101.his.com (zproxy101.his.com [18.218.2.49]) by smtp-4a.his.com (Postfix) with ESMTPS id C8C0287; Thu, 2 Nov 2023 21:08:23 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by zproxy101.his.com (Postfix) with ESMTP id 9AE29177C04; Thu, 2 Nov 2023 21:08:23 -0400 (EDT) X-Barracuda-RBL-Trusted-Forwarder: 18.218.2.49 Received: from zproxy101.his.com ([127.0.0.1]) by localhost (zproxy101.his.com [127.0.0.1]) (amavis, port 10032) with ESMTP id fF4wdu2l2jIj; Thu, 2 Nov 2023 21:08:23 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by zproxy101.his.com (Postfix) with ESMTP id 823A8177C05; Thu, 2 Nov 2023 21:08:23 -0400 (EDT) X-Virus-Scanned: amavis at zproxy101.his.com Received: from zproxy101.his.com ([127.0.0.1]) by localhost (zproxy101.his.com [127.0.0.1]) (amavis, port 10026) with ESMTP id aQd4uXsTVSxt; Thu, 2 Nov 2023 21:08:23 -0400 (EDT) Received: from prl-debianold-64.jexium-island.net (static-96-255-221-90.washdc.fios.verizon.net [96.255.221.90]) by zproxy101.his.com (Postfix) with ESMTPSA id 628E9177C04; Thu, 2 Nov 2023 21:08:23 -0400 (EDT) Received: from tom by prl-debianold-64.jexium-island.net with local (Exim 4.94.2) (envelope-from ) id 1qyife-0000Wy-Pr; Thu, 02 Nov 2023 21:08:22 -0400 X-Barracuda-RBL-IP: 96.255.221.90 X-Barracuda-Effective-Source-IP: static-96-255-221-90.washdc.fios.verizon.net[96.255.221.90] X-Barracuda-Apparent-Source-IP: 96.255.221.90 Date: Thu, 2 Nov 2023 21:08:22 -0400 From: Thomas Dickey To: Jamie Landeg-Jones , freebsd-current@freebsd.org, dickey@his.com, bapt@freebsd.org Subject: Re: Freebsd 14+ -- tcsh incompatible with terminfo Message-ID: X-ASG-Orig-Subj: Re: Freebsd 14+ -- tcsh incompatible with terminfo Reply-To: dickey@his.com References: <202310312245.39VMjNJB080965@donotpassgo.dyslexicfish.net> <202310312259.39VMxm6W081150@donotpassgo.dyslexicfish.net> <202311010349.3A13nX1M094463@donotpassgo.dyslexicfish.net> <20231101220247.HGrrB%steffen@sdaoden.eu> <202311020241.3A22f4o3042181@donotpassgo.dyslexicfish.net> <20231102175855.A1pj0%steffen@sdaoden.eu> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="HN1h7JErIyjKqOMa" Content-Disposition: inline In-Reply-To: <20231102175855.A1pj0%steffen@sdaoden.eu> X-Barracuda-Connect: smtp-4a.his.com[216.194.253.31] X-Barracuda-Start-Time: 1698973703 X-Barracuda-Encrypted: TLS_AES_256_GCM_SHA384 X-Barracuda-URL: https://spam.his.com:443/cgi-mod/mark.cgi X-Barracuda-BRTS-Status: 1 X-Virus-Scanned: by bsmtpd at his.com X-Barracuda-Scan-Msg-Size: 1863 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=5.0 KILL_LEVEL=7.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.116232 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-Spamd-Result: default: False [-3.39 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.81)[0.806]; FORGED_SENDER(0.30)[dickey@his.com,btv1==671aa5fb66c==tom@invisible-island.net]; R_SPF_ALLOW(-0.20)[+ip4:216.194.252.0/22]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[18.191.10.220:received]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_DKIM_NA(0.00)[]; DMARC_NA(0.00)[his.com]; ASN(0.00)[asn:11604, ipnet:216.194.252.0/22, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; HAS_REPLYTO(0.00)[dickey@his.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_NEQ_ENVFROM(0.00)[dickey@his.com,btv1==671aa5fb66c==tom@invisible-island.net]; RCPT_COUNT_THREE(0.00)[4]; RCVD_TLS_LAST(0.00)[]; TO_DN_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_SEVEN(0.00)[9] X-Rspamd-Queue-Id: 4SM2gM1785z3YZP X-Spamd-Bar: --- --HN1h7JErIyjKqOMa Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 02, 2023 at 06:58:55PM +0100, Steffen Nurpmeso wrote: > I do understand that a bit. Other than that plain termcap was so > small and i would assume essentially unchanged for decades, that > i do not. Termcap entries, yes. I could imagine vt220, xterm, > screen-256color, and take one of st-256color, whatever KDE and > GNOME terminal, and rxvt-unicode. Makes seven. Likely > automatically extractable via "infocmp -C" of Dickey's terminfo. >=20 > Let's just try that: >=20 > $ rm .TCAP;\ > for f in vt220 xterm screen-256color st-256color \ > rxvt-256color gnome-256color konsole-256color; do \ > infocmp -C $f >> .TCAP;\ > done;\ > ls -l .TCAP > -rw-r----- 1 steffen steffen 7145 Nov 2 18:40 .TCAP There's more data in termcap than that (which some people would like to use= ). And there's additional data for terminfo -- again, some want it. man infocmp: For best results when converting to termcap format, you should use b= oth -C and -r. Normally a termcap description is limited to 1023 byt= es. infocmp trims away less essential parts to make it fit. If you = are converting to one of the (rare) termcap implementations which accept= an unlimited size of termcap, you may want to add the -T option. More = of=E2=80=90 ten however, you must help the termcap implementation, and trim exc= ess whitespace (use the -0 option for that). (-T is appropriate here - ymmv) With -C alone, I get -rw------- 1 tom users 7315 Nov 2 21:02 .TCAP With -CrT, -rw------- 1 tom users 14390 Nov 2 21:02 .TCAP For terminfo, no options -rw------- 1 tom users 16027 Nov 2 21:03 .TCAP For terminfo with -x -rw------- 1 tom users 19533 Nov 2 21:03 .TCAP --=20 Thomas E. Dickey https://invisible-island.net --HN1h7JErIyjKqOMa Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAABCgAdFiEEGYgtkt2kxADCLA1WzCr0RyFnvgMFAmVESAMACgkQzCr0RyFn vgPPDAwAxAJMpu7+h9Ft5tjKGxEUdtQklNCiB29PorW00Se/xBUrWIlpW2F5Zb9e /6C6DCMigMts/QlY+xT8rG5QkJ0KPwcPSxDO8L45LOyeZXl2gXewhZMj3CTvnhFd kPY2ACQp9kCbvaWH7gUlE5gubQnN7Bl/JHZFi9Y4eIC1M14M7efx6t4bJl1jm1kc F3TaCBWE7hgiqc6XwInaNaBXW92eSwbg6XErwO0WfLybOdzfBUbWpsR3SehlCM9L hCs/GQrojzIpSOtu+ygSM86gMwZeTo40d4KNRjTdMG8hw2p8URHxqqy4zwbnwfZV g2z3Pby67kRrjwC00fLQb3aO50YjncKnIXUZmub9qbSW0GcpWElspeUzQsuBR7/q RJtpopbN6w4Ej3KFIUSm5wfPgU9xzDDU6lWIvmzw8clSreeF1PzQ8w1Z0Yv/0eDh q+Hs/06yP9q9/sJ4wT1LfL+NglMsig/fgX1FyyKyQkUrs5c3BF/9R3PCCQS4PaLo db6Zc3m6 =9J1j -----END PGP SIGNATURE----- --HN1h7JErIyjKqOMa-- From nobody Fri Nov 3 23:42:32 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SMcjk5qq4z4yj29; Fri, 3 Nov 2023 23:42:34 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SMcjk5d2wz4M4r; Fri, 3 Nov 2023 23:42:34 +0000 (UTC) (envelope-from gjb@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1699054954; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type; bh=24tg6VdPv80JrSuRvqgkOqst9njoTXOeEZ1xe8amkTE=; b=w0mZenDlMwevi1XNMyfFSgg9EtxVo6yh0hozcTZbiIZuOEuGKi7FR6aUs50J2StwhjuthF xhyMhuCF1UieL98DSS7MkA7vTKllUVh49g+EJ3vjVXNK9X2t0eLP0C6RPAYEaipqDTcteh Ax/RjvLgNZd4kiNQz0hoKJULKkjhRKMYMcRZT38SfkokvEFKtq5PiH1XvFR1k9rPonRIHn BmgW1FqU3RSSjxt13pRadQlqGOs2cuSxjhtHL4i+ixQMHINffIol6ahJxRhJXAV7ZgGaVZ Arel2YfC/eZtY+OOcMYn2CRTC4RqiSb2/PpJ7GxQR4jWkjkbH+Iuk88PBmD/MA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1699054954; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type; bh=24tg6VdPv80JrSuRvqgkOqst9njoTXOeEZ1xe8amkTE=; b=WQ8v52Fwjn+PalPWyMhrqXjcerwPjDdRMcWHnvK5hZSU9vAPADcUwPUSaHQt2gUhabxtFm DpeNDBj7Ol7UVVdSj001f9gpYGNFOb/liMybtuWKkQ3YZJY2LQuReE9aDbZNeO99uA3Efz EFvNSeOcoF1KTwNOTn7EtDVCXFfLIMcqdMIn7yiqp9TJxtJsSPlPYEr3tY+mHvFgqyh8z7 x/nOzqj866dDSCivRoHL8sjaLzGoYipnud9Vo4Vy+4D5xSrE8gahS7e1nwBFAkV2eZ1svQ hm7hn4afvIH7P3jex4oAgqWDTKyY6VBe0RTNjjEde2zQBmIJHYOnjIAp74/rBw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1699054954; a=rsa-sha256; cv=none; b=GKwjvYZ2AUL8fKZxL/DZnAnQdC+QajExobykDgLw3lqb7kk5lO6NZ25y+Qhc63SeSqGjMl kDawlESJiXVgVOZbbGGZLAsGtbvftlLrJJRwOT9//uLDJQ4ncyK9nr6KC6bnxMZW8tgZ8/ YiBNo8lmtSA7TO6+tJUDu4oLlxUUst1Ds9JhVUnQl234kPC2cdWcf2WS+ht+R9qWnIcCo/ jShiUIm4y+udWgkeZggqmBbMSHSsKNOkXNL4+4NJnZpDn5sWVsIe7FaxOMaw4+GzDeYROD r5wv+dhPrcgSsIhvG4zlczIXjbE66/5Aht7VX/wWB+gdJk/GMC1kY50aoHzAFA== Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 433C0CC46; Fri, 3 Nov 2023 23:42:34 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Fri, 3 Nov 2023 23:42:32 +0000 From: Glen Barber To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, freebsd-snapshots@freebsd.org Cc: FreeBSD Release Engineering Team Subject: FreeBSD 14.0-RC4 Now Available Message-ID: <20231103234232.GK1289@FreeBSD.org> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The fourth RC build of the 14.0-RELEASE release cycle is now available. Installation images are available for: o 14.0-RC4 amd64 GENERIC o 14.0-RC4 i386 GENERIC o 14.0-RC4 powerpc GENERIC o 14.0-RC4 powerpc64 GENERIC64 o 14.0-RC4 powerpc64le GENERIC64LE o 14.0-RC4 powerpcspe MPC85XXSPE o 14.0-RC4 armv7 GENERICSD o 14.0-RC4 aarch64 GENERIC o 14.0-RC4 aarch64 RPI o 14.0-RC4 aarch64 PINE64 o 14.0-RC4 aarch64 PINE64-LTS o 14.0-RC4 aarch64 PINEBOOK o 14.0-RC4 aarch64 ROCK64 o 14.0-RC4 aarch64 ROCKPRO64 o 14.0-RC4 riscv64 GENERIC o 14.0-RC4 riscv64 GENERICSD Note regarding arm SD card images: For convenience for those without console access to the system, a freebsd user with a password of freebsd is available by default for ssh(1) access. Additionally, the root user password is set to root. It is strongly recommended to change the password for both users after gaining access to the system. Installer images and memory stick images are available here: https://download.freebsd.org/releases/ISO-IMAGES/14.0/ The image checksums follow at the end of this e-mail. If you notice problems you can report them through the Bugzilla PR system or on the -stable mailing list. If you would like to use Git to do a source based update of an existing system, use the "releng/14.0" branch. A summary of changes since 14.0-RC3 includes: o ISA and GIANT-locked driver removal has been delayed to FreeBSD 15, and system messages have been updated to reflect such. o An update to OpenZFS correcting block cloning between encrypted and unencrypted datasets has been included. o A fix for Hyper-V emulation within QEMU resulting in system crashes has been addressed. A list of changes since 13.2-RELEASE is available in the releng/14.0 release notes: https://www.freebsd.org/releases/14.0R/relnotes/ Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 14.0-RELEASE cycle progresses. === Virtual Machine Disk Images === VM disk images are available for the amd64, i386, and aarch64 architectures. Disk images may be downloaded from the following URL (or any of the FreeBSD download mirrors): https://download.freebsd.org/releases/VM-IMAGES/14.0-RC4/ BASIC-CI images can be found at: https://download.freebsd.org/releases/CI-IMAGES/14.0-RC4/ The partition layout is: ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label) ~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label) ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label) The disk images are available in QCOW2, VHD, VMDK, and raw disk image formats. The image download size is approximately 135 MB and 165 MB respectively (amd64/i386), decompressing to a 21 GB sparse image. Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI loader file is needed for qemu-system-aarch64 to be able to boot the virtual machine images. See this page for more information: https://wiki.freebsd.org/arm64/QEMU To boot the VM image, run: % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt \ -bios QEMU_EFI.fd -serial telnet::4444,server -nographic \ -drive if=none,file=VMDISK,id=hd0 \ -device virtio-blk-device,drive=hd0 \ -device virtio-net-device,netdev=net0 \ -netdev user,id=net0 Be sure to replace "VMDISK" with the path to the virtual machine image. === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMI IDs can be retrieved from the Systems Manager Parameter Store in each region using the keys: /aws/service/freebsd/amd64/base/ufs/14.0/RC4 /aws/service/freebsd/amd64/base/zfs/14.0/RC4 /aws/service/freebsd/amd64/cloud-init/ufs/14.0/RC4 /aws/service/freebsd/amd64/cloud-init/zfs/14.0/RC4 FreeBSD/aarch64 EC2 AMI IDs can be retrieved from the Systems Manager Parameter Store in each region using the keys: /aws/service/freebsd/aarch64/base/ufs/14.0/RC4 /aws/service/freebsd/aarch64/base/zfs/14.0/RC4 /aws/service/freebsd/aarch64/cloud-init/ufs/14.0/RC4 /aws/service/freebsd/aarch64/cloud-init/zfs/14.0/RC4 === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can be installed by running: % vagrant init freebsd/FreeBSD-14.0-RC4 % vagrant up === Upgrading === The freebsd-update(8) utility supports binary upgrades of amd64, i386, and aarch64 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as follows: # freebsd-update upgrade -r 14.0-RC4 During this process, freebsd-update(8) may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install It is recommended to rebuild and install all applications if possible, especially if upgrading from an earlier FreeBSD release, for example, FreeBSD 12.x. Alternatively, the user can install misc/compat12x and other compatibility libraries, afterwards the system must be rebooted into the new userland: # shutdown -r now Finally, after rebooting, freebsd-update needs to be run again to remove stale files: # freebsd-update install == ISO CHECKSUMS == o 14.0-RC4 amd64 GENERIC: SHA512 (FreeBSD-14.0-RC4-amd64-bootonly.iso) = 2af53c6611eb67b184ba4c93c87ad5aba94911946da453428e38af385691c0a952126feff1be717bf67a3d8a227509449dd011364a9587eae41a204da7d18252 SHA512 (FreeBSD-14.0-RC4-amd64-bootonly.iso.xz) = fbfe4be553dc78d69981646673b66f9dd8f83d9f5fca3b1e50b11a816f4d47f5e5733e655adf0bb0a78ea0bfb6579ebee0c48157d69b00ec8a669b292eb0c16e SHA512 (FreeBSD-14.0-RC4-amd64-disc1.iso) = dac0f20ee98a2679647f1afdc8271b809d436182203e0b17601c69086e532ba73edf3872f67016d768e911164d7ecbc24770ce5b5546b2fe7a6fdabbc40fdc5d SHA512 (FreeBSD-14.0-RC4-amd64-disc1.iso.xz) = 662a5cf5c9f1c547f19c974d157b91c600d8e94cd57ff683d3a97a78e10d7675c538c55ad631d7b0c8aed7b4860e4453fce48714debd0b7ded787c533860b5c3 SHA512 (FreeBSD-14.0-RC4-amd64-dvd1.iso) = 6c25adce9d49bc9f168ef4048f4339ae70c1648c392b8f3f466335952f9eea5a05960b78bfee46acd38388195b12851e17d2cacf41be4b1fb22b10d5cb32404e SHA512 (FreeBSD-14.0-RC4-amd64-dvd1.iso.xz) = cd6201e3432d0fc2889c1612612582436e61d322533a05552650fdff2a48583ff7d399d709d85ef279a377f4afb85894cb7544e7b984cdcf48561de412eb18cf SHA512 (FreeBSD-14.0-RC4-amd64-memstick.img) = 02eb4fc41a595d9e78a1866b205d4301b502ec8deeb63414a01bbe61ff3ffecb503ad5a6cc75be4e0e5e11315f5875e141bead5ffe22fa69b111161d7c29c903 SHA512 (FreeBSD-14.0-RC4-amd64-memstick.img.xz) = 705c41197a6d354c6c086aa2feca36704808db0df423cdef8bd2bc59fe3f12931a4cdb7257631602e59d49862e31edddf0b4dc974a61ceb9dd6a59209874ee88 SHA512 (FreeBSD-14.0-RC4-amd64-mini-memstick.img) = 6988e9300baa0572d0801d9de289784c63b8f6aaab2c2cf37775458bc6828c79fcf3dc873b553346b0e470defc613a7ffdc4cf697e913e25f1cc8c3f95bd6c23 SHA512 (FreeBSD-14.0-RC4-amd64-mini-memstick.img.xz) = 9d597049a794d5f6474414d0146107bf4f2886b25a6b48e8cbadf00868ad63afd219550257991509a3969a0462cfa655229d5e6aded9cbb601b6b3508868fa6d SHA256 (FreeBSD-14.0-RC4-amd64-bootonly.iso) = 28674417c8da59ffe4d1c4fc4f325f49d3f627787bda5dd485a82c6080816260 SHA256 (FreeBSD-14.0-RC4-amd64-bootonly.iso.xz) = c9fe6bf7598446ddaaa181a503b559bb185e8f2acc63f5cd93d3caa77b49e762 SHA256 (FreeBSD-14.0-RC4-amd64-disc1.iso) = 213d610088db85392ca8a8b8c916c93fff9dc8f8d1c5a07cd2bba9df55ca9105 SHA256 (FreeBSD-14.0-RC4-amd64-disc1.iso.xz) = 74c460930aaedc994bb976579baee89df81b08dbacfe7668f004d9d45305b9e3 SHA256 (FreeBSD-14.0-RC4-amd64-dvd1.iso) = c2feb7808e4e34a32c3c309c1adb0bf8ed5cd0fa4b4ee98a44b1ebc7e48dc04c SHA256 (FreeBSD-14.0-RC4-amd64-dvd1.iso.xz) = a06045e90977e5d12c104daf7d96d9f0f452d3215d080dd27d072ab670ae981d SHA256 (FreeBSD-14.0-RC4-amd64-memstick.img) = d315c05038065f984c178829deeda47ac682c74c1bbe66a177873cdda7bc25b4 SHA256 (FreeBSD-14.0-RC4-amd64-memstick.img.xz) = a9068d9d04ac6b32f1d22b4ae803839a28f399fafe70e77d0a6aa7b3c89544e8 SHA256 (FreeBSD-14.0-RC4-amd64-mini-memstick.img) = 0035dd4d97b5243b0b8ddf9636bb39071013941d48fea9be0b92015cf74d4d5d SHA256 (FreeBSD-14.0-RC4-amd64-mini-memstick.img.xz) = d5e7b50fee0cfd5a8cce12fe0e86cc2539fe4d84345c5363b7ccfc08c59eb525 o 14.0-RC4 i386 GENERIC: SHA512 (FreeBSD-14.0-RC4-i386-bootonly.iso) = 8a9bc193a306328ec6fc17fe85a7333365a6f41560876ba6753623bff37a361b9e4e9417cf31f5913205c27e01b06f431553bff065efb4926d251229883e82f1 SHA512 (FreeBSD-14.0-RC4-i386-bootonly.iso.xz) = d4a21ada61e8f7157191c022ab30f0f17fabc3828ec75628fe18946a7b52f44d9f684fa07d61ea01ffc0a64a4fd7cfd1927985a4be1d264c7840131999ed87a2 SHA512 (FreeBSD-14.0-RC4-i386-disc1.iso) = 1b91762401259e9a0aab18499fa8270f8dad2b7651c5433d313850052af7e702a66f9408a7f274e379cbd86cfca184fb3e9181f33939a771dce1e683f0fb90e5 SHA512 (FreeBSD-14.0-RC4-i386-disc1.iso.xz) = e535de2443335277f43fc8de8e93fab85b452d8c67596d4b87bd6830f0bf6a09e0014600d2e984c69bf5e5bb600683441b87cf580fa3994a626a098e10cb3272 SHA512 (FreeBSD-14.0-RC4-i386-dvd1.iso) = 2b803000b10cb5d1fe324708193874dc52035ac6ed3442c6d6ce1668597da5f19c1bf920dc63a34b5cf599c52d2d423e5ea22402edaf084f219b755f7be99c24 SHA512 (FreeBSD-14.0-RC4-i386-dvd1.iso.xz) = d269054590c2f66217a7d500c28886fd80f105e343052a69b55576c2aea981e9745d10b49778d18af13f8b2b2e884eaeb90b1d0324f196dfca0779032ff479bd SHA512 (FreeBSD-14.0-RC4-i386-memstick.img) = 8a8c6488926099c04a78cf0ddeeececbf0c4d2372bf1ea00516d8bdad8ec31f0ac81333c06c3a78d1c883297fa584e53cc895f50a4cca620a9e20125c909d16f SHA512 (FreeBSD-14.0-RC4-i386-memstick.img.xz) = 68211b0d63ffab63a76e04001d9ed0960095a1e4effd24d38f7fcb7e73d3d1ad99ec1a94d555e5610375bae534d01ef925a7d08ef542a9a352a6a7330712baa6 SHA512 (FreeBSD-14.0-RC4-i386-mini-memstick.img) = 0571d8c32f493a908beda92bc92c597f9bd80a2474108ff743ad11dd463ef21c754294da5e993beb8944df03cd639d2d969318651d1fe1a1251b3f4f1f5eb66a SHA512 (FreeBSD-14.0-RC4-i386-mini-memstick.img.xz) = 83f3422ee6935f8b6994a1fc40c2f750ea27bab1c1b324e4b3300f87de47e8a29e7f127201a4eb03f713b6fe1d47ea81a05cbf8ce063286960c3e28ab2f17694 SHA256 (FreeBSD-14.0-RC4-i386-bootonly.iso) = bfeacfe8bbf429cd88e8ed4145de24f747e75c4e97c6bfd023d88d4752e5100a SHA256 (FreeBSD-14.0-RC4-i386-bootonly.iso.xz) = c11f09b11183105b5920753bbcf68427574d09ca7fb10d812b995999c04b2b0c SHA256 (FreeBSD-14.0-RC4-i386-disc1.iso) = e032e4300210f9aed57e5c820fc3c07c4d0b9cbba417d61458dba74d188f0214 SHA256 (FreeBSD-14.0-RC4-i386-disc1.iso.xz) = 53d6c96580d2a486b9da43169e4e4183cd125b06f3a1e7fa25e74487c20e50ea SHA256 (FreeBSD-14.0-RC4-i386-dvd1.iso) = 7e756d0ae13e9798601f45740ab7381c0e319efa3691ba1565ff203a613ea77a SHA256 (FreeBSD-14.0-RC4-i386-dvd1.iso.xz) = 90bbb28db964188988bbff402a677fe10cffaf9f620fc78a5883a1c381a969bb SHA256 (FreeBSD-14.0-RC4-i386-memstick.img) = e4699f5e7ffe6d9f38b000e324c896955c005324702e30477b529786a49e00b9 SHA256 (FreeBSD-14.0-RC4-i386-memstick.img.xz) = cd978403efd56248c655232b02dcf5e3b292faf691c98e72f1482707e2bc9db2 SHA256 (FreeBSD-14.0-RC4-i386-mini-memstick.img) = b80b37c2aa16c4166426e2f6f3ec9fdccd765ca965f75b855ef3dda619c7a02e SHA256 (FreeBSD-14.0-RC4-i386-mini-memstick.img.xz) = 5157bf384edbc8c4069e1360297a680e3540be85aad614f82c7bcc14d1ee1055 o 14.0-RC4 powerpc GENERIC: SHA512 (FreeBSD-14.0-RC4-powerpc-bootonly.iso) = 02ad34d6e7a3acdef46d3a6bb7abb44fe3e55fdf8f99b900a3aedd97520f409888db21e9ab359c641deabfebcce5360ec1d1d4ac90fe60c42b2ee8de27c9da89 SHA512 (FreeBSD-14.0-RC4-powerpc-bootonly.iso.xz) = 1a8b2b661cfbef4f1656c5185dbdbd37b751ff4862f951b30364d9d91bbe030e69c5ee98adac1be81a3a7fc0e209f530c57440c714c8e9e8b1a547e3cdbb6633 SHA512 (FreeBSD-14.0-RC4-powerpc-disc1.iso) = 783445a184562191cbaee132004de70502aac22001fc5aa1a10ae0d5d18eae5005dc630a2c3e72fe9b47e98c4625edef165fce21f1678deb1f8ad3e991ca8f3e SHA512 (FreeBSD-14.0-RC4-powerpc-disc1.iso.xz) = c28086587265cc80ecff0233ac6eb8b3e4a51232e5ab662c04df513e78fe996f051aefb668038190658805d18539c86f49e992540308ff35e4c47fd24a72e292 SHA256 (FreeBSD-14.0-RC4-powerpc-bootonly.iso) = a6c330740401487ca15097612acf08a1b8c933e94f6a1a104527062250f5d5f9 SHA256 (FreeBSD-14.0-RC4-powerpc-bootonly.iso.xz) = e7e5bfcd06bce96a10785bfe0b2aaba21f7cf0963af0744e1b064bc198c23811 SHA256 (FreeBSD-14.0-RC4-powerpc-disc1.iso) = d31ac53ca89a915c2a613343bd4bd5bf128d2e8f9f38afa789e232097c25ab5c SHA256 (FreeBSD-14.0-RC4-powerpc-disc1.iso.xz) = c85cbf09b76f66b6795b18214d06329694f392e06ffa9df52447cede5c0a9aec o 14.0-RC4 powerpc64 GENERIC64: SHA512 (FreeBSD-14.0-RC4-powerpc-powerpc64-bootonly.iso) = 6dab28bf1bb33d4f0b2f90eb3dd45c473e2ee446125f3597a43c5a69d5731a3bf52c402ea8d5df0871dc53e0689bd01dce279e36e9ebff64bd4a9a7988083795 SHA512 (FreeBSD-14.0-RC4-powerpc-powerpc64-bootonly.iso.xz) = 3022076a2c7bd3c0b27775320267e232f61efc4469d84045f2732f0864a780641e8833de89b6a591a2a5302884588b956b64cf85c538467998f7e005af72be0d SHA512 (FreeBSD-14.0-RC4-powerpc-powerpc64-disc1.iso) = bf3c2a10a513ff281e77aa0cd41d0a5c8bee4d5be94936615e612dc3044dbb4e8077b0e5e1fa236479a0d48b72649871e5b1f5cb8d64cb484d09037ce3407f65 SHA512 (FreeBSD-14.0-RC4-powerpc-powerpc64-disc1.iso.xz) = ac4ba53584e65b9ce94a6fe50139c4df10ba527647c170b4a37077e7bdd0d6abebb0954ba7b06f4b1d0aa27d74fec6f8cde2f214646d9c0ed4523790378bac96 SHA256 (FreeBSD-14.0-RC4-powerpc-powerpc64-bootonly.iso) = 73c31144955ad8a63772dec8ee4be107ec9c290e966faf95f354c63c1b41ca14 SHA256 (FreeBSD-14.0-RC4-powerpc-powerpc64-bootonly.iso.xz) = de0a4127dd7b7ea2bd4bbfb809094199e1f9135f1c9fd12fcc6e06fe7c818861 SHA256 (FreeBSD-14.0-RC4-powerpc-powerpc64-disc1.iso) = 34a72ea31ae01ad57ced7e4ab6eac3b9714179003ecd0995996284c74a88ebb8 SHA256 (FreeBSD-14.0-RC4-powerpc-powerpc64-disc1.iso.xz) = e3f82a17d9dddb20c6ca195340ddcf2d63eb82bbc6c381b4adcd864c1845386f o 14.0-RC4 powerpc64le GENERIC64LE: SHA512 (FreeBSD-14.0-RC4-powerpc-powerpc64le-bootonly.iso) = 14338fe5d76356713ee94f6b3ca293abbdaf380d0cd2b74ada14a4ef475f6c34c68e67dd13fcb69dbd9cbab1a951d4e71c81d5add7f3133d792e94311c8f262e SHA512 (FreeBSD-14.0-RC4-powerpc-powerpc64le-bootonly.iso.xz) = 399fdb443265566bd5e6ce1a3dc11ca41f005968a529a7535dd72622a3ae0fb2a93e66b7753c953fc5d35c63b58022ab4c223f914d3720a19490332b379156e3 SHA512 (FreeBSD-14.0-RC4-powerpc-powerpc64le-disc1.iso) = acc729d7abd0f8474e1fdf3f22804aaa486c98e479dad813b83116036e0db16dce9ab956c1fd6fb80d69f462f43200f3220864e1901ae62903b717682838e5fe SHA512 (FreeBSD-14.0-RC4-powerpc-powerpc64le-disc1.iso.xz) = cb341d0eb64847a50ccb33170bbfca9c8855377e6883a4cc0c181967182700afc669b6112edb37275519cac5992765700f9eb16aef6d0bcfbc25cdb399839cab SHA256 (FreeBSD-14.0-RC4-powerpc-powerpc64le-bootonly.iso) = 2bff70b162f8f4711f9f2eb67fe10716166f4b8c062e4cbaca34fb8d521bfb09 SHA256 (FreeBSD-14.0-RC4-powerpc-powerpc64le-bootonly.iso.xz) = 03c7bd799e52bb6e95428ce7809ba863f2c98e2ab71dbb45fcd67eddf79677ef SHA256 (FreeBSD-14.0-RC4-powerpc-powerpc64le-disc1.iso) = e2387661bb279c3cf6f904a858c2d87aed1ede49a29f1d1f8424d65bad38ccd6 SHA256 (FreeBSD-14.0-RC4-powerpc-powerpc64le-disc1.iso.xz) = a3b4ca6af55b099100677685033328868d28cdd9322b1bcd12b4d5c0919d6652 o 14.0-RC4 powerpcspe MPC85XXSPE: SHA512 (FreeBSD-14.0-RC4-powerpc-powerpcspe-bootonly.iso) = 4417492d5d6ae001661252a465090d9d6daa50429cda5c069284c95095533e35e6b9bb94c4c5a24d8c51768a9732b960b3659f1e66577c4e0baf41c37cdb01e7 SHA512 (FreeBSD-14.0-RC4-powerpc-powerpcspe-bootonly.iso.xz) = e9fb2333c5dea7048fbf289209bab16a8854de08847782acbcfe869d32d77aa5dc4089020baf53c4e88aa95c8dc696ff7bb770f8d14a823d2c0248c477cf78d1 SHA512 (FreeBSD-14.0-RC4-powerpc-powerpcspe-disc1.iso) = 25ebf8167e090dd09647eff3f26c8313097de84b3038165018afa05f5dc5893b63286042a524fb53feeb323ee337c934616f47c6739e65cd89ffc3bc0e5076b7 SHA512 (FreeBSD-14.0-RC4-powerpc-powerpcspe-disc1.iso.xz) = f7199bda837bd15ad1c201962fcc31c88ef0134605092436f09fa1ee7027f440cd808deef20c34f63c6a80de1411d1eababfa0ed529af091dad7baef8c676a77 SHA256 (FreeBSD-14.0-RC4-powerpc-powerpcspe-bootonly.iso) = b9b930c2e2d3a320befc46cd93eeeb8bb10d8c87db8864d00fc5438def022391 SHA256 (FreeBSD-14.0-RC4-powerpc-powerpcspe-bootonly.iso.xz) = 9281bceb101f97b9741bb0ca3407998db598a35c6117f472409d7dbc88c78f4b SHA256 (FreeBSD-14.0-RC4-powerpc-powerpcspe-disc1.iso) = 01b59d130bb608dfb012306472d24d9a46a25c329a2d86bb9396c5b26c9233be SHA256 (FreeBSD-14.0-RC4-powerpc-powerpcspe-disc1.iso.xz) = 721a3a28b3cebb358d5d93ba7cf7345325ea421d6fb1c6b624ba8d8a8244d23d o 14.0-RC4 armv7 GENERICSD: SHA512 (FreeBSD-14.0-RC4-arm-armv7-GENERICSD.img.xz) = 5d0592accd64318e81ab36b3f15cd828998734a6c781d9a267928550a5ae60ab3a2e36ddfdc6749b6851f96e06f57778aabb861c6f55cdc2476402eee1c8f8d2 SHA256 (FreeBSD-14.0-RC4-arm-armv7-GENERICSD.img.xz) = 858f153be5aa6312e14ae8b4109bd7bf3b221668cfacada991bcd22beec95342 o 14.0-RC4 aarch64 GENERIC: SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-bootonly.iso) = 47b116b596167cbabed0cbe238b0265c79cfc9cd75be74ab690c465756145552e6c8d40f8a803d56afb4d7ef0106cce14581d342e31c92cf230b12ff5fe04324 SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-bootonly.iso.xz) = 379bdb38548995866a5325b3fd4ff71b90887d2b97d9c5f41561d41c953cca271990a66b541b5625897ef4ce1359deae8fcf42f7efa4f19aa1b582793fb4e513 SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-disc1.iso) = 105a6fe2f4b4b0669219adba0aecc4f056e27d3f380d1591a8bdb1cb60917b52242bd5ac9127a461bf3cdc85d323402977e617220c37129511149810e166c48e SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-disc1.iso.xz) = 413a2ce8523ab59acd70bc8e52c93ce65558cf0b57627683534267d5695977b1bcea85d754528251e1375b469f8f69b15e22476fb3cd8916cb59c4ca10a6217a SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-dvd1.iso) = ad536c842136232eafa8f27b57641212c3b13bbb8ad560cdc7d964dedbfa878b6f050876792c94a54c8caccc687c49fad1bfe5586e51f9001c2db5fc1e24651a SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-dvd1.iso.xz) = 74d78034d36f19f918e3c807ecb675b5d95bbe3d6fa517d6d2ceb10a29fcf7d89c9067ec1c78638af6cc8c5fba8eb91bb5445a4af1a66a447c03000433ee7ac4 SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-memstick.img) = adea1b24641b05b1caccd806f224397421cf94d1105861d3d6485065027461f20809edee7f258fbf45a69cd82a1beae7afd0c48d025a8e4646232d9a634abf1d SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-memstick.img.xz) = 76c6733aea25b1c7130b0dd87056a40310caf5868afd592fb0239a882cd45f61c8975b3819a958d0dd42385d2c52dbe61dc910d7814a0c8514c804b52944da09 SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-mini-memstick.img) = dab27511105faeeaccfaabb498682906ff2d61561e9f422eb26b20abc4ce2bbfa0a6d3cbfc5e26e06a737fffbb799559ebd3a659ad5a37f361937cdbf0f3c312 SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-mini-memstick.img.xz) = 918d3452b5a4bc5873e781596d5bc119cde82b89f782094efc5e6913bc58774bf368ee178287fce22ff146526cbe17171e7db45acafdb94bc2818d45c475fcaf SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-bootonly.iso) = 84cedc4fcf0da7186f1289815276b7d6eb1cb9fd0058a8057bf130e00b7596e5 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-bootonly.iso.xz) = 080dc3e9d965ef4b5180b376e5c6623fb5d2fdb6b6e3ed151ca981eef6965675 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-disc1.iso) = 41a9163f4adaec848319f914f23879c608fe73ef3d498f1b402494d594e86fa8 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-disc1.iso.xz) = 621897f6d6f3631b0b830d08fa5b969a1a556e18aac637a05a6d9876885d440a SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-dvd1.iso) = f252763cecb39b3fa6f3d2a75dd593bd891f01c3dcd68f90436a53610b77fcb2 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-dvd1.iso.xz) = 7e9e9085ef8c4ec7f1bf7e493fb16f2101edd59342b05de7bd52c4e142aea812 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-memstick.img) = 145eda64f7a3e91f3ba253478a5d290fe141a0f6c2f8050e04625ec759f1e043 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-memstick.img.xz) = 7afc16842df83f0722e667eca07cdfcfbc9b2c35f8437b3397c195e6a9636c27 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-mini-memstick.img) = 9baa46356ae16a828e3e8ad3d9f1217bf4dd2d826392f18797d885600f7e814c SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-mini-memstick.img.xz) = 000ee91e812d04886d04d6e4f77516835caf1c372bb37eebbcd81a56f5dd83e3 o 14.0-RC4 aarch64 RPI: SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-RPI.img.xz) = 7291b077b0338c5400af32eb6822d0139b953ad971cd9f44c5646ab5e3e502833fcda35005412a7b24203dd8dc9e3b2fe68bc3c737812b2255be624094013c47 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-RPI.img.xz) = 26d84974d64fc0fb10cc8f5f7afd9fd49a84b42392b3537fd8766bdcc0e0cd41 o 14.0-RC4 aarch64 PINE64: SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-PINE64.img.xz) = 6aaa42b2f515e3847235001382683484a57790e9ba1da8b19fc318668ea6b0640f76e00d6a12b3daa1ea9ea09bd0afd0db1fa322ed236fa9e181c1ebaa19906f SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-PINE64.img.xz) = d242d0337fd76684ebfce4ff84641303da07502d51f33089219aa70c615eb4b2 o 14.0-RC4 aarch64 PINE64-LTS: SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-PINE64-LTS.img.xz) = ce3deff3d02244359303331b0b3ed966bc503a42f1da0eee54f62984d2e8e54dc61f184c699cfb11aa3465fe31a89028799c0059185915d151da3be10301b8cd SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-PINE64-LTS.img.xz) = a6d398d616d2f9db3692f2c8118d9a5cde3960cdf2797497a7c155b9e8139b37 o 14.0-RC4 aarch64 PINEBOOK: SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-PINEBOOK.img.xz) = f0a50d83fee5d113a95ab09c64c757243bb8874d8384c05f4bc14d6f5bd33075989ae0a73c13a46b9107f32c2834a74cde5481e970fb47d064544664a21f6abf SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-PINEBOOK.img.xz) = 42e38931bd4d527ca0753cf861f90e91d3df2f9e108c632656a77bcf16bf5068 o 14.0-RC4 aarch64 ROCK64: SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-ROCK64.img.xz) = 14888fe2af5cd4f1787b86cd49c61f353619761cbe43436beb12ca1207b5c15e682ec0446257dd0dc4876c9e0a9843b318e38f20f4b8f96f8aecfb2c7d8ee6d2 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-ROCK64.img.xz) = 720687a8f2f7639d661dc21bd2176bad14c27f51d6fcdf6aa45fa976352332e6 o 14.0-RC4 aarch64 ROCKPRO64: SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-ROCKPRO64.img.xz) = 476f9bf3cf86aec65823eeeffe8b3caf3f8df3b599672137bc6cddacde16b5db28575e768206cb5d29baee09236a658a03f75efb5fdfb766adf49abcd698bee3 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-ROCKPRO64.img.xz) = 66d44eb1c4745b80c928dc71fe4822b9adc213cd66dbb61f78f440d715c9cd82 o 14.0-RC4 riscv64 GENERIC: SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-bootonly.iso) = 524773593f3187ef7bacb7bcd49ad3422121b819ae34f51d79d6ce91f2754df7e52dd28df62c335bccfd987bd7af073a00d04beb866cfc83d710e6cdc8d33624 SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-bootonly.iso.xz) = b1fa47bfe88a85dda0a7a92e76d65fd620a5c62a1c8fb5baa21183ff75614bf80c63424a9efd4a4a646e50c03e1dfb17c49c589dbdf7c8c78f915835115d1ce3 SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-disc1.iso) = 2627889757b073413dfdf94118ae7d47a173a4a6f148d9552c7f77357ffdda54298a4ae59b0c5a36159076784a2f50ca1c24cd127616ade0945a953604d62935 SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-disc1.iso.xz) = 756e79801584cf2366d8eb0365facd53e6fcd3ae1c753073f6389d4e16c4f839ddf8e5a26b27daf767b5b727dac3d2976e14b02231d52498de7ee4bc4dc34541 SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-memstick.img) = d511a815a8ceef7bb3197dabecd4e59ba61078d008f96ec6c8990b9d0583569ac896d8739133feb7f13ea91635232d6dc3e6f9a8e5d546047ecef953b087cfd8 SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-memstick.img.xz) = b33caeb29f10dda4bbffba3ab1cdd914777e1b0639a2264859741522f313f38bde8a9bfa24e6cdb64c02746257e7dabaa56c39b3824a66480063e8be91c79fb6 SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-mini-memstick.img) = 68c638927e0e070e8ec7a704e763db9561a23b46d39288e55faa1ac8fde0b39853ebf9c36e2f51752a965d6940cbdbdcafdff2bffc33fad9866363988dabe337 SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-mini-memstick.img.xz) = af0b304c13a6bb69eebc5e106caf60419a8d41d2da90ef935b76e7b39cacceba98c37a8237d7cd3d012fcd4658d71a36d7197f7e4ee2b9fa67c8d7bd4c33c830 SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-bootonly.iso) = 3605436a2601aa992ab8f6b0ac238e13fd8fe14c11c42c6fe5ffd2395f0b5669 SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-bootonly.iso.xz) = e9423f5452213d821720bb6497416741f678187d4c7eb885437661c7b13af955 SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-disc1.iso) = 5f81e6deb3c98feca33ae5f5b409bb25b425b62279bcc1b40a36e756ad1ae1a9 SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-disc1.iso.xz) = 8c6e348f874ef42aab7527fd118902862529e37a50e33e73ba700758262501c8 SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-memstick.img) = 69153d6dc19fe08af410f23af3c2f95bd33500e9152e2f00a9489d47fa308faa SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-memstick.img.xz) = a1b97f38dd5f16c2c0fca710a6c296e5420388d2df887c66c31c7b152449cf47 SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-mini-memstick.img) = e9a370a815ce652fa9851242b4beea28a41ee27ca3ccab87c2605fc491dc8fbb SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-mini-memstick.img.xz) = 93075f74008d544c843332ef792dbcae4cf26ba57b50842c39f299e8137d1da3 o 14.0-RC4 riscv64 GENERICSD: SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-GENERICSD.img.xz) = e61212d3bcb42858f080c0260fac4d0fcee80819de0ca6504bb0c9113cf598b43d11134ac26a9dc3b5fc142431370c3bec86debd94e02a2fa3114c7c7d9cc34f SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-GENERICSD.img.xz) = e1bb1522ebaeb9a8b0d218af007ba76542d87e6b0fd146fecc07bff7d2bbed90 == VM IMAGE CHECKSUMS == o 14.0-RC4 amd64: SHA512 (FreeBSD-14.0-RC4-amd64-ufs.qcow2.xz) = 166b0709efc63262b964c604ea746e1ac6743b2bead2efab5d5c4d6c9491a336e39d1a793b465eb751f6085ef7fa0988840e1dbcb47f67f0f5dd7ae3d48b57c4 SHA512 (FreeBSD-14.0-RC4-amd64-ufs.raw.xz) = b158c9369ecbb0178cc048990f855a71e6ffbff32f0bdbf2d5ff0255659b95e062ccc886cfdd7f91ad25fdb1d8d0f4bb78d3d097202bc6b8bd27cf13fde3220c SHA512 (FreeBSD-14.0-RC4-amd64-ufs.vhd.xz) = f860eeb1cd405bd074cca746542cff147c9331a5b64a50c43c95d686686db81b5d2e4b1f5ea8957f403b4425dfa156bf39ede7a98807d25828d7d9dc0232dd69 SHA512 (FreeBSD-14.0-RC4-amd64-ufs.vmdk.xz) = 3787cf9de0a5f4b8ae358f2316ddf62493aa6b30d70f6af2108a1730e9d79e07ef847932d7fa42b11f6f5b8b9eb3f33f41c701a67f2995005afdea053d6ef330 SHA512 (FreeBSD-14.0-RC4-amd64-zfs.qcow2.xz) = c3e7e36e5b19f3ee80011a035b047063deb64acc1409fccd3732f5639d0cc1ce0c0b1da0f60a99b3cd7c696243917ec580ef6d5319b52c1763676def92d34e86 SHA512 (FreeBSD-14.0-RC4-amd64-zfs.raw.xz) = 50c9a08d10d96f42c1669abf25a75d4115c6eb6b71241f1b8e321dcf2ac313627e6b449b941604150ecef652a7786dcd0b0be7c1b4221ae459c08e0bd5ceee91 SHA512 (FreeBSD-14.0-RC4-amd64-zfs.vhd.xz) = be44fe7f97ac044b00cc39554df4eca8a19dcacc03e936747822acbc091f0baa5b6f6ebd219fd34a1f3e86f8031cf132cdd7e12f9b498bef3b9a4c79cb60d3a8 SHA512 (FreeBSD-14.0-RC4-amd64-zfs.vmdk.xz) = 25a399e1165f7c77ab96daff57270cc5013fc3f2a1d777583fbde100a396211f46661f3fd9e675367e519b7be3cc29276529aaab062a821e8763496e8a628597 SHA512 (FreeBSD-14.0-RC4-amd64.qcow2.xz) = 166b0709efc63262b964c604ea746e1ac6743b2bead2efab5d5c4d6c9491a336e39d1a793b465eb751f6085ef7fa0988840e1dbcb47f67f0f5dd7ae3d48b57c4 SHA512 (FreeBSD-14.0-RC4-amd64.raw.xz) = b158c9369ecbb0178cc048990f855a71e6ffbff32f0bdbf2d5ff0255659b95e062ccc886cfdd7f91ad25fdb1d8d0f4bb78d3d097202bc6b8bd27cf13fde3220c SHA512 (FreeBSD-14.0-RC4-amd64.vhd.xz) = f860eeb1cd405bd074cca746542cff147c9331a5b64a50c43c95d686686db81b5d2e4b1f5ea8957f403b4425dfa156bf39ede7a98807d25828d7d9dc0232dd69 SHA512 (FreeBSD-14.0-RC4-amd64.vmdk.xz) = 3787cf9de0a5f4b8ae358f2316ddf62493aa6b30d70f6af2108a1730e9d79e07ef847932d7fa42b11f6f5b8b9eb3f33f41c701a67f2995005afdea053d6ef330 SHA256 (FreeBSD-14.0-RC4-amd64-ufs.qcow2.xz) = b79d9e82e3bf5081efb8159b66b3b3fa0472fefab9389f0ca8e18a469720a5eb SHA256 (FreeBSD-14.0-RC4-amd64-ufs.raw.xz) = c1718eff5c455afc9e689b97751ba577eeff880c1e02ae0ac758dd8452f18977 SHA256 (FreeBSD-14.0-RC4-amd64-ufs.vhd.xz) = f75b814422bfe88ae352d4342a6fce7a7059ae83210c20f3af30ef410bbc7a56 SHA256 (FreeBSD-14.0-RC4-amd64-ufs.vmdk.xz) = 4abcfc77bda9f04fdb83af19d66a3db908dc2eac3983f3169e01b59c7cce3055 SHA256 (FreeBSD-14.0-RC4-amd64-zfs.qcow2.xz) = f99a66864585598496cc43f73deed54f1a4c05552e5f02e8505c71bca743d573 SHA256 (FreeBSD-14.0-RC4-amd64-zfs.raw.xz) = bfcb87a82a02ed1f7ee3bd25885f3d8d51c1c384f56e4ab9ff959fbac600e6ae SHA256 (FreeBSD-14.0-RC4-amd64-zfs.vhd.xz) = 7c3c47e9abf98e406bb3c68dba55cab34a54e50fae5df79afdf9605dc768f0f1 SHA256 (FreeBSD-14.0-RC4-amd64-zfs.vmdk.xz) = 5b0c3e8941ab57d18a9c3bf611158812d413cc9f1191bafdc0874e3b858448d3 SHA256 (FreeBSD-14.0-RC4-amd64.qcow2.xz) = b79d9e82e3bf5081efb8159b66b3b3fa0472fefab9389f0ca8e18a469720a5eb SHA256 (FreeBSD-14.0-RC4-amd64.raw.xz) = c1718eff5c455afc9e689b97751ba577eeff880c1e02ae0ac758dd8452f18977 SHA256 (FreeBSD-14.0-RC4-amd64.vhd.xz) = f75b814422bfe88ae352d4342a6fce7a7059ae83210c20f3af30ef410bbc7a56 SHA256 (FreeBSD-14.0-RC4-amd64.vmdk.xz) = 4abcfc77bda9f04fdb83af19d66a3db908dc2eac3983f3169e01b59c7cce3055 o 14.0-RC4 i386: SHA512 (FreeBSD-14.0-RC4-i386-ufs.qcow2.xz) = 83e9052c4e7bb574ea9763309ddc952a9632cc8b2b8693cf84c3d405e91a2d5c0ce8c9b25947982661537a9fb64a3325449cfb9f18699741328f5f8f446d1407 SHA512 (FreeBSD-14.0-RC4-i386-ufs.raw.xz) = 66f9dca74d1e24869ea85f6ac10868b9197bdb508956168319f25db9ab1e7b13723b48cd544d0b25dc01d898eec127decb06329ca9c3ca9f3b333fd106eed49d SHA512 (FreeBSD-14.0-RC4-i386-ufs.vhd.xz) = 8b0152123fffd4ea9e38b7658eeddf7e6fb69525e68312f3ca0a57efdcc3716113703e94b03da0f6607ef87782599a1da74b588b3b17a934c4299f9b9d62f99a SHA512 (FreeBSD-14.0-RC4-i386-ufs.vmdk.xz) = a894383f188ad274130eb3c6d27d2e8810a502cf4f43544ecead17a61880b7b5a24f3a2709b6251c4139613a9d7e231f6d13b75b2c1413136e76b9ada1b04897 SHA512 (FreeBSD-14.0-RC4-i386-zfs.qcow2.xz) = b02e65d34149f2b21ea8f4d546764f16ad0c96c067f7c7afb685301cf4e4b1d5953f9fbaefdb6b8b2e1ab275d5c201ef1f1e3a2fdb4ce9a60078c133092f6911 SHA512 (FreeBSD-14.0-RC4-i386-zfs.raw.xz) = cfbe7aa6c8339daee268202e95d2c0c385f65debe53a22710c8314beae5a7f6e9cde02920920febf062a6613c84498e6659aa0878b112fb06af7c1a27843fd65 SHA512 (FreeBSD-14.0-RC4-i386-zfs.vhd.xz) = d72284dad778a11cf40be9a91ba1537f32118567e3dcefe40449d225f6f6280746a89b0d15e689db7ed60b54caa4cd69067b303791ab33b47b58ccc854e0c035 SHA512 (FreeBSD-14.0-RC4-i386-zfs.vmdk.xz) = 0e61517e4ff20edb0154bd68a7bff76f6095a4ef63bd1699f4665c39cf4a00d7eea1f9d562e4620c75c1ab982811409032033900e8fdcf892d228fcf49f3a335 SHA512 (FreeBSD-14.0-RC4-i386.qcow2.xz) = 83e9052c4e7bb574ea9763309ddc952a9632cc8b2b8693cf84c3d405e91a2d5c0ce8c9b25947982661537a9fb64a3325449cfb9f18699741328f5f8f446d1407 SHA512 (FreeBSD-14.0-RC4-i386.raw.xz) = 66f9dca74d1e24869ea85f6ac10868b9197bdb508956168319f25db9ab1e7b13723b48cd544d0b25dc01d898eec127decb06329ca9c3ca9f3b333fd106eed49d SHA512 (FreeBSD-14.0-RC4-i386.vhd.xz) = 8b0152123fffd4ea9e38b7658eeddf7e6fb69525e68312f3ca0a57efdcc3716113703e94b03da0f6607ef87782599a1da74b588b3b17a934c4299f9b9d62f99a SHA512 (FreeBSD-14.0-RC4-i386.vmdk.xz) = a894383f188ad274130eb3c6d27d2e8810a502cf4f43544ecead17a61880b7b5a24f3a2709b6251c4139613a9d7e231f6d13b75b2c1413136e76b9ada1b04897 SHA256 (FreeBSD-14.0-RC4-i386-ufs.qcow2.xz) = 6ef1dfcea80aa0687141c7917f0e8ab81c4241a62bee8043ac1dc23c82be05ed SHA256 (FreeBSD-14.0-RC4-i386-ufs.raw.xz) = 5eca8b0ffe97f7e6a485f496a61fad9c93a261c6c4e0d083f9fd1c500c2d4db4 SHA256 (FreeBSD-14.0-RC4-i386-ufs.vhd.xz) = 3997fd89984392f2ca2fc3b7df864dfd0dfc17be750aa78d61a31233e947fc0b SHA256 (FreeBSD-14.0-RC4-i386-ufs.vmdk.xz) = dda9a1962d1cd910465c1c91d36c2df5c923fe7353fffb172c04adaebb368505 SHA256 (FreeBSD-14.0-RC4-i386-zfs.qcow2.xz) = ab840c119d46ab49e2e33f7024f453ef872df908b47a8d9fdca0a8740b49c478 SHA256 (FreeBSD-14.0-RC4-i386-zfs.raw.xz) = 1d2635935bdd73de8e76b8815392a2f0399782aa9e41296bc4dfb9e2073a35aa SHA256 (FreeBSD-14.0-RC4-i386-zfs.vhd.xz) = 998a040e0849ed03a1cbf6da446672525c5ddee79ed225ff7cd8283164b484bf SHA256 (FreeBSD-14.0-RC4-i386-zfs.vmdk.xz) = db11801f993246135e3cd4b28b6c7457853668180ff7d11c4b0c7018e04a58c2 SHA256 (FreeBSD-14.0-RC4-i386.qcow2.xz) = 6ef1dfcea80aa0687141c7917f0e8ab81c4241a62bee8043ac1dc23c82be05ed SHA256 (FreeBSD-14.0-RC4-i386.raw.xz) = 5eca8b0ffe97f7e6a485f496a61fad9c93a261c6c4e0d083f9fd1c500c2d4db4 SHA256 (FreeBSD-14.0-RC4-i386.vhd.xz) = 3997fd89984392f2ca2fc3b7df864dfd0dfc17be750aa78d61a31233e947fc0b SHA256 (FreeBSD-14.0-RC4-i386.vmdk.xz) = dda9a1962d1cd910465c1c91d36c2df5c923fe7353fffb172c04adaebb368505 o 14.0-RC4 aarch64: SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-ufs.qcow2.xz) = 6f67f49ddf46bd4468394c985a2b34bc48f975f659de560a8ca1bd6935c3f27d02bc143632c088580aa440fae5f7f18932b5b335247c3aa328090ddbbc9c70b5 SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-ufs.raw.xz) = ef0af5d2877eaa8e2a6c3ca9df9ac3b9a0e9f30035170eca3ceef1984d35b08ea422254583c08b45cda9453a3e09d7209d85b2093d69768e8c892be67ae5f975 SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-ufs.vhd.xz) = 4b6bc513892b5ebd1cf2206014da0b548ddfbedb1a5fa8349fa5ddfd6363afb68f104bdc6d5447476f70ad61b27202a390cf6f5d7c5cf90c415edfe3ce0bc26d SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-ufs.vmdk.xz) = fece4ca62f30260beee2de4265f3c6559ba0a948e6dcf65658016ee10aa961136fbacc7238a6ea3b6e9afe334879cdfbcfe23f31d012a9abfca86c6783ea6a10 SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-zfs.qcow2.xz) = cb21c41ad4e1e09e58bc00cc55c6e5decdf2d01e29ef7031e4497532bb33ced39473390141292d8819eb59f9f49b880c8d6d269d879c4f3b671e646968c83d32 SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-zfs.raw.xz) = c33a58f30eb6f798cb353e11ad821ac9927852f6262617bb7340b963448ad83e4b4fe039676e1e48a5618db4e00ee6bc209b32809e3e70395114935189493e24 SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-zfs.vhd.xz) = 4bb8cc4d313d14247701b7fa0bc920c2c5fd467126b961a5ecbc791c928730440c87dc452ecbc653db26fda482d86b0be87cd0f6ba272c2036ee3146096c70fc SHA512 (FreeBSD-14.0-RC4-arm64-aarch64-zfs.vmdk.xz) = 5a49668bebd971fdc1145adb69edb5dd4aa521ca1a86d1532f43b58c1b3aed23c4187ce23366cc182fae296cc17a31b00858660522bb2897746f519ce5ddf3eb SHA512 (FreeBSD-14.0-RC4-arm64-aarch64.qcow2.xz) = 6f67f49ddf46bd4468394c985a2b34bc48f975f659de560a8ca1bd6935c3f27d02bc143632c088580aa440fae5f7f18932b5b335247c3aa328090ddbbc9c70b5 SHA512 (FreeBSD-14.0-RC4-arm64-aarch64.raw.xz) = ef0af5d2877eaa8e2a6c3ca9df9ac3b9a0e9f30035170eca3ceef1984d35b08ea422254583c08b45cda9453a3e09d7209d85b2093d69768e8c892be67ae5f975 SHA512 (FreeBSD-14.0-RC4-arm64-aarch64.vhd.xz) = 4b6bc513892b5ebd1cf2206014da0b548ddfbedb1a5fa8349fa5ddfd6363afb68f104bdc6d5447476f70ad61b27202a390cf6f5d7c5cf90c415edfe3ce0bc26d SHA512 (FreeBSD-14.0-RC4-arm64-aarch64.vmdk.xz) = fece4ca62f30260beee2de4265f3c6559ba0a948e6dcf65658016ee10aa961136fbacc7238a6ea3b6e9afe334879cdfbcfe23f31d012a9abfca86c6783ea6a10 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-ufs.qcow2.xz) = afbc7e756418a70a28c77d3a50022fedbce08a2dc3861a1faf19273d75d8d893 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-ufs.raw.xz) = 100ddb13b6952293e9ea6678b6b4dacb350642036d95b3c6aa2b6d03f653e3b2 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-ufs.vhd.xz) = 3c6c44ffd9dbacce38e41ee2a3dbea86c2a1630c4e0f1e4157d6a9ae35045330 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-ufs.vmdk.xz) = 725b3e4f834f3aa296efef28524dca72e6e3a366afe9a70f66f872446d620417 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-zfs.qcow2.xz) = b064cb8feeee25caf7b87634ec2d2111dc8f264dbc433e41249d2620b06f5c6b SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-zfs.raw.xz) = ebb407772250fdfb179bad97483233378fc63cc72ccd3dbcf01163968bfbd68e SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-zfs.vhd.xz) = 406a87f32a192a00077c071d295c749c166b8ad110d28f509a1f163d8b1c9358 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64-zfs.vmdk.xz) = c8be970e5337d282b45c097bb30b2d2a9eb469402cc9ffa6b7f2ee9c3bbfdb65 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64.qcow2.xz) = afbc7e756418a70a28c77d3a50022fedbce08a2dc3861a1faf19273d75d8d893 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64.raw.xz) = 100ddb13b6952293e9ea6678b6b4dacb350642036d95b3c6aa2b6d03f653e3b2 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64.vhd.xz) = 3c6c44ffd9dbacce38e41ee2a3dbea86c2a1630c4e0f1e4157d6a9ae35045330 SHA256 (FreeBSD-14.0-RC4-arm64-aarch64.vmdk.xz) = 725b3e4f834f3aa296efef28524dca72e6e3a366afe9a70f66f872446d620417 o 14.0-RC4 riscv64: SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-ufs.qcow2.xz) = 2538e1fa6d9c975d0ab2b680e634441209f8c2fdc2ad95f3431ead256185397cf7f639e2523753d4cee1b4f677499815538486b20d3684f9210e492dd0675b1a SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-ufs.raw.xz) = 96a49721ba1428b8cddf65abed849ff3567e31773fc2446f021dd67f61b92a231939a1d5abea28995d1ec8af9d8ba891b881f7ec8b6530a2182e570cb5e78042 SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-ufs.vhd.xz) = d2aacdcefecee3cd8456d7f371a2f5254ddebbd22277d978b00baa9c23304239df1fcec89531644db575f0481b19ccdbfeaa66aa85f17e8651ec164afc4842a2 SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-ufs.vmdk.xz) = e6bacea877352f5ff3fc16f5717e3944927753a5c64e7d237bf5c6c253f85dfe3011314d286198ae7c62d921cc2d7b00398767e207793c4b968f7071ea706858 SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-zfs.qcow2.xz) = 8681d7bee0b60bee27e113c9b0c6601b640a8d49218280511d55aa38b6bcf1d873911de3beedae61be1c2e11244c384239c9d06bd8ebf7f081c0975621af44aa SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-zfs.raw.xz) = 2812d912f583dc574074c4c49f2d6005d60dbf0515c310a49858788bdea2b3f016091937acf67a80d1bcc123133f1f4585fd9a90ebd10b3fd2cfa2954d2a7b0b SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-zfs.vhd.xz) = 8cc13a0ccc40262c99e0dd8b71965cf7150e5ddab6fb754a8e46bb448ed7f8fda63aa79b132502cf890be0bc1141dddfebf77c3cb2d20e2edee050428cf138e8 SHA512 (FreeBSD-14.0-RC4-riscv-riscv64-zfs.vmdk.xz) = e71bb6d4f17e709289f6cc853a72e18a5b61c99e747064bae0e356ab9b1893cb97183ff971892eba1658bcf50bbea40c55827c579643ef88b2799b4f13d5d364 SHA512 (FreeBSD-14.0-RC4-riscv-riscv64.qcow2.xz) = 2538e1fa6d9c975d0ab2b680e634441209f8c2fdc2ad95f3431ead256185397cf7f639e2523753d4cee1b4f677499815538486b20d3684f9210e492dd0675b1a SHA512 (FreeBSD-14.0-RC4-riscv-riscv64.raw.xz) = 96a49721ba1428b8cddf65abed849ff3567e31773fc2446f021dd67f61b92a231939a1d5abea28995d1ec8af9d8ba891b881f7ec8b6530a2182e570cb5e78042 SHA512 (FreeBSD-14.0-RC4-riscv-riscv64.vhd.xz) = d2aacdcefecee3cd8456d7f371a2f5254ddebbd22277d978b00baa9c23304239df1fcec89531644db575f0481b19ccdbfeaa66aa85f17e8651ec164afc4842a2 SHA512 (FreeBSD-14.0-RC4-riscv-riscv64.vmdk.xz) = e6bacea877352f5ff3fc16f5717e3944927753a5c64e7d237bf5c6c253f85dfe3011314d286198ae7c62d921cc2d7b00398767e207793c4b968f7071ea706858 SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-ufs.qcow2.xz) = a20bb128dfcf977a8d8fcbe711287cde37204fed4656b015b55da484825207e3 SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-ufs.raw.xz) = 9b8ceb27d0e67144c3e498f3c0d29857746147acf65262fbea319c5a8c7d038c SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-ufs.vhd.xz) = ee5dc591d890b717d5fef43081d0d9c7050a9d8ae8ce255d68b2a34ff123340b SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-ufs.vmdk.xz) = c37a5c0527a086fc52a81c4699ae0aea4b5a963fc71ce5836b0dc0cbe94fa152 SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-zfs.qcow2.xz) = 23627ae8e397f0de495a0cbe75cec3d98053a0d450c1d8f95c400984f52d9add SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-zfs.raw.xz) = a38a35541f621e59404c32c8ec1f73f1f6a54f554a39230fcc82f963f365543f SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-zfs.vhd.xz) = be9c521b31c7443b46f99f24dab640b6c37da4cf2edee48fc6ecf815be0b8252 SHA256 (FreeBSD-14.0-RC4-riscv-riscv64-zfs.vmdk.xz) = 43506386c53bb76ce5b5b67684a1f36da948fd31a92caa252fa492b3a94e9004 SHA256 (FreeBSD-14.0-RC4-riscv-riscv64.qcow2.xz) = a20bb128dfcf977a8d8fcbe711287cde37204fed4656b015b55da484825207e3 SHA256 (FreeBSD-14.0-RC4-riscv-riscv64.raw.xz) = 9b8ceb27d0e67144c3e498f3c0d29857746147acf65262fbea319c5a8c7d038c SHA256 (FreeBSD-14.0-RC4-riscv-riscv64.vhd.xz) = ee5dc591d890b717d5fef43081d0d9c7050a9d8ae8ce255d68b2a34ff123340b SHA256 (FreeBSD-14.0-RC4-riscv-riscv64.vmdk.xz) = c37a5c0527a086fc52a81c4699ae0aea4b5a963fc71ce5836b0dc0cbe94fa152 o 14.0-RC4 amd64 BASIC-CI: SHA512 (FreeBSD-14.0-RC4-amd64-BASIC-CI.raw.xz) = f553ef24fe92025eee845e54f25c1410883367beba2293c3244516218d9d9f5e3957f1d95643c57e4f97d7a6dc46d6534354ba1284f6a909a532d80e0fc260c4 SHA256 (FreeBSD-14.0-RC4-amd64-BASIC-CI.raw.xz) = 3d0eea50499d49020b9510a26d8df36d0f63ad66b8befb35e42b32943a44a7fe Regards, Glen Please consider donating to help support my FreeBSD work: https://www.gofundme.com/f/gjbbsd https://paypal.me/gjbbsd Love FreeBSD? Support this and future releases with a donation to the FreeBSD Foundation! https://www.freebsdfoundation.org/donate/ -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAmVFhWcACgkQAxRYpUeP 4pMdsQ/+LUr8muc5k7axBIAQdn+uGYkHgj6racCLiGO/aER2ggbH5u3K/P4bbFQ2 Bm4/qGM3ucr+GpdOgGTsfl06jKWtBoD5E969OkDIbRnftIGZwplx9QmpEILRqp22 Ff6J6raJG1SBjIj7sRZB/IhgXQiRlFVmoOFgOcUFIKBoYwffy0/Bh/2jHyBK/hAt FRczo6vn15x/Vom9hFfpu9/VAiGucqMjzLxuMg13YzCNDKyn/T9rhTDAA2Ede2/H E90qzv/er/V+DYRPy9i3/1db3tOrdB/8mKigkeZEEiaF4usVVEQVwlEh1+Cb3kSv ldZTpDEV53jqnp/FekuFjf2sqhSDuFEsYO8pZrcFdK+h8+fDHZBsU0o11TJHjORe G9+Xn8boZLexXKrQZHUNe/YTWpdpciRj9fRMRrf9UvuCyvsxW5qEa29WdZP7Umph ZzcANLTrXt7Uoq2WxmbYjT28aFPEWZ8kiJetSbXowqGxARx7TESexn/lNuHx/0gC MXqN95R2zqULfyFVHF9rFNA0G8QJYkBtAzvdoDiLjojfiL4oI0yDQfvXbshRGB9F YcRRCxc0yz8/mfGuYrvZgaWq4rloLB7ZCR4pF/bTCU23TPrWbHeCxRHohK0BSBqG c2BIT+YW7v/zQax+k5gs8gVNTLWEM3mOiGZbz8Itos+yquLJjkU= =Pcjo -----END PGP SIGNATURE----- From nobody Sat Nov 4 01:28:52 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SMg4Y6fYpz504XT for ; Sat, 4 Nov 2023 01:29:01 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4SMg4Y0Rdvz4c1c; Sat, 4 Nov 2023 01:29:00 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of steffen@sdaoden.eu designates 217.144.132.164 as permitted sender) smtp.mailfrom=steffen@sdaoden.eu; dmarc=none Date: Sat, 04 Nov 2023 02:28:52 +0100 Author: Steffen Nurpmeso From: Steffen Nurpmeso To: Thomas Dickey Cc: Jamie Landeg-Jones , freebsd-current@freebsd.org, bapt@freebsd.org Subject: Re: Freebsd 14+ -- tcsh incompatible with terminfo Message-ID: <20231104012852.ibgGG%steffen@sdaoden.eu> In-Reply-To: References: <202310312245.39VMjNJB080965@donotpassgo.dyslexicfish.net> <202310312259.39VMxm6W081150@donotpassgo.dyslexicfish.net> <202311010349.3A13nX1M094463@donotpassgo.dyslexicfish.net> <20231101220247.HGrrB%steffen@sdaoden.eu> <202311020241.3A22f4o3042181@donotpassgo.dyslexicfish.net> <20231102175855.A1pj0%steffen@sdaoden.eu> Mail-Followup-To: Thomas Dickey , Jamie Landeg-Jones , freebsd-current@freebsd.org, bapt@freebsd.org User-Agent: s-nail v14.9.24-553-gc24c1fad78 OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-1.31 / 15.00]; MID_CONTAINS_FROM(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.97)[-0.971]; R_SPF_ALLOW(-0.20)[+a]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_SHORT(-0.04)[-0.040]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_ZERO(0.00)[0]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_THREE(0.00)[4]; BLOCKLISTDE_FAIL(0.00)[217.144.132.164:server fail]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[sdaoden.eu]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:15987, ipnet:217.144.128.0/20, country:DE] X-Rspamd-Queue-Id: 4SMg4Y0Rdvz4c1c X-Spamd-Bar: - Hello Thomas Dickey. Thomas Dickey wrote in : |On Thu, Nov 02, 2023 at 06:58:55PM +0100, Steffen Nurpmeso wrote: |> I do understand that a bit. Other than that plain termcap was so |> small and i would assume essentially unchanged for decades, that |> i do not. Termcap entries, yes. I could imagine vt220, xterm, |> screen-256color, and take one of st-256color, whatever KDE and |> GNOME terminal, and rxvt-unicode. Makes seven. Likely |> automatically extractable via "infocmp -C" of Dickey's terminfo. |>=20 |> Let's just try that: |>=20 |> $ rm .TCAP;\ |> for f in vt220 xterm screen-256color st-256color \ |> rxvt-256color gnome-256color konsole-256color; do \ |> infocmp -C $f >> .TCAP;\ |> done;\ |> ls -l .TCAP |> -rw-r----- 1 steffen steffen 7145 Nov 2 18:40 .TCAP | |There's more data in termcap than that (which some people would like \ |to use). You know the entire thread is moot as i think bapt@ has thrown away the BSD termcap years ago, if i recall correctly (i think i spoke up by then). I only answered because of the "great it is gone" thing. |And there's additional data for terminfo -- again, some want it. | |man infocmp: | | For best results when converting to termcap format, you should \ | use both | -C and -r. Normally a termcap description is limited to \ | 1023 bytes. And i do not know whether BSD termcap can work with larger ones. | infocmp trims away less essential parts to make it fit. If \ | you are | converting to one of the (rare) termcap implementations which \ | accept an | unlimited size of termcap, you may want to add the -T option. \ Yes. I heard about the limit. | More of=E2=80=90 | ten however, you must help the termcap implementation, and \ | trim excess | whitespace (use the -0 option for that). | |(-T is appropriate here - ymmv) | |With -C alone, I get |-rw------- 1 tom users 7315 Nov 2 21:02 .TCAP | |With -CrT, |-rw------- 1 tom users 14390 Nov 2 21:02 .TCAP | |For terminfo, no options |-rw------- 1 tom users 16027 Nov 2 21:03 .TCAP | |For terminfo with -x |-rw------- 1 tom users 19533 Nov 2 21:03 .TCAP One would have to add that OpenGL-accelerated terminal (allacritty or so) at least, too. I am not speaking against your ncurses and the work and effort you put there, you know, i spent about 30% of my live in front of a st/tmux combination, and i would think tmux uses more and more of the optimizations, and improvements of yours. For example i saw fly by an OpenBSD commit where tmux started using tparm_s or what its name was. They imported some ncurses snapshot only for it (in the end), if i got that right. The function is not on my box -- and i do not "track" ncurses no more because i will likely never reach a point where i need it as such. I was speaking pro BSD termcap. I do not know whether even the omnipresent readline library would need anything more than the absolute basics. I know my mailer can, .. it can even without termcap, .. at least a little bit, and very expensive. (I have not tried that out for years so.) --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) From nobody Sat Nov 4 12:00:49 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SMx5t6V6vz509TK for ; Sat, 4 Nov 2023 12:01:06 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic312-23.consmr.mail.gq1.yahoo.com (sonic312-23.consmr.mail.gq1.yahoo.com [98.137.69.204]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4SMx5r6cN9z3Z1W for ; Sat, 4 Nov 2023 12:01:04 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=bP3GT4hx; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.69.204 as permitted sender) smtp.mailfrom=marklmi@yahoo.com; dmarc=pass (policy=reject) header.from=yahoo.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1699099262; bh=nusVZbEIP7mIpV+w/Dlh/JQE63k1F/z3QuQrgCOx1eY=; h=From:Subject:Date:Cc:To:References:From:Subject:Reply-To; b=bP3GT4hxrSKfds8EwGn+Os4SBGadlpBCEitZeVE7MX6TuKc231WlEZmKB3sW5EZqO5aYnGrase2IyuEibap4o7HacnT1U1aIegLe4jtmdXb9lTHbcmUlsPrhs/6FzAXKcBBdtxEG5un2iXvGHZDlGABz0IbwvBibMgizgdlW6qUmFknIOIkSq7uPuQvBTrbBWC3wt+LH1XqqcKAdPQyIiVgFoopnB+090qfGLTzN4Jn1BL0LM6td3mod63NoZCgczajazQH0NoDEaCtB2uCkXSjhWZeymRFdjbcQpJA5qszHZTUCwYg9NzEiq9h6EcrvVqk5hgxLdY1fZBkHsZ16dA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1699099262; bh=fomoHiZcD/o6UKTDdkR8wPfRoRKKRSsr5koRRrfgMq2=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=S/v5RDJvz0Z1onKxCRUvqE35gpleGBcJp6x1c4WfX1YW8zS+GWO/yMBtM+lxoo7XK6Uv90rvvWcNUel9ZgHCMaaBrM8ZT6nL85iZR/3xX1Z6b1jhO1V9uEI7+S7tQNqRE0hI8dLql+qTPKTlknTPDgFP5SJtlKyzoWsrMKKmLCKZzVRnHHa+Xd/oziZPy5P2Vd0rFjRX7v5Ov6auTFyF6kPUszfj/20hHxKytDGEgNiRjToccawsrGwfb7NZOxpvvU0kTWfQipdHo6iSybySYBp+zF5zJRMOPYXpJ/OF9LYiYDo9/O7vknL8hAmkq6Z9zKJfFvdgmsFJHI8tvRpUzg== X-YMail-OSG: Yv6G.HsVM1kAS2wztmMU6Z9dwmtBXRp7y_9bwePkYGVKiPJgpdp3KDszIN0Rl0C bXqUDs4s5FBgEtWo4zGUJJ_p2QU9dSFYxFmISEdj4bAPY_tSnDOFLNUUtNPdP_5BcWa_C8N3NPBI 3BG4gVrTOoWv2_gNV2zkr05dAo1ZvkDg.V5pNiwjHGJv7JlKiN.qlfCvUPdUBipJQLwBVRSGLXW1 XpEw_V_F6FjRP8VvHyXP3YjoVBYH6aeFKemKxY15zGRURPjI2VnAdg4czwzQmGUthpB10527QdZi id6Cm_LLzccWiJPxmaBh7yxkOqn06tiQ.mp2D3xxrrC9GbqINW009aOz9N0M8dKSpiE.GE.QtdKa tPV7dy.jPfwkyEGFlCk3tjeyoDf1fPY2ziTZz_Vzcoe8wGGVHZBllhDkwQgofKackyHGTpzmfU.. qgnO8IL1o0jBk9eo6AVHKr4Vlv3iktWWtIh2Jl0oDTmDwVh81s.A169vYKa6wP7ndzFwH66RYgQX aUitlEBkBMYGyCU2Nb4vFPhaeceB0ABOOvJeBqRaPAlvbdVoqVgyrwDmAecmFwk9460EZDuJ6bAN 6OhsafGJ_qmGjPr43B4woLzUPvUB16t9_yNl84uY0wLMokuSaA4K9aBAy0vZcwZkgQ7F.RXWOzwG 4jARFew__dZo6k.qSkosXcuAHoXusOkxuy5Cv9YOdwlzMCyWgGDjiImxC72PsLHCUr1dXTahUCHs DAOl85Qm9Bg45exectTpLsWT8g7A1KUGNfm5VszQRDjLbi_nf8GovKnyGOvirODJDt67ZU9g9dvd bgtfDQwR0FadoWFjKqS.gAWnClsXmNJKN8AwXKOuivRZfnzKUE5LOLvbDQtrO0mIICqx_SYbvyzp EErkUfEx577CO5L7ToNuUKcDwmOOMoiRKRN.NSYhk4JeBglC73s.tuUVa5kC6euuEcsZBIbVY6AQ ZOghWM.VK5NPDn1n6d_WdmarsOAtAHzLcjKZY8My8vvd09Rq5ahZt6T_L.Umj3kyCkR9Tj5TP43W hqjhDt_02.RvqW.PiiOofq1Vp2kaChdQa4iL.sl75I.FHvf6sobZUcPYo2c3yTzrgWXH1dkDNBFn 7LFOsNpDOf0bO4ur1NQ9grCeBaepJmE9CecGJn00hb8kKu9CuKt1w.sC1cDlIUYnsSvHk2vxfsBr pgXz2v6RbQV.ryiI4q5ta_p8FFbQfGw1Fy84hjwt_2pWe3UEmBx0Y0rm5jEDNfbZHLBEatvaphso cqkC8KwO9kLFrkNwmEkZBq02lJouDGAd83BV2PomFydSVqEOFxfKpwuOiKG7R_M_7ScWNcDEjQQw hBqrUn5hLDgHDBPg44EAHfvbfwVtrkjjdcf8i0KEBqpojKjxWVJeCnN1u_eaSp1JSVkzEiZjeE5u 4KL6TJeNAx5kc9VO4_2nXXysUBuRiUosANJcoHCciUEv7iXQOCYj6o2Csjq.XN0kvF1Iq6fObRQR j_Rmc4MPDv0I3pUIZbOa6GUgMv1kCLQ16eTX7QICGbayRUgDkis7PpJqPJtAq6ajdmVk36xF_fFr teDKBi5kFq7NBHztQROCbotXJ3iO7L6lwtk0usxEOvCyjIQJEOomcfvJr_mQ0vpE4x4InO5LF8bO ccrewsqEItrhN5p5rxAsVDhtiM.APYZrAZHb78azEJckp8FiUlNdqmwl_xG4SAfvP5xhsAtcrwZ9 ufsBIBl9aRrbSrMyKBwVbzko5MFcWcrcT.d12ik90ETHEg9KaOQCuav2yirk5IfEdq9DtW57sp6c tA7QEPOsyAwYsCULiPUMn2lNgDmbThmuFeV6CqpGk92F8HNiHoZ.Xn08MXg8gAjfwb.D2iwzl65E sVB.2UjWdLvopGDiVR9y4SZswhBCZS7fMTmdYyMHCSd23cPR7TuP8WcC9Hk9Oq5w1bl_savOf8DC tiQO3PIvt007xRMXUbpMpKGGQXZkg7JF8176rjyyu8i06XNjL3qal0uIGE1NeLBbFlVa8XwccqZg Sk.8R8X732KuMBpcrRxFMBW6lD043lr7fSwgB.25aso4W9QpAITQiAvTwfizDxHRT2ZmVgy53ied otGRRacv2tascX03gBT9z_FpIaeBgi.xI0fqjqMGw4LVuJ2hXRQEd1OV8ucrC40E.Qtsk9CsHS4c BjnL5l0LFeT1VBBsLpL98BChrrj92CQdns4Q4qmbUmFThDoXzT3blXq8syBa0Eq7x3U_wubVuma5 UpaJfbJg_zuFPCrqfFTkZVfHnRFmiS0anxvf5qoZtlW9JqHwbm1rX593WhHanbvjTyQP3tZUFWX0 DE6l3aw-- X-Sonic-MF: X-Sonic-ID: 1455f27e-2baa-43e6-828b-89dbe6fc637b Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.gq1.yahoo.com with HTTP; Sat, 4 Nov 2023 12:01:02 +0000 Received: by hermes--production-ne1-56df75844-pr5zc (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID a3da3ff4ff01476dd0fb07b1c2f3b19b; Sat, 04 Nov 2023 12:01:01 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\)) Subject: poudriere bulk -a fails on UFS: "Too many links" under logs/bulk/latest-per-pkg/ and then "Failed: starting" Message-Id: Date: Sat, 4 Nov 2023 05:00:49 -0700 Cc: Kirk McKusick , "bapt@freebsd.org" To: Current FreeBSD , freebsd-fs@freebsd.org, FreeBSD Mailing List X-Mailer: Apple Mail (2.3774.200.91.1.1) References: X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.69.204:from]; BLOCKLISTDE_FAIL(0.00)[98.137.69.204:server fail]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.69.204:from]; FREEMAIL_FROM(0.00)[yahoo.com]; RCPT_COUNT_FIVE(0.00)[5]; TO_DN_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4SMx5r6cN9z3Z1W X-Spamd-Bar: --- Looks like there are too many ports for "poudiere bulk -a" to work on = UFS: more than 32767 directory files to go in the likes of = logs/bulk/latest-per-pkg/ as an example. Context: # uname -apKU you have mail FreeBSD amd64-UFS 15.0-CURRENT FreeBSD 15.0-CURRENT #126 = main-n266130-d521abdff236-dirty: Tue Oct 24 18:17:40 PDT 2023 = root@amd64-ZFS:/usr/obj/BUILDs/main-amd64-nodbg-clang/usr/main-src/amd64.a= md64/sys/GENERIC-NODBG amd64 amd64 1500002 1500002 =3D> 40 2930277088 nda1 GPT (1.4T) 40 2008 - free - (1.0M) 2048 532480 1 efi (260M) 534528 1562624 - free - (763M) 2097152 2919235584 2 freebsd-ufs (1.4T) 2921332736 8944392 - free - (4.3G) # ~/fbsd-based-on-what-commit.sh -C /usr/ports 6ec8e3450b29 (HEAD -> main, freebsd/main, freebsd/HEAD) devel/sdts++: = Mark DEPRECATED Author: Muhammad Moinur Rahman Commit: Muhammad Moinur Rahman CommitDate: 2023-10-21 19:01:38 +0000 branch: main merge-base: 6ec8e3450b29462a590d09fb0b07ed214d456bd5 merge-base: CommitDate: 2023-10-21 19:01:38 +0000 n637598 (--first-parent --count for merge-base) # ls -a /usr/local/poudriere/data/logs/bulk/latest-per-pkg/ | wc -l 32767 =46rom the bulk -a output: . . . [30:24:09] [32] [00:00:42] Finished devel/p5-DateTime-Calendar-Hebrew | = p5-DateTime-Calendar-Hebrew-0.05_1: Success [30:24:10] [32] [00:00:00] Building dns/knot3 | knot3-3.3.1 mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/knot3: Too = many links [30:24:13] [23] [00:00:22] Finished sysutils/ttyload | ttyload-0.5.3_1: = Success [30:24:14] [05] [00:01:44] Finished deskutils/mytetra | mytetra-1.43.27: = Success [30:24:15] [23] [00:00:01] Building audio/komposter | = komposter-g20201211_1 [30:24:16] [05] [00:00:00] Building devel/pear-SebastianBergmann_PHPCPD = | php81-pear-SebastianBergmann_PHPCPD-2.0.0 [30:24:16] [08] [00:18:43] Finished mail/cyrus-imapd36@http | = cyrus-imapd36-http-3.6.3: Success mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/komposter: Too = many links [30:24:17] [08] [00:00:00] Building sysutils/p5-Samba-SIDhelper | = p5-Samba-SIDhelper-0.0.0_3 mkdir: = /usr/local/poudriere/data/logs/bulk/latest-per-pkg/php81-pear-SebastianBer= gmann_PHPCPD: Too many links [30:24:18] [19] [00:00:38] Finished devel/p5-Test-WWW-Mechanize-CGIApp | = p5-Test-WWW-Mechanize-CGIApp-0.05_1: Success [30:24:18] [12] [00:00:24] Finished net-mgmt/p5-Mon | p5-Mon-0.11_1: = Success [30:24:19] [19] [00:00:00] Building mail/squirrelmail-plugins@php82 | = squirrelmail-plugins-php82-1.0_2 [30:24:19] [12] [00:00:00] Building security/bsmtrace | bsmtrace-1.4_1 mkdir: = /usr/local/poudriere/data/logs/bulk/latest-per-pkg/p5-Samba-SIDhelper: = Too many links mkdir: = /usr/local/poudriere/data/logs/bulk/latest-per-pkg/squirrelmail-plugins-ph= p82: Too many links mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/bsmtrace: Too = many links [30:24:24] [17] [00:00:29] Finished devel/p5-Class-Delegation | = p5-Class-Delegation-1.9.0: Success [30:24:24] [17] [00:00:00] Building devel/py-memory-profiler@py39 | = py39-memory-profiler-0.61.0 [30:24:25] [13] [00:00:21] Finished converters/nomyso | nomyso-4.3: = Success [30:24:25] [13] [00:00:00] Building devel/rubygem-aws-sdk | = rubygem-aws-sdk-3.1.0 mkdir: = /usr/local/poudriere/data/logs/bulk/latest-per-pkg/py39-memory-profiler: = Too many links mkdir: = /usr/local/poudriere/data/logs/bulk/latest-per-pkg/rubygem-aws-sdk: Too = many links [30:24:29] [16] [00:15:52] Finished games/sauerbraten | = sauerbraten-20201221_2: Success [30:24:30] [16] [00:00:00] Building lang/ccl | ccl-1.12_2 [30:24:30] [20] [00:09:58] Finished security/sssd@default | = sssd-1.16.5_10: Success mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/ccl: Too many = links [30:24:33] [20] [00:00:00] Building games/xpired | xpired-1.22_24 [30:24:33] [18] [00:01:12] Finished irc/miau | miau-0.6.6_3: Success [30:24:34] [18] [00:00:00] Building textproc/rubygem-nokogumbo | = rubygem-nokogumbo-2.0.5_2 mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/xpired: Too = many links mkdir: = /usr/local/poudriere/data/logs/bulk/latest-per-pkg/rubygem-nokogumbo: = Too many links [30:24:39] [22] [00:01:12] Finished net/zsync | zsync-0.6.2_2: Success [30:24:39] [22] [00:00:00] Building devel/distcc | distcc-3.4 mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/distcc: Too = many links [30:24:49] [01] [00:05:11] Finished audio/myxer | myxer-1.2.1_26: = Success [30:24:50] [01] [00:00:00] Building security/theonionbox | = theonionbox-4.3.1_2 mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/theonionbox: = Too many links [30:24:56] [21] [00:01:41] Finished dns/knock | knockpy-5.4.0_2: Success [30:24:57] [29] [00:01:56] Finished games/meandmyshadow | = meandmyshadow-0.5a_2: Success [30:24:58] [21] [00:00:00] Building biology/phyml | = phyml-3.3.20220408_1,1 [30:24:58] [29] [00:00:00] Building security/globalprotect-openconnect | = globalprotect-openconnect-1.4.9_1 mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/phyml: Too = many links mkdir: = /usr/local/poudriere/data/logs/bulk/latest-per-pkg/globalprotect-openconne= ct: Too many links [30:25:00] [06] [00:01:21] Finished www/mod_auth_openidc | = ap24-mod_auth_openidc-2.4.14.2: Success [30:25:00] [06] [00:00:00] Building net-mgmt/torrus | torrus-2.09_2 mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/torrus: Too = many links [30:25:03] [24] [00:02:29] Finished www/dooble@qt5 | = dooble-qt5-2023.08.30: Success [30:25:03] [24] [00:00:00] Building games/openarena-oax | = openarena-oax-B51_1 mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/openarena-oax: = Too many links [30:25:19] [28] [00:02:11] Finished www/npm-node20 | npm-node20-10.2.0: = Success [30:25:20] [28] [00:00:00] Building editors/hexcurse | hexcurse-1.60.0 mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/hexcurse: Too = many links [30:25:27] [25] [00:16:04] Finished mail/cyrus-imapd34@http | = cyrus-imapd34-http-3.4.6: Success [30:25:27] [25] [00:00:00] Building www/rustypaste-cli | = rustypaste-cli-0.8.0 mkdir: = /usr/local/poudriere/data/logs/bulk/latest-per-pkg/rustypaste-cli: Too = many links [30:25:39] [10] [00:01:34] Finished misc/lightgbm | lightgbm-4.1.0: = Success [30:25:40] [10] [00:00:00] Building audio/mkcue | mkcue-1 mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/mkcue: Too = many links [30:26:10] [01] [30:26:10] Finished security/theonionbox | = theonionbox-4.3.1_2: Failed: starting [30:26:11] [05] [30:26:11] Finished devel/pear-SebastianBergmann_PHPCPD = | php81-pear-SebastianBergmann_PHPCPD-2.0.0: Failed: starting [30:26:11] [01] [00:00:00] Building editors/openoffice-4 | = apache-openoffice-4.1.14_3 [30:26:12] [06] [30:26:12] Finished net-mgmt/torrus | torrus-2.09_2: = Failed: starting [30:26:12] [05] [00:00:00] Building databases/pgreplay | = pgreplay-1.3.0_2 mkdir: = /usr/local/poudriere/data/logs/bulk/latest-per-pkg/apache-openoffice: = Too many links [30:26:13] [08] [30:26:13] Finished sysutils/p5-Samba-SIDhelper | = p5-Samba-SIDhelper-0.0.0_3: Failed: starting [30:26:13] [06] [00:00:00] Building cad/qflow | qflow-1.4.100_1 mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/pgreplay: Too = many links [30:26:14] [10] [30:26:14] Finished audio/mkcue | mkcue-1: Failed: = starting [30:26:14] [08] [00:00:00] Building sysutils/mcweject | mcweject-1.1 [30:26:14] [10] [00:00:00] Building devel/pear-Net_Gearman@php83 | = php83-pear-Net_Gearman-0.2.3_3 [30:26:14] [12] [30:26:14] Finished security/bsmtrace | bsmtrace-1.4_1: = Failed: starting mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/qflow: Too = many links mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/mcweject: Too = many links [30:26:15] [13] [30:26:15] Finished devel/rubygem-aws-sdk | = rubygem-aws-sdk-3.1.0: Failed: starting [30:26:15] [12] [00:00:00] Building net/cloud-init-devel@py39 | = py39-cloud-init-devel-23.3.1 mkdir: = /usr/local/poudriere/data/logs/bulk/latest-per-pkg/php83-pear-Net_Gearman:= Too many links [30:26:16] [11] [00:02:11] Finished japanese/font-plemoljp | = ja-font-plemoljp-1.6.0: Success [30:26:16] [16] [30:26:16] Finished lang/ccl | ccl-1.12_2: Failed: = starting [30:26:16] [13] [00:00:00] Building devel/py-pyupgrade@py39 | = py39-pyupgrade-3.15.0 mkdir: = /usr/local/poudriere/data/logs/bulk/latest-per-pkg/py39-cloud-init-devel: = Too many links mkdir: = /usr/local/poudriere/data/logs/bulk/latest-per-pkg/py39-pyupgrade: Too = many links [30:26:18] [16] [00:00:00] Building lang/frawk | frawk-0.4.7 [30:26:18] [17] [30:26:18] Finished devel/py-memory-profiler@py39 | = py39-memory-profiler-0.61.0: Failed: starting [30:26:19] [18] [30:26:19] Finished textproc/rubygem-nokogumbo | = rubygem-nokogumbo-2.0.5_2: Failed: starting [30:26:19] [17] [00:00:00] Building net/rubygem-google-cloud-spanner | = rubygem-google-cloud-spanner-2.18.1 mkdir: /usr/local/poudriere/data/logs/bulk/latest-per-pkg/frawk: Too = many links mkdir: = /usr/local/poudriere/data/logs/bulk/latest-per-pkg/rubygem-google-cloud-sp= anner: Too many links [30:26:20] [18] [00:00:00] Building www/p5-HTML-Widgets-SelectLayers | = p5-HTML-Widgets-SelectLayers-0.07_2 [30:26:20] [19] [30:26:20] Finished mail/squirrelmail-plugins@php82 | = squirrelmail-plugins-php82-1.0_2: Failed: starting . . . # poudriere status -b [main-amd64-bulk_a-default] [2023-11-02_21h44m56s] [parallel_build:] = Queued: 34683 Built: 32285 Failed: 1038 Skipped: 366 Ignored: 320 = Fetched: 0 Tobuild: 674 Time: 30:50:53 ID TOTAL ORIGIN PKGNAME = PHASE PHASE TMPFS CPU% MEM% [29] 00:00:30 misc/swissfileknife | = swissfileknife-1.9.9.0 starting 00:00:30 1.28 GiB = [15] 00:52:19 cad/kicad-library-packages3d | = kicad-library-packages3d-7.0.2_2 package 00:48:06 16.55 = GiB 100% 0.1% [30] 00:00:30 sysutils/mac_rtprio | = mac_rtprio-kmod-g20170417 starting 00:00:30 1.28 GiB = [01] 00:00:00 net/nakenchat | = nakenchat-3.00.b1 starting 00:00:00 1.43 GiB = [16] 00:00:31 ports-mgmt/pkgs_which | = pkgs_which-0.4.1 starting 00:00:31 1.28 GiB = [31] 00:00:30 x11-themes/Kvantum | = Kvantum-qt5-1.0.10 starting 00:00:30 1.28 GiB = [02] 00:00:00 graphics/pear-Image_Barcode@php83 | = php83-pear-Image_Barcode-1.1.3 starting 00:00:00 1.43 GiB = [17] 00:00:31 games/egoboo | = egoboo-2.8.1_1,1 starting 00:00:31 1.28 GiB = [32] 00:00:30 textproc/fa-aspell | = fa-aspell-0.11.0_1,2 starting 00:00:30 1.28 GiB = [03] 00:00:00 comms/sigdigger | = sigdigger-0.3.0.1_1 starting 00:00:00 1.39 GiB = [18] 00:00:31 devel/py-pdoc@py39 | = py39-pdoc-14.1.0 starting 00:00:31 1.28 GiB = [04] 00:00:00 graphics/pecl-qrencode@php80 | = php80-pecl-qrencode-0.11 starting 00:00:00 1.31 GiB = [19] 00:00:31 devel/websvn@php81 | = websvn-php81-2.8.2_1 starting 00:00:31 1.28 GiB = [05] 00:00:00 mail/squirrelmail-quota_usage-plugin@php82 | = squirrelmail-quota_usage-plugin-php82-1.3.1_3 starting 00:00:00 1.28 GiB = [20] 00:00:31 textproc/p5-Text-DHCPLeases | = p5-Text-DHCPLeases-1.0_1 starting 00:00:31 1.28 GiB = [06] 00:00:00 textproc/html2fo | = html2fo-0.4.2 starting 00:00:00 1.29 GiB = [21] 00:00:31 graphics/partio | = partio-1.14.6_2 starting 00:00:31 1.28 GiB = [07] 00:00:00 math/py-pdal@py39 | = py39-pdal-3.0.2_2 starting 00:00:00 1.28 GiB = [22] 00:00:31 cad/cura | = Cura-4.13.1_4,2 starting 00:00:31 1.28 GiB = [08] 00:00:00 mail/mboxstats | = mboxstats-3.1 starting 00:00:00 1.28 GiB = [23] 00:00:31 textproc/p5-Text-HikiDoc | = p5-Text-HikiDoc-1.023 starting 00:00:31 1.28 GiB = [09] = crashed = [24] 00:00:31 lang/zephir@php81 | = php81-zephir-0.17.0 starting 00:00:31 1.28 GiB = [10] 00:00:32 databases/php-xapian@php82 | = php82-xapian-1.4.23 starting 00:00:32 1.28 GiB = [25] 00:00:31 security/stegify | = stegify-1.2.2_14 starting 00:00:31 1.28 GiB = [11] 00:00:32 science/py-qspin@py39 | = py39-qspin-2.3.3 starting 00:00:32 1.28 GiB = [26] 02:08:19 emulators/libretro-mame | = libretro-mame-20220124_1 build 02:06:29 3.67 GiB = 0% 0.1% [12] 00:00:32 devel/pear-PEAR_Info@php83 | = php83-pear-PEAR_Info-1.9.2_4 starting 00:00:32 1.28 GiB = [27] 00:00:30 www/moodle42@php82 | = moodle42-php82-4.2.3 starting 00:00:30 1.28 GiB = [13] 00:00:32 sysutils/luckybackup | = luckybackup-0.5.0_2 starting 00:00:32 1.28 GiB = [28] 00:00:30 news/mmail | = mmail-0.52 starting 00:00:30 1.28 GiB = [14] 00:00:32 math/giacxcas | = giacxcas-1.9.0.55 starting 00:00:32 1.28 GiB = =3D>> Logs: = /usr/local/poudriere/data/logs/bulk/main-amd64-bulk_a-default/2023-11-02_2= 1h44m56s =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Sat Nov 4 12:05:03 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SMxBZ6xKcz509mG for ; Sat, 4 Nov 2023 12:05:10 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4SMxBZ45lhz3cSj; Sat, 4 Nov 2023 12:05:10 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; none X-Catflap-Envelope-From: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 3A4C54A6062640; Sat, 4 Nov 2023 12:05:04 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 3A4C53tT062639; Sat, 4 Nov 2023 12:05:03 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202311041205.3A4C53tT062639@donotpassgo.dyslexicfish.net> Date: Sat, 04 Nov 2023 12:05:03 +0000 Organization: Dyslexic Fish To: steffen@sdaoden.eu, dickey@his.com Cc: jamie@catflap.org, freebsd-current@freebsd.org, bapt@freebsd.org Subject: Re: Freebsd 14+ -- tcsh incompatible with terminfo References: <202310312245.39VMjNJB080965@donotpassgo.dyslexicfish.net> <202310312259.39VMxm6W081150@donotpassgo.dyslexicfish.net> <202311010349.3A13nX1M094463@donotpassgo.dyslexicfish.net> <20231101220247.HGrrB%steffen@sdaoden.eu> <202311020241.3A22f4o3042181@donotpassgo.dyslexicfish.net> <20231102175855.A1pj0%steffen@sdaoden.eu> <20231104012852.ibgGG%steffen@sdaoden.eu> In-Reply-To: <20231104012852.ibgGG%steffen@sdaoden.eu> User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Sat, 04 Nov 2023 12:05:04 +0000 (GMT) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US] X-Rspamd-Queue-Id: 4SMxBZ45lhz3cSj Steffen Nurpmeso wrote: > You know the entire thread is moot as i think bapt@ has thrown > away the BSD termcap years ago, if i recall correctly (i think > i spoke up by then). > I only answered because of the "great it is gone" thing. Maybe I should have rephrased that as "it's great that we only now have one to deal with, that is the same as most other POSIX systems use." It was not a dig against termcap per se. Jamie