From nobody Sun Jul 23 02:43:39 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 4R7nfq39fGz4nXWM for ; Sun, 23 Jul 2023 02:43:47 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail2.karels.net (mail2.karels.net [3.19.118.201]) (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 (2048 bits) client-digest SHA256) (Client CN "freebsd", Issuer "freebsd" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R7nfp48nGz4Hf7 for ; Sun, 23 Jul 2023 02:43:46 +0000 (UTC) (envelope-from mike@karels.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=karels.net header.s=mail2 header.b="LPpCG/LU"; spf=pass (mx1.freebsd.org: domain of mike@karels.net designates 3.19.118.201 as permitted sender) smtp.mailfrom=mike@karels.net; dmarc=none Received: from mail2.karels.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail2.karels.net (8.17.1/8.17.1) with ESMTP id 36N2hdHt061287; Sat, 22 Jul 2023 21:43:40 -0500 (CDT) (envelope-from mike@karels.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=karels.net; s=mail2; t=1690080220; bh=ynAOfYgu3VNs8WZYlB+uF6TL2d7rJGoJLxpdiMm28dY=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=LPpCG/LUjfzWp1qNrDQ8HYCT7YJrFuhAhlI/LZq3xdSpCvksVlCAxzc2HsPICB34B kBQPFnpDyMKZ0UxzgjoP2m5vr0KpUVtOFl+qpeECeaTP4pFutoerXtAGITDpntcMTS duLK95A8kZwheHIHSDeIrPSC8lWRw+kPzHwaqcSbhs6v0V6nzccKI6OnKUx9FfuB5l d706RbdEU4k0BAXfQ+tdlCJYiKAoG07FGrh0jtSgoitZWb4n6xCvgkLylgqT3DKl0T RxUAiD2vpdNcOenMmBGeLCtKC3MCZFC0eDDkPn7FrHadGOVuPwyQ9R5fEMKUZxQOst RThjSyueIEgJw== Received: from [10.0.2.130] ([73.62.165.147]) by mail2.karels.net with ESMTPSA id x6NbNduTvGRl7wAAs/W3XQ (envelope-from ); Sat, 22 Jul 2023 21:43:39 -0500 From: Mike Karels To: Mateusz Guzik Cc: Current FreeBSD Subject: Re: confusion about root partition causes panic during startup Date: Sat, 22 Jul 2023 21:43:39 -0500 X-Mailer: MailMate (1.14r5964) Message-ID: <6DAF78D1-BAFF-49E4-9B42-9480A901A05A@karels.net> In-Reply-To: <202307210237.36L2bjqk049891@mail2.karels.net> References: <202307210237.36L2bjqk049891@mail2.karels.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 X-Spamd-Result: default: False [-3.38 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; NEURAL_HAM_SHORT(-0.88)[-0.884]; R_SPF_ALLOW(-0.20)[+ip4:3.19.118.201]; R_DKIM_ALLOW(-0.20)[karels.net:s=mail2]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_TO(0.00)[gmail.com]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[karels.net:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ASN(0.00)[asn:16509, ipnet:3.16.0.0/14, country:US]; FREEFALL_USER(0.00)[mike]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[karels.net]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4R7nfp48nGz4Hf7 X-Spamd-Bar: --- Are you planning to commit the change to mountroot? Mike On 20 Jul 2023, at 21:37, Mike Karels wrote: > Mateusz Guzik wrote: >> On 7/20/23, Mike Karels wrote: >>> I installed an additional NVME drive on a system, and then booted. It >>> turns >>> out that the new drive became nda0, renumbering the other drives. The >>> loader >>> found the correct partition to boot (the only choice), and loaded the >>> kernel >>> correctly. However, /etc/fstab still had the old name (nvd1p2), which is >>> now drive 2. I expected it to drop into single user, but instead the >>> system >>> panicked in vfs_mountroot_shuffle trying to switch root devices (see >>> below). >>> It doesn't seem that having the wrong root device in /etc/fstab should >>> cause >>> a panic; it makes it harder to patch the system. I was unable to get the >>> system to boot using boot-to-single-user or setting currdev, but I managed >>> to remember doing "boot -a" from a loader prompt to get the system to ask >>> the root device before mounting it. I can easily reproduce this to test. >>> Probably the NDFREE_PNBUF() shouldn't happen if namei() returned an error. >>> > >> ye, this should do it (untested): > >> diff --git a/sys/kern/vfs_mountroot.c b/sys/kern/vfs_mountroot.c >> index 956d29e3f084..85398ff781e4 100644 >> --- a/sys/kern/vfs_mountroot.c >> +++ b/sys/kern/vfs_mountroot.c >> @@ -352,13 +352,13 @@ vfs_mountroot_shuffle(struct thread *td, struct >> mount *mpdevfs) >> NDINIT(&nd, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, fspath); >> error = namei(&nd); >> if (error) { >> - NDFREE_PNBUF(&nd); >> fspath = "/mnt"; >> NDINIT(&nd, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, >> fspath); >> error = namei(&nd); >> } >> if (!error) { >> + NDFREE_PNBUF(&nd); >> vp = nd.ni_vp; >> error = (vp->v_type == VDIR) ? 0 : ENOTDIR; >> if (!error) >> @@ -376,7 +376,6 @@ vfs_mountroot_shuffle(struct thread *td, struct >> mount *mpdevfs) >> } else >> vput(vp); >> } >> - NDFREE_PNBUF(&nd); > >> if (error) >> printf("mountroot: unable to remount previous root " >> @@ -387,6 +386,7 @@ vfs_mountroot_shuffle(struct thread *td, struct >> mount *mpdevfs) >> NDINIT(&nd, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, "/dev"); >> error = namei(&nd); >> if (!error) { >> + NDFREE_PNBUF(&nd); >> vp = nd.ni_vp; >> error = (vp->v_type == VDIR) ? 0 : ENOTDIR; >> if (!error) > > That was missing the last change, and tabs were expanded. I put it in > by hand, and the patch works, at least to avoid this panic. It still > insisted on remounting root on nda1p2, which is not a root file system. > Remounting /dev still failed without panicking, then it panicked because > there was no /sbin/init. Apparently it is necessary to use "boot -a" > in this situation. Too bad the loader option menu doesn't include that. > > Just to be clear what I tested, my patch follows. > > Mike > > diff --git a/sys/kern/vfs_mountroot.c b/sys/kern/vfs_mountroot.c > index 956d29e3f084..b08b2a3200f8 100644 > --- a/sys/kern/vfs_mountroot.c > +++ b/sys/kern/vfs_mountroot.c > @@ -352,13 +352,13 @@ vfs_mountroot_shuffle(struct thread *td, struct mount *mpdevfs) > NDINIT(&nd, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, fspath); > error = namei(&nd); > if (error) { > - NDFREE_PNBUF(&nd); > fspath = "/mnt"; > NDINIT(&nd, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, > fspath); > error = namei(&nd); > } > if (!error) { > + NDFREE_PNBUF(&nd); > vp = nd.ni_vp; > error = (vp->v_type == VDIR) ? 0 : ENOTDIR; > if (!error) > @@ -376,7 +376,6 @@ vfs_mountroot_shuffle(struct thread *td, struct mount *mpdevfs) > } else > vput(vp); > } > - NDFREE_PNBUF(&nd); > > if (error) > printf("mountroot: unable to remount previous root " > @@ -387,6 +386,7 @@ vfs_mountroot_shuffle(struct thread *td, struct mount *mpdevfs) > NDINIT(&nd, LOOKUP, FOLLOW | LOCKLEAF, UIO_SYSSPACE, "/dev"); > error = namei(&nd); > if (!error) { > + NDFREE_PNBUF(&nd); > vp = nd.ni_vp; > error = (vp->v_type == VDIR) ? 0 : ENOTDIR; > if (!error) > @@ -413,7 +413,6 @@ vfs_mountroot_shuffle(struct thread *td, struct mount *mpdevfs) > if (error) > printf("mountroot: unable to remount devfs under /dev " > "(error %d)\n", error); > - NDFREE_PNBUF(&nd); > > if (mporoot == mpdevfs) { > vfs_unbusy(mpdevfs); From nobody Mon Jul 24 11:53:24 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 4R8dpq2ZPVz4nvnj for ; Mon, 24 Jul 2023 11:53:39 +0000 (UTC) (envelope-from otis@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 4R8dpq17ngz4NMn for ; Mon, 24 Jul 2023 11:53:39 +0000 (UTC) (envelope-from otis@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1690199619; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=gofjfi8d+cuO3sYcJB+y9Iec0l2HWnEjbg6xcdF/6JQ=; b=N3QDlSb6etUNk4TTYy7sqmrCQJlzF86KhRqIPblL6knqbFyzUEDkOV9iOidO70/kWF4iq2 S7YMYdbe5iFrvFVtvXS5KsTbKi7Rs1mStgFGuPJbxb+whBm3luTVZT0wRUHlwdgZ6ybL1b TJ+g51ojKbdeoKIbPYA9yDHItz5JWCHNExumnT37nyAi6QgMc7MHBMzxLZI5s2nFv9t9cm rWgH7FJdmHAAATMFhotJlgU5apg3JzblxsiZGFbslXSA6i1z/YkvuI24TAqIhciGRF9A8Z xPi33IAd2T3szIRqedxDtQ9HUR7zVRBDqkTw6pXRGJYCpdWnWmtupuJkOcZvOQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1690199619; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=gofjfi8d+cuO3sYcJB+y9Iec0l2HWnEjbg6xcdF/6JQ=; b=KruvPh9hK0PdcId4q3Q0068TPJvngKQ2hf9LLXUdBi3q8uNsfoEYXAs4xkDlG5pF1/gjoE FHD89OGqiqBJ6QbQ9iS1g0kLiX0sgb/k/8NgnSKxXXplpw4icT18yFsksfm+puuflR35Ah ZHPxUZPn/+Q8LW62zlBgSEbl8uW0STM4+66tIRwWyLm/CpXgTU1xCFIlu0VuFusNtkHzvb 4ZpETqKcYIa5h4q3sxqKY+ufJ8+t/tstPGEqMrpTGaIudGtCU2NxsU7ucyBNZ/X/6TB5G9 1ZLj+1SLT94ZiwqbY3A/SA8YlWtrVqxaSesehbPRB9k1gVhkpmH7qch2A6qlWg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1690199619; a=rsa-sha256; cv=none; b=jdTjPup8hGfmFLA6fUAdlAI+Kg430n/xGS1ytvywcBWrawliFdMSFwKEnuDq1jdPo6o6RU QDXlPA24dJaNbcOptWeHScQTP1bWqMayF3uToicSERHUSI0hHgBlEI93LPZxkQkaQ0hUrv JcCWval5deChte3OAkWJqfrma3wZRiUdDR/3jKikiIvWRS+7J6ZlxSjwCliWA9NPLdw72B 0uZTjmxSy0TWemGozgyVXBjKvZBDMkkGpg6UE048q4lxqDKW3Dwy425/Nl+kGIp0Ziq8dq eWydpFMXiWL7/PVTJYNU4Vud/eBPQtx82MNMOSvi6T/7Wh8Ldk6ETCD0KXAczQ== Received: from ns2.wilbury.net (ns2.wilbury.net [92.60.51.55]) (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 ECDSA (P-256) client-digest SHA256) (Client CN "svc.wilbury.net", Issuer "R3" (verified OK)) (Authenticated sender: otis) by smtp.freebsd.org (Postfix) with ESMTPSA id 4R8dpp61QPz1NFg for ; Mon, 24 Jul 2023 11:53:38 +0000 (UTC) (envelope-from otis@FreeBSD.org) Received: from smtpclient.apple (gw-upc.owhome.net [188.167.168.254]) (Authenticated sender: juraj@lutter.sk) by svc.wilbury.net (Postfix) with ESMTPSA id 167AB6217F for ; Mon, 24 Jul 2023 13:53:35 +0200 (CEST) From: Juraj Lutter Content-Type: text/plain; charset=utf-8 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 \(3731.600.7\)) Subject: LOR in network Message-Id: Date: Mon, 24 Jul 2023 13:53:24 +0200 To: FreeBSD CURRENT X-Mailer: Apple Mail (2.3731.600.7) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=4.0.0 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on ns2.wilbury.net Hi, I=E2=80=99ve seen following LOR in -CURRENT (3a46fe226193) on GENERIC = arm64.aarch64: lock order reversal: 1st 0xffff000041af89e8 tcphash (tcphash, sleep mutex) @ = /usr/src/sys/netinet/tcp_usrreq.c:1513 2nd 0xffff000000f91648 in6_ifaddr_lock (in6_ifaddr_lock, rm) @ = /usr/src/sys/netinet6/in6_src.c:305 lock order tcphash -> in6_ifaddr_lock attempted at: #0 0xffff0000004d64bc at witness_checkorder+0xa98 #1 0xffff00000045fce4 at _rm_rlock_debug+0x130 #2 0xffff00000063f5e8 at in6_selectsrc+0x33c #3 0xffff00000063f260 at in6_selectsrc_socket+0x44 #4 0xffff00000063d314 at in6_pcbconnect+0x228 #5 0xffff000000621f40 at tcp6_connect+0x9c #6 0xffff00000061fa80 at tcp6_usr_connect+0x230 #7 0xffff00000051003c at soconnectat+0xc8 #8 0xffff000000516cfc at kern_connectat+0xc8 #9 0xffff000000516c14 at sys_connect+0xb0 #10 0xffff0000007fa3cc at do_el0_sync+0x520 #11 0xffff0000007d6910 at handle_el0_sync+0x44 =E2=80=94 Juraj Lutter otis@FreeBSD.org From nobody Mon Jul 24 12:29:08 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 4R8fc32wdCz4pScq for ; Mon, 24 Jul 2023 12:29:23 +0000 (UTC) (envelope-from wireless.insecurity@gmail.com) Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 4R8fc25V0hz3NrF for ; Mon, 24 Jul 2023 12:29:22 +0000 (UTC) (envelope-from wireless.insecurity@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=owCpY6sz; spf=pass (mx1.freebsd.org: domain of wireless.insecurity@gmail.com designates 2a00:1450:4864:20::536 as permitted sender) smtp.mailfrom=wireless.insecurity@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-5222a38c0a0so1923365a12.1 for ; Mon, 24 Jul 2023 05:29:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690201761; x=1690806561; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=C7aEnIbHAGZnEa7jqO9/Sbbf7hp/U65bYN7AExFoWO0=; b=owCpY6szlYhwoLphCsXKGQWiwQ6IYE3ed/Wy6Sr2qJtjeG21wPJPBWVtLAa7FVMHto /lYqDHPc6cap0RyDtmjlttGCN7lxRtdB6Cf94r8hLGtu2HqrFex//qv+5jkAUFbfL7sF q2Gw3DdF+u5Z0JFBdwbbnkyFccC6kpacrUQKOfUfiO8p2aGUL6Ft1CbG1oC4zdozVKGH Oq5HullZLz71oDgsECsr8UqHAs0nWLeh+9SlUkJC7GyVEE8cl3nwLtJ26jSsa3WUqe8p s00dO5sp/SAxbeBtDPKgm2d30eirVyzv6noFvcCuB1bdHpZ3YHtj5qiEoTD+8GWGe6Qo F3uA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690201761; x=1690806561; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=C7aEnIbHAGZnEa7jqO9/Sbbf7hp/U65bYN7AExFoWO0=; b=QGCXoIHvbpRjdizeK9Tk5vZ0TkutPE9uCjoEK8hrtFy7GLJPlN2lIKOp29Ws37AO4E UUwR3P/adrLKEN3Xtqb0uPeinCIAEetUpac9O2my1twygz1J96qywgcVNIWtQvFNNVii mZQCpRic0A/uX6jCbnL8fqqQvbbdKfIhUNwNdIYPj/M2EuYC9PqqX71A41xyt9FDbWwQ n+XHkQWztm3o4k35hqJbYQL2FUiQwFEYTCQ1AjI+0Pcgx9uLd904BuRn8QNh4dEKFPTL n0qeDL1W5iUzPMNMIGqJVRXktlciw9HmwMi/OPO9Ah/IYmF0mQNwvPlCPeZC7JVr2eDm 1Kog== X-Gm-Message-State: ABy/qLbxrfee7RJC/JmpnbQwoDzE7fzq8CxcpQH6T6QbQwLxn9OBDxjX emaBwV5HtRWM26fK6NmzIsjIf7ejSzY1f49q6uwLpcrF X-Google-Smtp-Source: APBJJlECMU09TyViSARNoNSjN8llLxmmirk2IBM1NkWC0z9tkpOC2WDe2mZ1C2EoZt4W6TvEmHRM7Biie/sTVPi5R6I= X-Received: by 2002:a17:906:76d4:b0:988:882b:9a3 with SMTP id q20-20020a17090676d400b00988882b09a3mr10168823ejn.36.1690201760645; Mon, 24 Jul 2023 05:29:20 -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 From: Benjamin Cance Date: Mon, 24 Jul 2023 08:29:08 -0400 Message-ID: Subject: Successfully built -Current over the weekend To: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000008ac44406013ac320" X-Spamd-Result: default: False [-3.82 / 15.00]; NEURAL_HAM_LONG(-0.97)[-0.971]; NEURAL_HAM_MEDIUM(-0.93)[-0.934]; NEURAL_HAM_SHORT(-0.91)[-0.912]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::536:from]; ARC_NA(0.00)[]; TAGGED_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4R8fc25V0hz3NrF X-Spamd-Bar: --- --0000000000008ac44406013ac320 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Greetings, thanks for all of your all=E2=80=99s work. I have a laptop I run= FBSD on with the following: I7-10510u with an AX201. So far, everything works though I haven=E2=80=99t tried to get the finger p= rint reader working. Basically Friday, I synced the current tree, cleaned up the no debug kernel file, then make build world; make install world and left it running when I went home. This morning I walked into a crisp new 14-Current install. I=E2=80=99d really like to give back, so I=E2=80=99ll go check the issues! = Cheers all --0000000000008ac44406013ac320 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Greetings, thanks=C2=A0for all of your all=E2=80=99s work. I have a laptop = I run FBSD on with the following:

I7-10510u with an AX201.=C2=A0

So far, everything works though I haven=E2=80=99t tried to get t= he finger print reader working.=C2=A0

Basically Friday, I synced the current tree, cleaned up the n= o debug kernel file, then make build world; make install world and left it = running when I went home.=C2=A0

This morning I walked into a crisp new 14-Current install.=C2=A0<= /div>

I=E2=80=99d really like = to give back, so I=E2=80=99ll go check the issues! Cheers all
--0000000000008ac44406013ac320-- From nobody Tue Jul 25 04:31:24 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 4R93y63khJz4p7dN for ; Tue, 25 Jul 2023 04:31:26 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 4R93y53qtQz3FJy for ; Tue, 25 Jul 2023 04:31:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20221208.gappssmtp.com header.s=20221208 header.b=TcNGbwpW; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2a00:1450:4864:20::532) smtp.mailfrom=wlosh@bsdimp.com; dmarc=none Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-52222562f1eso3609232a12.3 for ; Mon, 24 Jul 2023 21:31:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1690259484; x=1690864284; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=xJM1GdvYcyXl2o/d8iXSx4nYA5rZ+fDusKKvFQhZY9g=; b=TcNGbwpW4j66M9OWbXm7JQqCn07pp3fFm1paPtVqPChGTCXPAwCmDOZPX7KONsxysP /cYYKxrQxrEFGAIP7OgR/gAB6aSW+WR18y4OJhUt9qBQh4xgA2xGA3tlprFzDuKDGAdX BMKiyOho2j2B7tkZUaDnWFK7I73/vhUdzWh85V++Us1BTLYoeX5s/D9pEPYQjH3ysev2 UyJXuTiJLUtFVS1SztfPLeX+6IURKn0XBZk9ol8C8Ilwtpr9HVpTcas4Aoqtq4tL6U91 wsj/JOwxJENUee7CNrvwBvgKG6D6hQU/zwWOwlqkbqI6ZjSOEOione2w0dsBO9tMSjt9 6zVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690259484; x=1690864284; h=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=xJM1GdvYcyXl2o/d8iXSx4nYA5rZ+fDusKKvFQhZY9g=; b=Uy3xa00Ps13z6QBBtVry7G4VKP+I0KF0UwPQ8QYx2FzuHlaD3kShRag9De2ieUZN8Y JEcgzTMoPKU5f0oUNGtJffjl+eJck0ppxj4gpmyZ1C6yg1mugv02oex0FhyRoKe0FT1g SqSLOwkyy9r92jpt4qTfA9noafyacdCey2mamdvDSt9LHsM8eN92o5iYL+1mUQt2GC9B zyuiVlwzRSR1gwNSWF8sX3Een+zKZPfFCLtj56Le52sNycLFjHWQvAGFNnNJnu4VVyyI ruB53um/g3taUgv4NpAVayinyGND4cfV3IUBBybaMhWdn7juqXQD6zYMJiv+2g2wgAXz NtyQ== X-Gm-Message-State: ABy/qLZTD34FzelPmzljUaMX+bNJdisTAHcmu/6xBQA0nVhyDvqnyB4b Zd9sfTghBKkWDlJDnoBMzxHoggfekKdIATRS/2Nkdg== X-Google-Smtp-Source: APBJJlHlZ8E36yuKFDp9/AmB+awq27wFZwdnB0Wos9KuCsXpU1nFQ+uJTZhIFXnuQvoG4opZWBMBBrYESfgwLEOcVBY= X-Received: by 2002:a05:6402:204e:b0:51e:1af0:3a90 with SMTP id bc14-20020a056402204e00b0051e1af03a90mr11023155edb.37.1690259484219; Mon, 24 Jul 2023 21:31:24 -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: In-Reply-To: From: Warner Losh Date: Mon, 24 Jul 2023 22:31:24 -0600 Message-ID: Subject: Re: Heads up: s/u_intXX_t/uintXX_t/ in sys/cam To: scsi@freebsd.org, "freebsd-arch@freebsd.org" , FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000022acbf060148342f" X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20221208.gappssmtp.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::532:from]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_TLS_LAST(0.00)[]; BLOCKLISTDE_FAIL(0.00)[2a00:1450:4864:20::532:server fail]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20221208.gappssmtp.com:+]; RCPT_COUNT_THREE(0.00)[3]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[bsdimp.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4R93y53qtQz3FJy X-Spamd-Bar: -- --00000000000022acbf060148342f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I have just pushed this update into -current. It compiles and boots for me. It should be a giant nop. I plan on MFCing this in a few days unless there's unanticipated turbulence. I have not updated the SIM drivers because most of the u_intXX_t use in these drivers are not related to CAM interfaces. And many of these drivers are vendor code, to various degrees. I think this is the ideal time: Before the 14 branch, when all I need to do is merge to 13 since 12 is about to go out of support. There will never be a better time. Please let me know if I missed anything. or there are problems. Warner On Fri, Jul 7, 2023 at 3:12=E2=80=AFPM Warner Losh wrote: > I plan on finally biting the bullet and moving to the standard uintXX_t. > > I plan on doing this next week, before we branch 14. > > I also plan on MFC'ing these changes (or rather running the same script > and tagging that commit as a MFC). > > This has been talked about forever, and now seems like we have a good lul= l > in things to do it. > > Comments? > > Warner > > --00000000000022acbf060148342f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I have just pushed this update into = -current. It compiles and boots for me. It should be a giant nop. I plan on= MFCing this in a few days unless there's unanticipated turbulence.

I have not updated the SIM drivers because most of th= e u_intXX_t use in these drivers are not related to CAM interfaces. And man= y of these drivers are vendor code, to various degrees.

I think this is the ideal time: Before the 14 branch, when all I need= to do is merge to 13 since 12 is about to go out of support. There will ne= ver be a better time.

Please let me know if I = missed anything. or there are problems.

Warner=

On Fri, Jul 7, 2023 at 3:12=E2=80=AFPM Warner Losh <imp@bsdimp.com> wrote:
I plan on final= ly biting the bullet and moving to the standard uintXX_t.

I plan on doing this next week, before we branch 14.

=
I also plan on=C2=A0 MFC'ing these changes (or rather runnin= g the same script and tagging that commit as a MFC).

This has been talked about forever, and now seems like we have a good lu= ll in things to do it.

Comments?

Warner

--00000000000022acbf060148342f-- From nobody Tue Jul 25 20:26:59 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 4R9T8z3wLMz4pW48 for ; Tue, 25 Jul 2023 20:27:15 +0000 (UTC) (envelope-from dave@dogwood.com) Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 4R9T8y1zznz3LWB for ; Tue, 25 Jul 2023 20:27:14 +0000 (UTC) (envelope-from dave@dogwood.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=dogwood.com header.s=google header.b=PD7CViQI; spf=pass (mx1.freebsd.org: domain of dave@dogwood.com designates 2a00:1450:4864:20::235 as permitted sender) smtp.mailfrom=dave@dogwood.com; dmarc=pass (policy=quarantine) header.from=dogwood.com Received: by mail-lj1-x235.google.com with SMTP id 38308e7fff4ca-2b74209fb60so87179261fa.0 for ; Tue, 25 Jul 2023 13:27:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dogwood.com; s=google; t=1690316831; x=1690921631; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=fEXfxzt4U1oIUTSS3/uEnuQ4+TSrdsePdqkzRPTRXGw=; b=PD7CViQIOrdjFafSHwfFf8g9CJME1pUKfqxnkjy7HQ3QwkB8pU018Z/ovsi9/G9y3K 4icrFGRTMyWXaN4R8LzUB6V+d7KfVAg9fWWWMG+tba1CvC/tlmfsPlCux8DaEB/eLqLi WdEXrRAtjudvYdLx9GZT1uJ5FoUdXwpwNUNBg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690316831; x=1690921631; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=fEXfxzt4U1oIUTSS3/uEnuQ4+TSrdsePdqkzRPTRXGw=; b=Q8/BBJO3kLyBGNYT6oRXu9xtV2m0h1qj84nRCk3eEUdZLZ7KfiZj683RJX3O2OLWue /0+BRHpPpqY/I45CwgzWAosvMvNJXpb9GJfa2ecI3pHjcoAtJjYhNMcaf0kk6XsmJOIK 3DTIx6UylNX2OP2UBkPL3AhYOHkNW44jnHVa4kpIl+rrefKOKoQZHo3xbeoj/5OSEgVj fgjerEO9ZxDX8ydNZfwk3M9uTFnhcIz69YJBLn4uDwUfkmQOuny9HrBPi9UXgbJedaof 4wOJeauoeAKur9Kpqp7e1xWklYSNsAG49G6JTzskrKFqpvSAXJlUdoSJAdiWMxhkOdjs 8z3w== X-Gm-Message-State: ABy/qLYoLYh8GXLraoqRj32m5NDihk7VrgchTuOEEmhzovaHVFLNF6VJ DtPtlADCYngeMzXyrAXgmfuY9AyJUawGEgJu8IaLsTURHdgX6vQKXRg= X-Google-Smtp-Source: APBJJlHqYokS0qPENuYViACLIKe8Bn5iVzhrdg5Z+WZu82QEqpeRG8qskavhXbJrAif50zC73IH7HEhbvplie5CeN/8= X-Received: by 2002:a2e:350d:0:b0:2b6:9f95:46d9 with SMTP id z13-20020a2e350d000000b002b69f9546d9mr8549506ljz.46.1690316830703; Tue, 25 Jul 2023 13:27:10 -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 From: David Cornejo Date: Tue, 25 Jul 2023 10:26:59 -1000 Message-ID: Subject: HST time zone To: FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000040990f0601558e72" X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[dogwood.com,quarantine]; R_DKIM_ALLOW(-0.20)[dogwood.com:s=google]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::235:from]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[dogwood.com:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4R9T8y1zznz3LWB X-Spamd-Bar: --- --00000000000040990f0601558e72 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, One thing that has bothered me for a long time is that the Pacific/Honolulu timezone is found under the America -- North and South/United States of America/Hawaii in tzsetup. Politics of Hawaiian Sovereignty aside, every other system I regularly install uses Pacific/Honolulu as it is in the official tzdb. Is there any reason why a patch to change to match the standard would be refused? thanks, dave c --=20 Honolulu, O=CA=BBahu, Hawai=CA=BBi --00000000000040990f0601558e72 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

One thing that has bothered me for a long time is that th= e Pacific/Honolulu timezone=C2=A0is found under the America -- North and So= uth/United States of America/Hawaii in tzsetup. Politics of Hawaiian Sovere= ignty aside, every other system I regularly install uses Pacific/Honolulu a= s it is in the official tzdb.

Is there any reason why a patch to chang= e to match the standard would be refused?

thanks,
dave c

--
Honolulu, O=CA=BBahu, Hawai=CA=BBi<= /font>

--00000000000040990f0601558e72-- From nobody Tue Jul 25 21: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 4R9Tw46BMtz4nl8Z for ; Tue, 25 Jul 2023 21:01:08 +0000 (UTC) (envelope-from dim@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 4R9Tw459lhz3qL4; Tue, 25 Jul 2023 21:01:08 +0000 (UTC) (envelope-from dim@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1690318868; 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=yAUyHDOepjLRV0jCL0utqP9lIhOR5j2gdwiwkpbbEog=; b=A0yBLSedYqJs03f0jhssYXvMZHtVaGanshz6dmKAuv8Qfq5INRfN7m7rrjt6y/MNDu/4aA oMoKqjARbFjTi1RD52HeGoK14i3HU3wp6srYoGMwIqCI31AHidsgu841IL3tapLyhxfCkb CL+nXYWmoKjjmfqEbOb2WrdDBQtAxEhQv7CBt/sIlujrbsNoMiTyVNr8CNSWaXHdZ/kLRy NnZ6vpOHQZY4pyyUEcP/qgzbIbNU0BK4holb6I+suF5Oo1Rd2DZlgFd+DiTo941hcJH2ih xojGa8NwcyWUnhNkRN41FQr7TU9Bx7wvSKOF2m+x6fJL27ei5UZcKtvPrmtEZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1690318868; 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=yAUyHDOepjLRV0jCL0utqP9lIhOR5j2gdwiwkpbbEog=; b=QpKTl/PXWr6GXOrea1K8CBtYLKss+XbJlPSx6WuJT9LtiVWGSQbBxeGkn+VkgyeCKmOPIs iMJDftHoQ+NOYUjtBp4tvQpnYNFGINTz0sLYjxCvwd7xRj6KDG+7WfS2cqGMw8RqPMvNIu DhKz6pRWHel+ZssPLbjNqJ8tfIqeOGH8eAd4fr2Etw3PtcJkFCBfLRzXMzNXtFvbI7KJKX W5EIFA5IEmusuFzOoM+hUwMtR7OPf3DJjRyVwIqPTlRZB4vWBwo6n6feepPG7Er6E/VGyV KULuHqslS288PN4Qqpx9xn87hSPVTGV3wOszX2iuqKnkNeX5qdTwMGntvZrrYA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1690318868; a=rsa-sha256; cv=none; b=c5BSdD1sr6HLGgTqjtWv7rBHchtkbq2knSq0h43lvpy8sjv9Yt8raMUlSjM+qVo+Ka23Jf rb85rUmJX0ede//BlUgxqUr6iBPybVJdik3FDm8l9l7x5mEUseZJYuSJgjGMGhpxBEVBGb iE/3D7J5j/0qgJuWfmMIJgx/vzF/pYCMfA8NyhaMJoQVqfWVzVZZpiuQlj8qcTlecmbs4g 6aQalcOIeVEVywk887pbZTPlRrErxFcUe4F3dV964Ak/ZaAIDvPqRUD8kW1TZmzhiY4wod nQ3OHCxuqm576FLLMTIDtfkXF1kB2zSvSAQu5RTu/tzyPiJyiACKxbfvC03J2Q== Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (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 (2048 bits) client-digest SHA256) (Client CN "tensor.andric.com", Issuer "R3" (verified OK)) (Authenticated sender: dim) by smtp.freebsd.org (Postfix) with ESMTPSA id 4R9Tw43cH7zn7K; Tue, 25 Jul 2023 21:01:08 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from smtpclient.apple (longrow.home.andric.com [192.168.0.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 0FC87652B8; Tue, 25 Jul 2023 23:01:06 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_7D8054ED-B90F-44FB-AA8D-2AC6B6FE87A3"; protocol="application/pgp-signature"; micalg=pgp-sha1 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 \(3731.700.6\)) Subject: Re: HST time zone From: Dimitry Andric In-Reply-To: Date: Tue, 25 Jul 2023 23:00:49 +0200 Cc: FreeBSD Current Message-Id: References: To: David Cornejo X-Mailer: Apple Mail (2.3731.700.6) --Apple-Mail=_7D8054ED-B90F-44FB-AA8D-2AC6B6FE87A3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 25 Jul 2023, at 22:26, David Cornejo wrote: >=20 > One thing that has bothered me for a long time is that the = Pacific/Honolulu timezone is found under the America -- North and = South/United States of America/Hawaii in tzsetup. Politics of Hawaiian = Sovereignty aside, every other system I regularly install uses = Pacific/Honolulu as it is in the official tzdb. >=20 > Is there any reason why a patch to change to match the standard would = be refused? Which version of FreeBSD are you using? On my 14-CURRENT box, Hawaii is = actually found in *two* locations in tzsetup: * America -- North and South -> United States of America -> Hawaii * Pacific Ocean -> United States of America -> Hawaii So that would serve all sides? :) As far as I can see, the menu is dynamically generated from = /usr/share/zoneinfo/zone1970.tab, which has: US +211825-1575130 Pacific/Honolulu Hawaii and seems to be up-to-date with regards to the IANA tz files. -Dimitry --Apple-Mail=_7D8054ED-B90F-44FB-AA8D-2AC6B6FE87A3 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCZMA4AQAKCRCwXqMKLiCW o45UAJ4qazozABYGOhJl6CniEE4TbGFM/ACg2LOeEfW2z+nnSd6zuK2npBSFrQM= =KZUL -----END PGP SIGNATURE----- --Apple-Mail=_7D8054ED-B90F-44FB-AA8D-2AC6B6FE87A3-- From nobody Tue Jul 25 21:11:09 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 4R9V7v38GXz4nvVv for ; Tue, 25 Jul 2023 21:11:23 +0000 (UTC) (envelope-from dave@dogwood.com) Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 4R9V7v1J5yz3wTq for ; Tue, 25 Jul 2023 21:11:23 +0000 (UTC) (envelope-from dave@dogwood.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lj1-x22c.google.com with SMTP id 38308e7fff4ca-2b703a0453fso89088831fa.3 for ; Tue, 25 Jul 2023 14:11:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dogwood.com; s=google; t=1690319481; x=1690924281; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Qqo3dQEbBWwDmBUX8ztVJ2dc4F0SOHxS3LxftqVwMfU=; b=YE6nVmUx/dLgP50yoPPfgBbQ/XJNcI0U2zNrZfFWT02jHTxD+eVQEZuT+7J2CWaz6m kf0NvGXS61nJ40nFHIVQHf1wftvWdjfcoXxwILGL1BusvxfjWTahrBi/iumHdfUQtOoi LHPywG+FwDRBez+H9HoArKz/M7W+40552TFl8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690319481; x=1690924281; h=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=Qqo3dQEbBWwDmBUX8ztVJ2dc4F0SOHxS3LxftqVwMfU=; b=BE+rnJH/KkryxJSKY4sAPLl+RUt39QkIg2o6NEgu3FVJRVd32n9ZiAzAdCOnaO805X As9yiLhWf3OP7rRnLN9R5mwQ9fq8GuRASPvNa3bhzUwroGH4CFP/xNRmRLgXPHbXViYS ACTHOHq0Kxl+tzeFUy3AW3+SuEF9wg5m3+H/0kjeYD2FcNK46fEh8wgEvmd7774/eT5d TEqwp3TXs12DAE7z5GQqUu6ZSnLB/1+c6ZmQ68KFZKxQq1eWomAOzJWmMJcPnrqVhIZV 4ybBc3WeLHrfo+cAy25P7MjEq6gIYVxglUyMdYSwvxq/0H+PnjZ7r7+sZx3QzL+69D5R to7g== X-Gm-Message-State: ABy/qLZ4FDg+CvGe94oAxtB5ET6zJ139c57Hr38T0ZvIpxJ0elzhMNuq dk2PA/sYpNtauSeczAfpHnUDLpVbovAgQZsSCws97Hoy3n4p6Sd3yk8= X-Google-Smtp-Source: APBJJlFtJWVgLYxyz+yUtS4dBvJskly50tMHlRuYwdYzwcn8OTB8KQLNxgswojhYsIGWuOe0rIhx4+SjqANad0Jdaes= X-Received: by 2002:a2e:9cd4:0:b0:2b7:3656:c594 with SMTP id g20-20020a2e9cd4000000b002b73656c594mr3073ljj.3.1690319481060; Tue, 25 Jul 2023 14:11:21 -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: In-Reply-To: From: David Cornejo Date: Tue, 25 Jul 2023 11:11:09 -1000 Message-ID: Subject: Re: HST time zone To: Dimitry Andric Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000039d8c10601562cc0" X-Rspamd-Queue-Id: 4R9V7v1J5yz3wTq X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated --00000000000039d8c10601562cc0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jul 25, 2023 at 11:01=E2=80=AFAM Dimitry Andric w= rote: > On 25 Jul 2023, at 22:26, David Cornejo wrote: > > > > One thing that has bothered me for a long time is that the > Pacific/Honolulu timezone is found under the America -- North and > South/United States of America/Hawaii in tzsetup. Politics of Hawaiian > Sovereignty aside, every other system I regularly install uses > Pacific/Honolulu as it is in the official tzdb. > > > > Is there any reason why a patch to change to match the standard would b= e > refused? > > Which version of FreeBSD are you using? On my 14-CURRENT box, Hawaii is > actually found in *two* locations in tzsetup: > > * America -- North and South -> United States of America -> Hawaii > * Pacific Ocean -> United States of America -> Hawaii > It just seems that the "standard" is Pacific/Honolulu and we are different - in the IANA tz db, there is only mention of Pacific/Honolulu. While I'm not saying they're correct, every Linux dist I've tried uses it. I have a mixed shop, and every difference is a potential problem. I doubt that this affects many people, so consistency would not seem a hardship. So that would serve all sides? :) > > As far as I can see, the menu is dynamically generated from > /usr/share/zoneinfo/zone1970.tab, which has: > > US +211825-1575130 Pacific/Honolulu Hawaii > > and seems to be up-to-date with regards to the IANA tz files. > > -Dimitry > > --00000000000039d8c10601562cc0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Jul 25, 2023 at 11:01=E2=80=AFAM Dimitry Andric <dim@freebsd.org> wrote:
=
On 25 Jul 2023, at 22:26, David Cornejo <dave@dogwood.com> wrote:
>
> One thing that has bothered me for a long time is that the Pacific/Hon= olulu timezone is found under the America -- North and South/United States = of America/Hawaii in tzsetup. Politics of Hawaiian Sovereignty aside, every= other system I regularly install uses Pacific/Honolulu as it is in the off= icial tzdb.
>
> Is there any reason why a patch to change to match the standard would = be refused?

Which version of FreeBSD are you using? On my 14-CURRENT box, Hawaii is act= ually found in *two* locations in tzsetup:

* America -- North and South -> United States of America -> Hawaii * Pacific Ocean -> United States of America -> Hawaii

It just seems that the "standard" is Pacific/Honolulu a= nd we are different - in the IANA tz db, there is only mention of Pacific/H= onolulu. While I'm not saying they're correct, every Linux dist I&#= 39;ve tried uses it. I have a mixed shop, and every difference is a potenti= al problem.

I doubt that this affects many people, so consistency would = not seem a hardship.

So that would serve all sides? :)

As far as I can see, the menu is dynamically generated from /usr/share/zone= info/zone1970.tab, which has:

US=C2=A0 =C2=A0 =C2=A0 +211825-1575130 Pacific/Honolulu=C2=A0 =C2=A0 =C2=A0= =C2=A0 Hawaii

and seems to be up-to-date with regards to the IANA tz files.

-Dimitry

--00000000000039d8c10601562cc0-- From nobody Wed Jul 26 10:11:22 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 4R9qRy33nZz4pKlQ for ; Wed, 26 Jul 2023 10:11:26 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 4R9qRx3W6dz3nGr for ; Wed, 26 Jul 2023 10:11:25 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aetern.org header.s=fm3 header.b=FI7GKRNY; dkim=pass header.d=messagingengine.com header.s=fm3 header.b="k jRTArr"; spf=pass (mx1.freebsd.org: domain of yuri@aetern.org designates 66.111.4.27 as permitted sender) smtp.mailfrom=yuri@aetern.org Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id B7A5F5C0064 for ; Wed, 26 Jul 2023 06:11:24 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Wed, 26 Jul 2023 06:11:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1690366284; x=1690452684; bh=xs2WGgy6e+9h/NcFLViGsSLQmiW7mfNFiU/ XxfjkFMY=; b=FI7GKRNYbtZikFyyADqFT7BSJUXdtdFwE1Wv2+Y7iURMlPp82GO XMJ2aM14cAT63XTpM2HpCZ/hYiElXDIQ/EheLyBlQcJE8QJVo++ICIkO7J+Vz2sI 2cyyNeiPfJiv2ukEF8Udw2c+LOSxQPwIDbJg6GpZb6aAYnsDcSaaN9ms+rXVeCyN JJWCL6daosRBdwA5DMicDlkxzhYoadqAdXo+GF+ssG0LPDH7SqaofNQYXDgZIR9H Ur3fzSQ/1J+ddpIvrJCurORNKM+W6OowKuzAGgRzSd7zBEsE+gq3A5cqevqTy9+D oB1cTbPBIu+shbtc6CKgev3l68MD6qFLl+g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1690366284; x= 1690452684; bh=xs2WGgy6e+9h/NcFLViGsSLQmiW7mfNFiU/XxfjkFMY=; b=k jRTArrvoqjD0lnUmoKBxR2REz8SLAfO9ZgRQBZnLY6dbxFnKvuKre+Syku98vIaL cCZu1L+ZzbNxuezIflPbnToEJeauEFNfG3CMgqVOqTZj9odE7ZfXMYoE9AbuL+3J 5ekmht+2WY7s75mcf5QJRrtK422elW4tVZyghBYODwZe9dZwxREv385cVrgf264k AtfFrHH7DejqO4fGNDQ8HoMhnyEMcEEIPDfaZIazKwbBRKazrIQQvhZCxYs44j9g jnZ1u3CAl1UygtSURSZyWWRDV5APeHV/rcN3KnACn8mN0X2qW4JKCeD/YGUwDUWi 6RiJK6u/qzGU7JaWgobPg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedriedvgddvgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesthekre dttddvjeenucfhrhhomhepjghurhhiuceohihurhhisegrvghtvghrnhdrohhrgheqnecu ggftrfgrthhtvghrnhephfdtgfelkeeuheekgfevveduvdffheekkeegkeelgeekiedvud ejvdduheeuheelnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhf rhhomhephihurhhisegrvghtvghrnhdrohhrgh X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Wed, 26 Jul 2023 06:11:23 -0400 (EDT) Message-ID: Date: Wed, 26 Jul 2023 12:11:22 +0200 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: HST time zone Content-Language: en-US To: current@freebsd.org References: From: Yuri In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4R9qRx3W6dz3nGr X-Spamd-Bar: / X-Spamd-Result: default: False [-0.39 / 15.00]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.27]; R_DKIM_ALLOW(-0.20)[aetern.org:s=fm3,messagingengine.com:s=fm3]; XM_UA_NO_VERSION(0.01)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; local_wl_from(0.00)[yuri@aetern.org]; DKIM_TRACE(0.00)[aetern.org:+,messagingengine.com:+]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_from David Cornejo wrote: > On Tue, Jul 25, 2023 at 11:01 AM Dimitry Andric > wrote: > > On 25 Jul 2023, at 22:26, David Cornejo > wrote: > > > > One thing that has bothered me for a long time is that the > Pacific/Honolulu timezone is found under the America -- North and > South/United States of America/Hawaii in tzsetup. Politics of > Hawaiian Sovereignty aside, every other system I regularly install > uses Pacific/Honolulu as it is in the official tzdb. tzsetup is (more or less) following the logic of the original tzselect script from tzcode. > > Is there any reason why a patch to change to match the standard > would be refused? What kind of standard and what exactly needs to be patched? > Which version of FreeBSD are you using? On my 14-CURRENT box, Hawaii > is actually found in *two* locations in tzsetup: > > * America -- North and South -> United States of America -> Hawaii > * Pacific Ocean -> United States of America -> Hawaii Using tzsetup compiled with -DVERBOSE shows that both options install Pacific/Honolulu. > > > It just seems that the "standard" is Pacific/Honolulu and we are > different - in the IANA tz db, there is only mention of > Pacific/Honolulu. While I'm not saying they're correct, every Linux dist > I've tried uses it. I have a mixed shop, and every difference is a > potential problem. We are not really different as the timezone file selected is indeed Pacific/Honolulu. What is the exact difference with linux dists? > I doubt that this affects many people, so consistency would not seem a > hardship. > > So that would serve all sides? :) > > As far as I can see, the menu is dynamically generated from > /usr/share/zoneinfo/zone1970.tab, which has: > > US      +211825-1575130 Pacific/Honolulu        Hawaii > > and seems to be up-to-date with regards to the IANA tz files. Right, tzsetup only processes what's there in zone1970.tab. From nobody Thu Jul 27 15:37: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 4RBZf51cJRz4pTmN; Thu, 27 Jul 2023 15:37:49 +0000 (UTC) (envelope-from salvadore@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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 4RBZf50Hzrz3vLd; Thu, 27 Jul 2023 15:37:49 +0000 (UTC) (envelope-from salvadore@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1690472269; 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=IovPxAeKhIgzLHnGcVjxqZN8pgchgpLyzMkFWCa0pzU=; b=QRNtt0x56UIZ8jWayMMwt9OxVDi55xWHRwdLxrRsqSuo7VHlc4P0YUeEVrtZ+CUr2kUoTU 9C601eT1IA8mY6gxTlBOHpqQTRo1irbLT2V/Fe2oNl1RA/ClMr1tIZXd/qIWSeL3U1K201 Q4VCv01Ok9oodwlo3Pd0zH0x7sH5OBBoAPXfK8cJN2l1vNIZGroSuG/wa4Sd/SdveP3nrQ yQRI+ZCarG7TapuP6l4wPq8bH61ifAc0QVizTg5SZHR1wX0oKbicpNkLgGqSY74CvDMISG 5HEpGIH1xROrpLRAGE1qM9u+lrsWTRNY/0DTSGRmzfH2yPb7u7l+q4EXmG7D0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1690472269; 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=IovPxAeKhIgzLHnGcVjxqZN8pgchgpLyzMkFWCa0pzU=; b=L1LQBGgx8dRE62QqLYviRTdjgZn1cIxQX+ClJ8Vlm7cIAN/1K2qq5xrSkcimU8Mkb8/x11 TJqeps00L5KUHm9WgW6OInpkx0tALH2cgm1NBl0kkZvpog4lMp+O7XG1drs+VZH9SGJqsf KrlljWW5YeRpaCDD1wVn7KiLj1Y/ltHDjWvfaGeNU0l8PMGNhk3Eph/AVqF4TOkhTvP7vR nlI8gf9hQPNL/2R9h9sF6+r7dIEOkZJPgJpXN/4VEVHzW6ZoJRrXyPZ25w6+lZweEcpzq0 DHP8edB7KENBfG9/AHgCzBngxNWLwxemouvur9+zGjkQ6STRftXgYaO4kOdnkg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1690472269; a=rsa-sha256; cv=none; b=RQ22XbnM9cN+lYex+P9Afd4wnmjecI2481sUBv4E8vPLExA+loGshC29BExnINLyFmqbIg CvAYKZImdWaLK0X7XH6ZwS+H8brDtZYwXUogMZaRFClCctc4fFTJvz7ovy4PFs+d0w+yby ygodQSvwtwjJF/8cthVQa8wKF9aF6RtaREGVHBSQtzYpY/TQaGOPT3WOWIjUWkAlnUN/GQ 3Q67/hCSc151DXM1rZWCM5ZQN42KxPveGEwpSXRjpfzTcAhotyzw11yrnnHGyuJClDfuMx o1WugdZ2uHgBBBxAezSgnIQ3dkz5SeTpo+y2TsnmsCSwGJYhDezGkPG8OXktbg== Received: by freefall.freebsd.org (Postfix, from userid 1472) id DD86E6A33; Thu, 27 Jul 2023 15:37:48 +0000 (UTC) Date: Thu, 27 Jul 2023 15:37:48 +0000 From: Lorenzo Salvadore To: freebsd-hackers@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: FreeBSD Status Report - Second 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 Content-Transfer-Encoding: 8bit FreeBSD Status Report Second Quarter 2023 Here is the second 2023 status report, with 37 entries. As you might notice, we have several more reports than last quarter. This is a great news and shows how much the FreeBSD community is active and always working on providing high quality software. In particular, please note that Summer has started and do not miss the amazing projects shared by our Google Summer of Code students. 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-04-2023-06/ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Core Team □ FreeBSD Foundation □ FreeBSD Release Engineering Team □ Cluster Administration Team □ Continuous Integration □ Ports Collection • Projects □ Cirrus-CI □ BATMAN support in the FreeBSD kernel □ FreeBSD support on LinuxBoot • Userland □ OpenSSL 3 in base □ Linux compatibility layer update □ Service Jails — automatic jailing of rc.d services □ Security Sandboxing Using ktrace(1) □ NVMe over Fabrics • Kernel □ Boot Performance Improvements □ CI Test Harness For Bootloader □ Physical memory compaction for the FreeBSD kernel □ Increasing MAXCPU □ SquashFS port for FreeBSD kernel □ Pf Improvements □ Network Interface API (IfAPI) □ Making Netgraph Lock-Free • Architectures □ SIMD enhancements for amd64 □ Integrate mfsBSD into the release building tools • Cloud □ FreeBSD as a Tier 1 cloud-init Platform □ OpenStack on FreeBSD □ FreeBSD on Microsoft HyperV and Azure □ FreeBSD on EC2 • Documentation □ Documentation Engineering Team • Ports □ KDE on FreeBSD □ GCC on FreeBSD □ Puppet □ MITRE Caldera on FreeBSD □ Wazuh on FreeBSD • Third Party Projects □ PkgBase.live □ 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. DevSummit 202305 The Core Team has presented the status update at the FreeBSD Developer Summit, 17th–18th May. Slides are available at https://wiki.freebsd.org/DevSummit/ 202305. FreeBSD 14 The Core Team is working with other teams to ensure that FreeBSD 14.0-RELEASE will be of the highest quality. The Core Team has no objection to mark riscv64sf (64-bit RISC-V soft-float) as unsupported in 14. Meetings with The FreeBSD Foundation The Core Team and The FreeBSD Foundation continue to meet regularly 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 of, and employees of, the Foundation. They discussed how the Foundation can help the Core Team and the Project in general. Matrix IM solution One of the major items in the Core Team updates in DevSummit 202305 was proposing a new project communication solution. There is currently a testing instance at matrix-dev.FreeBSD.org setup by clusteradm. All developers can access the instance with their kerberos credentials, and some public rooms can be joined through Matrix’s federation feature. Please note this instance is for testing and evaluating so no backup or availability is guaranteed. The Core Team is still discussing the scope and administration of this service, and collecting feedback from the community. Code of Conduct Committee Code of Conduct Committee (conduct@) is managed by the Core Team now. Commit bits Core approved the src commit bit for Christos Margiolis (christos@). ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Foundation Links: FreeBSD Foundation URL: https://www.freebsdfoundation.org Technology Roadmap URL: https://freebsdfoundation.org/blog/technology-roadmap/ Donate URL: https://www.freebsdfoundation.org/donate/ Foundation Partnership Program URL: https://freebsdfoundation.org/our-donors/ freebsd-foundation-partnership-program/ FreeBSD Journal URL: https://www.freebsdfoundation.org/journal/ Foundation News and Events URL: https://www.freebsdfoundation.org/ news-and-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 are used to 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 release engineering efforts. We publish marketing material to promote, educate, and advocate for the FreeBSD Project, 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. Happy 30th birthday, FreeBSD! For more than 23 years, we have proudly backed this remarkable operating system and its vibrant community, and we eagerly anticipate supporting them for many more years. In this update, we will outline our contributions to FreeBSD across multiple domains. We will touch upon project development initiatives, some of which have detailed reports of their own. Additionally, we will showcase our advocacy for FreeBSD, our efforts to foster community engagement, and our expansion of partnership endeavors. Lastly, we will delve into our ongoing work to secure increased funding, enabling us to allocate additional resources to address any gaps within the Project. Fundraising During this quarter, we made significant progress in engaging with commercial FreeBSD users. To enhance our partnerships with existing and potential commercial users, we hired Greg Wallace as the Director of Partnerships and Research. His primary objective is to expand our collaborations with commercial users. Since assuming this position, Greg has hit the ground running, meeting with numerous companies in just one quarter. These interactions have provided valuable insights into how FreeBSD is being utilized, the challenges faced by users, and areas where the Project can improve. By understanding these aspects, we can make informed decisions on where to allocate our funding and recognize FreeBSD’s unique strengths. Additionally, the role involves conducting research to identify target markets, explore new opportunities for FreeBSD, and ensure our voice is heard in relevant discussions. For more details on Greg’s objectives and accomplishments, you can refer to his status update below. The Foundation extends its heartfelt gratitude to everyone who made financial contributions to support our work. Besides many individual contributions, we were pleased to receive larger donations from NetApp and Blackberry. In addition, we received FreeBSD Developer Summit sponsorships from Tarsnap, iXsystems, and LPI. These sponsorships greatly assist in offsetting our expenses and enable us to offer affordable registration fees to attendees. 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 having a dedicated individual focused on partnerships, we can effectively emphasize the significance of investing in our efforts and underscore the long-term viability of the Project to companies. Your support plays a crucial role in our mission, and we deeply appreciate your commitment to the FreeBSD community. Please consider making a donation toward our 2023 fundraising campaign! https://www.freebsdfoundation.org/donate/ For more prominent commercial donors we have the FreeBSD Foundation Partnership Program, which was established in 2017. Partnership Program Hello FreeBSD community. My name is Greg Wallace. I joined the Foundation as Director of Partnerships and Research in early April. This blog introduced me and the role. For Partnerships, I am focused on building connections with companies that use FreeBSD. I have met with several companies to learn about how they use FreeBSD. Some of these meetings have generated discussions about potential partnership. I continue to find out about interesting companies using FreeBSD and I am reaching out to them. My objective is to get in touch with every company building with and using FreeBSD to listen to their stories. If this is you and we have not yet connected, please schedule a call on my calendar. Some other partnership-related activities this quarter: • I created these slides about how partnering with the Foundation helps advance FreeBSD. If you have ideas for how I can improve these slides, or would like me to present them to your organization, please send me an email , or schedule a call. And please feel free to share the presentation liberally, in whole or in part. • I worked with my Foundation colleagues to create a number of industry-specific use case slides for a presentation to an industry analyst. • I am also pursuing grant opportunities with bodies including: □ NSF Secure and Trustworthy Cyberspace (SaTC) □ Sovereign Tech Fund □ NGI. In terms of research, my broad aim is to make sure that all of the expertise in this community is reflected in the global conversations on computing performance, security, and energy efficiency. As a community, we have much to bring to this work. So far, I have been tracking and plugging into the following threads: • Open Forum Europe • CHIPS Research and Development. If you have research ideas or are interested in working together in this area, please send me an email, or schedule a call. OS Improvements During the second quarter of 2023, 339 src, 155 ports, and 20 doc tree commits identified The FreeBSD Foundation as a sponsor. Some of this and other Foundation-sponsored work is described in separate report entries: • Continuous Integration • FreeBSD as a Tier 1 cloud-init Platform • OpenSSL 3 in base • OpenStack on FreeBSD • Security Sandboxing Using ktrace(1) • SIMD enhancements for amd64 Here is a sampling of other Foundation-sponsored work: • Bug fixes for fsck_ffs(8) • Bug fixes for killpg(2) • Improvements to hwpmc • Improvements to vmm • Port fixes and workarounds for LLVM 16 and OpenSSL 3.0 • Port kinst to RISC-V and related DTrace work • Update of libfido2 to version 1.9.0 • Various LinuxKPI 802.11 improvements • Various RISC-V improvements • Vendor import and update of tcpdump from version 4.9.3 to version 4.99.4. The status of current and past Foundation-contracted work can be viewed on the Foundation Projects page. Members of the Foundation’s technology team presented at the Developer Summit held in Ottawa, Canada from May 17-18. This included hosting the GSoC, FreeBSD Foundation Technical Review, and Workflow working group sessions. Pierre Pronchery spoke about driver harmony between the BSDs and En-Wei Wu discussed wtap work completed under contract with the Foundation. 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. 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 are grateful to be back to attending events mostly in person. In addition to attending and planning events, 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 the advocacy and education work we did: • Helped to organize and attended the May 2023 Developer Summit which took place May 17-18, 2023 in Ottawa, Ontario • Hosted a table and was the Tote Bag Sponsor of BSDCan, May 17-20, 2023 in Ottawa, Ontario □ Trip reports can be found on the blog • Celebrated the Project’s 30th Birthday at BSDCan with cake and printed copies of the special 30th Anniversary Edition of the FreeBSD Journal • Secured a FreeBSD Workshop and Talk at FOSSY, July 13-16, 2023, in Portland, Oregon • Secured our Silver Sponsorship for EuroBSDCon 2023 taking place September 14-17, 2023 in Coimbra, Portugal • Secured our booth for All Things Open, October 15-17, 2023 in Raleigh, North Carolina • Began planning the FreeBSD Fall Vendor Summit • Welcomed two New Team Members: Greg Wallace and Pierre Pronchery • Published April and June Newsletters • Celebrated the FreeBSD Day and the Project’s 30th Anniversary on June 19 and through the week with special videos and blog posts • Additional Blog Posts: □ EuroBSDcon 2023 Travel Grant Application Now Open - Note: Applications close August 2, 2023 □ AsiaBSDcon Trip Report • FreeBSD in the News: □ InfoWorld: Happy 30th FreeBSD!. 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:// www.FreeBSDfoundation.org/news-and-events/. 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://www.freebsdfoundation.org to find more about how we support FreeBSD and how we can help you! ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Release Engineering Team Links: FreeBSD 13.2-RELEASE schedule URL: https://www.freebsd.org/releases/13.2R/ schedule/ 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 second quarter of 2023, the Team continued work on 13.2-RELEASE. The 13.2 cycle had closely followed the set schedule, with the addition of three additional RC builds at the end, and the final RELEASE build and announcement in mid-April. In coordination with various teams within the Project management, the FreeBSD Release Engineering Team reconsidered the original schedule for the upcoming 14.0-RELEASE, primarily due to work that was in progress. The updated schedule was discussed and adjusted slightly to account for some concerns, and ultimately published on the FreeBSD Project website. The new schedule targets 14.0-RELEASE for October, 2023. The Team continued providing weekly development snapshot builds for the main, stable/13, and stable/12 branches. Note, there will no longer be snapshot builds against stable/12 moving forward. Sponsor: Tarsnap Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Cluster Administration Team Links: Cluster Administration Team members URL: https://www.freebsd.org/administration /#t-clusteradm Contact: Cluster Administration Team FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronise its distributed work and communications. In this quarter, the team has worked on the following: • Regular support for FreeBSD.org user accounts. • Regular disk and parts support (and replacement) for all physical hosts and mirrors. • Enable mirroring of https://www.FreeBSD.org and https://docs.FreeBSD.org in the FreeBSD project-managed mirrors. • Cluster refresh, upgrading all hosts and jails to the most recent versions of 14-CURRENT, 13-STABLE, and 12-STABLE. Work in progress • Large-scale network upgrade at our primary site. □ New Juniper switches arrived at our primary site to replace the former ones. We thank Juniper for the donation. • Replace old servers in our primary site and a few mirrors. □ Besides the broken CI servers, we have a few old servers with broken disks and faulty PSUs. This task is in conjunction with The FreeBSD Foundation and donors/sponsors. • Install new CI (Continuous Integration) machines repurposed from the package builders. • Review the backup configuration of the services running in the FreeBSD cluster. FreeBSD Official Mirrors Overview Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Taiwan, United Kingdom (full mirror site), United States of America — California, New Jersey (primary site), and Washington. The hardware and network connection have been generously provided by: • Bytemark Hosting • Cloud and SDN Laboratory at BroadBand Tower, Inc • Department of Computer Science, National Yang Ming Chiao Tung University • Equinix • Internet Association of Australia • Internet Systems Consortium • INX-ZA • KDDI Web Communications Inc • Malaysian Research & Education Network • Metapeer • NIC.br • Your.Org • 365 Data Centers The Frankfurt single server mirror is the primary Europe mirror in bandwidth and usage. We are still looking for an additional full mirror site (five servers) in Europe to replace old servers in the United Kingdom full mirror site. We see a good pattern in having single mirrors in Internet Exchange Points worldwide (Australia, Brazil, and South Africa); if you know or work for some of them that could sponsor a single mirror server, please get in touch. United States (West Coast) and Europe (anywhere) are preferable places. See generic mirrored layout for full mirror site specs and tiny-mirror for a single mirror site. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Continuous Integration Links: FreeBSD Jenkins Instance URL: https://ci.FreeBSD.org FreeBSD CI artifact archive URL: https://artifact.ci.FreeBSD.org FreeBSD Jenkins wiki URL: https://wiki.FreeBSD.org/Jenkins 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 second 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: • FreeBSD-stable-13-amd64-gcc12_build job has been added. • Build environment of main and stable/13 branches has been changed to 13.2-RELEASE, and stable/12 has been changed to 12.4-RELEASE. • *-build jobs using gcc12 are sending failure reports to dev-ci Mailing List . • Present Testing/CI Status Update in BSDCan 2023 Developer Summit Work in progress tasks: • Designing and implementing pre-commit CI building and testing (to support the workflow working group) • 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 • Organizing the scripts in freebsd-ci repository to prepare for merging to src repository • 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. Currently there are just over 34,400 ports in the Ports Tree. There are currently 3,019 open ports PRs of which 746 are unassigned. The last quarter saw 10,439 commits on the main branch by 151 committers and 745 commits on the 2023Q2 branch by 55 committers. Compared to the previous quarter, this means a slight increase in the number of ports, a tiny decrease in the number of open PRs, and a fair increase in the number of ports commits. During this quarter, we welcomed back Tom Judge (tj@) and said goodbye to Steve Wills (swills@). Steve was also on portmgr. As part of the portmgr lurker program, we welcomed Ronald Klop (ronald@), Renato Botelho (garga@), and Matthias Andree (mandree@). Portmgr has resumed work on introducing sub-packages into the Tree, but various things still needs to be fleshed out. On the software side, pkg was updated to 1.19.2, Firefox to 114.0.2, Chromium to 114.0.5735.198, and KDE Gear to 23.04.2. During the last quarter, antoine@ ran 23 exp-runs to test package updates, bump CPU_MAXSIZE to 1024, fix armv7 failures for devel/cmake-core and add --auto-features=enabled to USES=meson Lastly, the Ports Tree was updated to support LLVM 16 and OpenSSL 3 in FreeBSD-CURRENT. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Projects Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Cirrus-CI Links: FreeBSD Cirrus-CI Repositories URL: https://cirrus-ci.com/github/freebsd/ FreeBSD src CI URL: https://cirrus-ci.com/github/freebsd/freebsd-src FreeBSD doc CI URL: https://cirrus-ci.com/github/freebsd/freebsd-doc Contact: Brooks Davis Contact: Ed Maste < emaste@FreeBSD.org> Contact: Li-Wen Hsu Cirrus-CI is a hosted continuous integration service that supports open source projects with CI services on Linux, Windows, macOS, and FreeBSD. It complements our own Jenkins CI infrastructure by supporting other use cases, including testing GitHub pull requests and FreeBSD forks. We added Cirrus-CI configuration to the FreeBSD src tree in 2019 and to doc in 2020. A number of additional FreeBSD projects hosted on GitHub (such as drm-kmod, kyua, pkg, and poudriere) also make use of Cirrus-CI. Over the last quarter Cirrus-CI configs received ongoing maintenance updates (moving to the most recent FreeBSD release images). In the src tree we have added some additional checks. These ensure that generated files are updated when needed (make sysent and make makeman) and check for missing directories. We have added jobs that build using the Clang/LLVM 16 toolchain package, mirroring the Clang version now in the base system. The GCC job is now run on the GitHub mirror by default, for all commits. Sponsor: DARPA Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BATMAN support in the FreeBSD kernel Links: Wiki page URL: https://wiki.freebsd.org/SummerOfCode2023Projects/ CallingTheBatmanFreeNetworksOnFreeBSD Source code (Pull Request) URL: https://github.com/obiwac/freebsd-gsoc/pull/1 Contact: Aymeric Wibo BATMAN (Better Approach to Mobile Ad-hoc Networking), as developed and used by the Freifunk project, is a routing protocol for (primarily wireless) multi-hop ad-hoc networks. Freifunk is a German initiative to build an open Wi-Fi network at city-scale, based on the principles of net-neutrality. BATMAN’s motive is to be a completely decentralized protocol; no one node in the network knows or has to care about the topology of the whole network. Support for this protocol is provided by the batman-adv kernel module on Linux, and this project aims to bring that to FreeBSD. This includes the kernel module itself, but also userland networking libraries and tools necessary to create BATMAN networks. Currently, creating interfaces and interacting with them works (with both Linux and FreeBSD userspaces), and packet transmission (kind of) works, although it is incomplete as of yet. Support for batadv interfaces has been added to ifconfig(8) too. Mentor: Mahdi Mokhtari Sponsor: The Google Summer of Code '23 program ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD support on LinuxBoot Contact: Warner Losh Links: LinuxBoot Project URL: https://www.linuxboot.org/+ BSDCan 2023 kboot talk slides URL: https://docs.google.com/presentation/d/ 1N5Jp6XzYWv9Z9RhhETC-e6tFkqRHvp-ldRDW_9h2JCw/edit?usp=sharing LinuxBoot is an effort to create a clean, robust, auditable and repeatable boot firmware. What originally started as a specific project at Google has grown to encompass any boot environment that uses Linux to launch the final operating system. Many platforms now support this environment, and in some cases it is the only available boot environment. In addition, some embedded boxes have a LinuxBoot environment hard-coded that is quite hard to change, and being able to reboot into FreeBSD is desirable. The old Sony PlayStation 3 port used a boot loader called 'kboot' to boot the FreeBSD port from its Linux kernel (all predating the LinuxBoot project). That code has been greatly expanded, made generic with easily replaceable per-architecture plug ins. The normal FreeBSD /boot/loader is built as a Linux binary that reads in the FreeBSD kernel, modules and tunables. It places them into memory as if it were running in a pre-boot environment, then loads that image into the Linux kernel with kexec_load(2) and does a special reboot to that image. For UEFI-enabled systems, it passes the UEFI memory table and pointer to UEFI runtime services to the new kernel. It supports loading files from the host’s filesystem, from any loader(8) -supported filesystem on the host’s block devices (including pools that span multiple devices), from ram disk images and from files downloaded over the network. Any mix of these is available. So, for example, configuration overrides can be loaded from the host’s filesystem whilst the kernel loads from dedicated storage (say NVME) or a ram disk image. It supports a host console running over stdin/stdout. It supports explicit locations such as /dev/ nvme0ns1:/boot/loader/gerbil.conf for where to load filesystems from. It supports ZFS boot environments, including the boot-once feature. Additional details about kboot, what it supports and some general background can be found in Warner’s BSDcan talk (slides linked above). FreeBSD/aarch64 now can boot from Linux in a LinuxBoot environment, with support and functionality comparable to loader.efi(8). Memory layout passed in for GICv3 workarounds. Need patch for aarch64 kernel for the GICv3 workaround ( https://reviews.freebsd.org/D40902). FreeBSD/amd64 support is in progress and is maybe 80% done. The amd64 boot environment places more requirements on the boot loader to provide data for the kernel than aarch64, due to amd64 being an older port. All sources for data in the BIOS environment had to be provided by the boot loader since the kernel had no access to them from long mode. While UEFI and ACPI provide ways for the kernel to get this data, much of the data must still be provided by the boot loader. The kernel panics during initialization since all these prerequisites have not been discovered and implemented. PowerPC builds, but nothing more of its state is known. Attempts to acquire a suitable Playstation 3 proved to be too time consuming for the author. Help Needed 1. loader.kboot(8) needs to be written. It should document how to use loader.kboot, how to create images, and the use cases that work today. 2. Finish amd64 support. 3. The current elf arch-specific metadata code is copied from efi. Unifying the kboot and efi copies is needed. While they are mostly the same, sharing is complicated by remaining compile-time differences. In addition, the build infrastructure makes sharing awkward. 4. It would be nice to add riscv64 support. 5. PowerPC testing (it has been untested since the refactoring started). 6. Creating a script to repackage EDK-II image (say, from QEMU) as a linux-boot image with a Linux kernel built on FreeBSD for CI testing. 7. Testing it from the coreboot LinuxBoot. Sponsored by: Netflix, Inc ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Userland Changes affecting the base system and programs in it. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ OpenSSL 3 in base Links: OpenSSL Downloads URL: https://www.openssl.org/source/ OpenSSL 3.0 Has Been Released! URL: https://www.openssl.org/blog/blog/2021/09/ 07/OpenSSL3.Final/ openssl-fipsinstall URL: https://www.openssl.org/docs/man3.0/man1/ openssl-fipsinstall.html Contact: Pierre Pronchery Pierre has been tasked with importing OpenSSL 3 into the base system. OpenSSL is a library for general-purpose cryptography and secure communication. It provides an open source implementation of the SSL and TLS network protocols, which are widely used in applications such as e-mail, instant messaging, Voice over IP (VoIP), or more prominently the global Web (aka HTTPS). Assuming that the Apache and nginx web servers use OpenSSL, their combined market share for web traffic exceeds 50%, cementing the leadership and critical importance of OpenSSL as part of the infrastructure of the Internet. Since its initial release in August 2016, the 1.1 branch of OpenSSL has been adopted by most Linux and BSD systems, while remaining supported by the upstream maintainers through an LTS (long term support) policy. However, official support is planned to end in the middle of September this year, and it became urgent and necessary to consider adopting its successor for LTS, the 3.0 branch. OpenSSL has largely outgrown its ancestor SSLeay, now shipping over half a million single lines of code (SLOC) split in over two thousand files. Perhaps as a consequence, its build system is relatively complex and normally requires Perl, which was removed from base more than twenty years ago for FreeBSD 5.0-RELEASE. Thankfully however, it was possible to import and setup OpenSSL 3.0.9 the FreeBSD way, and it is now part of the base system as planned for FreeBSD 14.0-RELEASE. To describe OpenSSL 3 as a major release is an understatement. First, its problematic licensing model has finally been solved, with a complete switch to the Apache License 2.0. Then, OpenSSL 3 introduces the concept of provider modules. While obsolete cryptographical algorithms have been isolated to a legacy module, it is also possible to restrict the implementation to the standards part of FIPS with the fips module. The latter can then benefit from a dedicated certification process, and be validated officially (like the 3.0.8 release at the time of writing). Moreover, the updated library comes with a version bump, as applications using OpenSSL 1.1 need to be recompiled to use 3.0. Many API functions have been deprecated and replaced with newer, more generic alternatives, however it is still possible to explicitly request older APIs and have OpenSSL 3 expose them accordingly. This possibility has been leveraged in FreeBSD to help with the transition, where a number of libraries and applications have simply been configured to request the OpenSSL 1.1 API. These components will be updated progressively over time in order to consume OpenSSL 3’s native API instead. While there is a known performance impact associated with the update when consuming small input block sizes, it was found to be marginal when working with blocks of 1 KB and above. Another challenge lies with the FIPS provider module, which currently requires some manual steps in order to have it working. We are currently looking for a solution to ship FreeBSD with a functional FIPS provider by default. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 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 cbbac5609115, preserving an fpu xsave state across signal delivery on amd64 is implemented. That makes it possible to run modern golang with preemptive scheduler on. The new facility to specify an alternate ABI root path was added to the namei (9). Previously, to dynamically reroot lookups, every linux(4) syscall where path names translation is needed required a bit of ugly code and used kern_alternate_path() which does not properly resolve symlinks with leading / in the target. For now a non-native ABI (i.e., linux(4)) uses one call to pwd_altroot() during exec-time into that ABI to specify its root directory (e.g., /compat/ubuntu) and forget about path names translation. That makes possible chroot into the Ubuntu compat without having to fix such symlinks by hand. In total, over 10 bugs were fixed; glibc-2.37 tests suite reports less than 70 failed tests. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Service Jails — automatic jailing of rc.d services Links: D40369: Extend /usr/bin/service with the possibility to set ENV vars URL: https://reviews.freebsd.org/D40369 D40370: Infrastructure for automatic jailing of rc.d-services URL: https:// reviews.freebsd.org/D40370 D40371: automatic service jails: some setup for full functionality of the services in automatic service jails URL: https://reviews.freebsd.org/D40371 Contact: Alexander Leidinger Service jails extend the rc(8) system to allow automatic jailing of rc.d services. A service jail inherits the filesystem of the parent host or jail, but uses all other limits of the jail (process visibility, restricted network access, filesystem mounting permissions, sysvipc, …​) by default. Additional configuration allows inheritance of the IPs of the parent, sysvipc, memory page locking, and use of the bhyve virtual machine monitor (vmm(4)). If you want to put e.g. local_unbound into a service jail and allow IPv4 and IPv6 access, simply change rc.conf(5) to have: local_unbound_svcj_options=net_basic local_unbound_svcj=YES While this does not have the same security benefits of a manual jail setup with a separate filesystem and IP/VNET, it is much easier to setup, while providing some of the security benefits of a jail like hiding other processes of the same user. The patches in the links are a rewrite of what I presented in 2019. The main difference is that an ENV variable is used to do more rational tracking and as such, requires a change to service(8). My intent is to commit D40369 before the branch of stable/14. I will not commit D40370 or D40371 before 14.0 is released and both will benefit from more eyes. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Security Sandboxing Using ktrace(1) Links: ktrace branch URL: https://github.com/jakesfreeland/freebsd-src/tree/ff/ktrace Contact: Jake Freeland Capsicumization With ktrace(1) This report introduces an extension to ktrace(1) that logs capability violations for programs that have not been Capsicumized. The first logical step in Capsicumization is determining where your program is raising capability violations. You could approach this issue by looking through the source and removing Capsicum-incompatible code, but this can be tedious and requires the developer to be familiar with everything that is not allowed in capability mode. An alternative to finding violations manually is to use ktrace(1). The ktrace (1) utility logs kernel activity for a specified process. Capsicum violations occur inside of the kernel, so ktrace(1) can record and return extra information about your program’s violations with the -t p option. Programs traditionally need to be put into capability mode before they will report violations. When a restricted system call is entered, it will fail and return with ECAPMODE: Not permitted in capability mode. If the developer is doing error checking, then it is likely that their program will terminate with that error. This behavior made violation tracing inconvenient because ktrace(1) would only report the first capability violation, and then the program would terminate. Luckily, a new extension to ktrace(1) can record violations when a program is NOT in capability mode. This means that any developer can run capability violation tracing on their program with no modification to see where it is raising violations. Since the program is never actually put into capability mode, it will still acquire resources and execute normally. Violation Tracing Examples The cap_violate program, shown below, attempts to raise every type of violation that ktrace(1) can capture: # ktrace -t p ./cap_violate # kdump 1603 ktrace CAP system call not allowed: execve 1603 foo CAP system call not allowed: open 1603 foo CAP system call not allowed: open 1603 foo CAP system call not allowed: open 1603 foo CAP system call not allowed: open 1603 foo CAP system call not allowed: readlink 1603 foo CAP system call not allowed: open 1603 foo CAP cpuset_setaffinity: restricted cpuset operation 1603 foo CAP openat: restricted VFS lookup: AT_FDCWD 1603 foo CAP openat: restricted VFS lookup: / 1603 foo CAP system call not allowed: bind 1603 foo CAP sendto: restricted address lookup: struct sockaddr { AF_INET, 0.0.0.0:5000 } 1603 foo CAP socket: protocol not allowed: IPPROTO_ICMP 1603 foo CAP kill: signal delivery not allowed: SIGCONT 1603 foo CAP system call not allowed: chdir 1603 foo CAP system call not allowed: fcntl, cmd: F_KINFO 1603 foo CAP operation requires CAP_WRITE, descriptor holds CAP_READ 1603 foo CAP attempt to increase capabilities from CAP_READ to CAP_READ,CAP_WRITE The first 7 system call not allowed entries did not explicitly originate from the cap_violate program code. Instead, they were raised by FreeBSD’s C runtime libraries. This becomes apparent when you trace namei translations alongside capability violations using the -t np option: # ktrace -t np ./cap_violate # kdump 1632 ktrace CAP system call not allowed: execve 1632 ktrace NAMI "./cap_violate" 1632 ktrace NAMI "/libexec/ld-elf.so.1" 1632 foo CAP system call not allowed: open 1632 foo NAMI "/etc/libmap.conf" 1632 foo CAP system call not allowed: open 1632 foo NAMI "/usr/local/etc/libmap.d" 1632 foo CAP system call not allowed: open 1632 foo NAMI "/var/run/ld-elf.so.hints" 1632 foo CAP system call not allowed: open 1632 foo NAMI "/lib/libc.so.7" 1632 foo CAP system call not allowed: readlink 1632 foo NAMI "/etc/malloc.conf" 1632 foo CAP system call not allowed: open 1632 foo NAMI "/dev/pvclock" 1632 foo CAP cpuset_setaffinity: restricted cpuset operation 1632 foo NAMI "ktrace.out" 1632 foo CAP openat: restricted VFS lookup: AT_FDCWD 1632 foo NAMI "/" 1632 foo CAP openat: restricted VFS lookup: / 1632 foo CAP system call not allowed: bind 1632 foo CAP sendto: restricted address lookup: struct sockaddr { AF_INET, 0.0.0.0:5000 } 1632 foo CAP socket: protocol not allowed: IPPROTO_ICMP 1632 foo CAP kill: signal delivery not allowed: SIGCONT 1632 foo CAP system call not allowed: chdir 1632 foo NAMI "." 1632 foo CAP system call not allowed: fcntl, cmd: F_KINFO 1632 foo CAP operation requires CAP_WRITE, descriptor holds CAP_READ 1632 foo CAP attempt to increase capabilities from CAP_READ to CAP_READ,CAP_WRITE In practice, capability mode is always entered following the initialization of the C runtime libraries, so a program would never trigger those first 7 violations. We are only seeing them because ktrace(1) starts recording violations before the program starts. This demonstration makes it clear that violation tracing is not always perfect. It is a helpful guide for detecting restricted system calls, but may not always parody your program’s actual behavior in capability mode. In capability mode, violations are equivalent to errors; they are an indication to stop execution. Violation tracing is ignoring this suggestion and continuing execution anyway, so invalid violations may be reported. The next example traces violations from the unzip(1) utility (pre-Capsicumization): # ktrace -t np unzip foo.zip Archive: foo.zip creating: bar/ extracting: bar/bar.txt creating: baz/ extracting: baz/baz.txt # kdump 1926 ktrace CAP system call not allowed: execve 1926 ktrace NAMI "/usr/bin/unzip" 1926 ktrace NAMI "/libexec/ld-elf.so.1" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/etc/libmap.conf" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/usr/local/etc/libmap.d" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/var/run/ld-elf.so.hints" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/lib/libarchive.so.7" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/usr/lib/libarchive.so.7" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/lib/libc.so.7" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/lib/libz.so.6" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/lib/libbz2.so.4" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/usr/lib/libbz2.so.4" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/lib/liblzma.so.5" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/usr/lib/liblzma.so.5" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/lib/libbsdxml.so.4" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/lib/libprivatezstd.so.5" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/usr/lib/libprivatezstd.so.5" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/lib/libcrypto.so.111" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/lib/libmd.so.6" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/lib/libthr.so.3" 1926 unzip CAP system call not allowed: readlink 1926 unzip NAMI "/etc/malloc.conf" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/dev/pvclock" 1926 unzip NAMI "foo.zip" 1926 unzip CAP openat: restricted VFS lookup: AT_FDCWD 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/etc/localtime" 1926 unzip NAMI "bar" 1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD 1926 unzip CAP system call not allowed: mkdir 1926 unzip NAMI "bar" 1926 unzip NAMI "bar" 1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD 1926 unzip NAMI "bar/bar.txt" 1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD 1926 unzip NAMI "bar/bar.txt" 1926 unzip CAP openat: restricted VFS lookup: AT_FDCWD 1926 unzip NAMI "baz" 1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD 1926 unzip CAP system call not allowed: mkdir 1926 unzip NAMI "baz" 1926 unzip NAMI "baz" 1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD 1926 unzip NAMI "baz/baz.txt" 1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD 1926 unzip NAMI "baz/baz.txt" 1926 unzip CAP openat: restricted VFS lookup: AT_FDCWD The violation tracing output for unzip(1) is more akin to what a developer would see when tracing their own program for the first time. Most programs link against libraries. In this case, unzip(1) is linking against libarchive(3), which is reflected here: 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/lib/libarchive.so.7" 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/usr/lib/libarchive.so.7" The violations for unzip(1) can be found below the C runtime violations: 1926 unzip NAMI "foo.zip" 1926 unzip CAP openat: restricted VFS lookup: AT_FDCWD 1926 unzip CAP system call not allowed: open 1926 unzip NAMI "/etc/localtime" 1926 unzip NAMI "bar" 1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD 1926 unzip CAP system call not allowed: mkdir 1926 unzip NAMI "bar" 1926 unzip NAMI "bar" 1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD 1926 unzip NAMI "bar/bar.txt" 1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD 1926 unzip NAMI "bar/bar.txt" 1926 unzip CAP openat: restricted VFS lookup: AT_FDCWD 1926 unzip NAMI "baz" 1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD 1926 unzip CAP system call not allowed: mkdir 1926 unzip NAMI "baz" 1926 unzip NAMI "baz" 1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD 1926 unzip NAMI "baz/baz.txt" 1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD 1926 unzip NAMI "baz/baz.txt" 1926 unzip CAP openat: restricted VFS lookup: AT_FDCWD In this instance, unzip(1) is recreating the file structure contained in the zip archive. Violations are being raised because the AT_FDCWD value cannot be used in capability mode. The bulk of these violations can be fixed by opening AT_FDCWD (the current directory) before entering capability mode and passing that descriptor into openat(2), fstatat(2), and mkdirat(2) as a relative reference. Violation tracing may not automatically Capsicumize programs, but it is another tool in the developer’s toolbox. It only takes a few seconds to run a program under ktrace(1) and the result is almost always a decent starting point for sandboxing your program using Capsicum. Sponsor: FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ NVMe over Fabrics Links: nvmf2 branch URL: https://github.com/bsdjhb/freebsd/tree/nvmf2 Contact: John Baldwin NVMe over Fabrics enables communication with a storage device using the NVMe protocol over a network fabric. This is similar to using iSCSI to export a storage device over a network using SCSI commands. NVMe over Fabrics currently defines network transports for Fibre Channel, RDMA, and TCP. The work in the nvmf2 branch includes a userland library (lib/libnvmf) which contains an abstraction for transports and an implementation of a TCP transport. It also includes changes to nvmecontrol(8) to add 'discover', 'connect', and 'disconnect' commands to manage connections to a remote controller. The branch also contains an in-kernel Fabrics implementation. nvmf_transport.ko contains a transport abstraction that sits in between the nvmf host (initiator in SCSI terms) and the individual transports. nvmf_tcp.ko contains an implementation of the TCP transport layer. nvmf.ko contains an NVMe over Fabrics host (initiator) which connects to a remote controller and exports remote namespaces as disk devices. Similar to the nvme(4) driver for NVMe over PCI-express, namespaces are exported via /dev/nvmeXnsY devices which only support simple operations, but are also exported as ndaX disk devices via CAM. Unlike nvme(4), nvmf(4) does not support the nvd(4) disk driver. nvmecontrol(8) can be used with remote namespaces and remote controllers, for example to fetch log pages, display identify info, etc. Note that nvmf(4) is currently a bit simple and some error cases are still a TODO. If an error occurs, the queues (and backing network connections) are dropped, but the devices stay around, with I/O requests paused. nvmecontrol reconnect can be used to connect a new set of network connections to resume operation. Unlike iSCSI which uses a persistent daemon (iscsid(8)) to reconnect after an error, reconnections must be made manually. The current code is very new and likely not robust. It is certainly not ready for production use. Experienced users who do not mind all their data vanishing in a puff of smoke after a kernel panic, and who have an interest in NVMe over Fabrics, can start testing it at their own risk. The next main task is to implement a Fabrics controller (target in SCSI language). Probably a simple one in userland first followed by a "real" one that offloads the data handling to the kernel but is somewhat integrated with ctld(8) so that individual disk devices can be exported via iSCSI or NVMe, or via both using a single config file and daemon to manage all of that. This may require a fair bit of refactoring in ctld to make it less iSCSI-specific. Working on the controller side will also validate some of the currently under-tested API design decisions in the transport-independent layer. I think it probably does not make sense to merge any of the NVMe over Fabrics changes into the tree until after this step. Sponsored by: Chelsio Communications ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Kernel Updates to kernel subsystems/features, driver support, filesystems, and more. Boot Performance Improvements Links: Wiki page URL: https://wiki.freebsd.org/BootTime BSDCan talk slides URL: https://www.bsdcan.org/events/bsdcan_2023/sessions/ session/116/slides/44/BSDCan23-Firecracker.pdf Contact: Colin Percival Colin is coordinating efforts to speed up the FreeBSD boot process. Recent efforts have moved from EC2 to the Firecracker virtual machine manager, which provides a very minimalist environment; stripping the boot process down to the bare minimum makes it easier to identify the remaining time and determine whether it can be optimized further. With some experimental patches to both FreeBSD and Firecracker, it is now possible to boot a FreeBSD kernel in under 20 ms. Some of the recent improvements were discussed in Colin’s Porting FreeBSD to Firecracker session at BSDCan. This work is supported by his FreeBSD/EC2 Patreon. Sponsor: https://www.patreon.com/cperciva ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ CI Test Harness For Bootloader Links: FreeBSD Wiki GSoC Page Github Project Link Contact: Sudhanshu Mohan Kashyap FreeBSD supports multiple architectures, file systems, and disk-partitioning schemes. I am trying to write a Lua script which would allow for testing boot loader of all the architecture combinations supported in the first and second-tier support, and provide a report on any broken combinations and expected functionality. If time permits, further exploration could be done to integrate the script into the existing build infrastructure (either Jenkins or Github Actions) to generate a comprehensive summary of the test results. Currently any changes made by developer might inhibit the ability of the operating system to boot in some specific environment. These scripts provide assurance that changes do not cause regressions for the tested environments. The scripts are designed to be efficient and much less expensive than a full make universe required today. These attributes allow developers to routinely use the script, and allow integration into the CI pipelines without undue cost. Currently script related work seems to be on track, but certainly ahead I will need to find all different kinds of QEMU recipes to test different environments. If anyone has any kind of working QEMU recipe for currently released versions of FreeBSD, feel free to send to me via mail at smk@FreeBSD.org . Sponsor: The Google Summer of Code '23 program ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Physical memory compaction for the FreeBSD kernel Links: GSoC project wiki page URL: https://wiki.freebsd.org/SummerOfCode2023Projects/ PhysicalMemoryAntiFragmentationMechanisms Differential revision 40575 URL: https://reviews.freebsd.org/D40575 Differential revision 40772 URL: https://reviews.freebsd.org/D40772 Contact: Bojan Novković Most modern CPU architectures offer performance boosts by supporting pages that are larger than the standard page size. Unfortunately, allocating such pages can fail due to a high degree of physical memory fragmentation. This work implements physical memory compaction as a means of actively reducing fragmentation in running systems. This work is part of an ongoing Google Summer of Code project, the goal of which is to add various physical memory anti-fragmentation measures to the virtual memory subsystem. Differential D40575 implements a well-known metric used for quantifying the degree of physical memory fragmentation. Differential D40772 implements physical memory compaction and adds a daemon that monitors the system and performs compaction when needed. Planned future work includes designing an appropriate benchmarking suite, running tests, and tweaking the code using feedback from reviews and test results. This is still a work in progress, so any testing, reviews, and feedback would be greatly appreciated. Sponsor: The Google Summer of Code '23 program ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Increasing MAXCPU Links: Review D36838: amd64: Bump MAXCPU to 1024 (from 256) URL: https:// reviews.freebsd.org/D36838 Contact: Ed Maste The default amd64 and arm64 FreeBSD kernel configurations currently support a maximum of 256 CPUs. A custom kernel can be built with support for larger core counts by setting the MAXCPU kernel option. However, commodity systems with more than 256 CPUs are becoming available and will be increasingly common during FreeBSD 14’s support lifecycle. We want to increase the default maximum CPU count to 1024 to support these systems "out of the box" on FreeBSD 14. A number of changes have been made to support a larger default MAXCPU, including fixing the userland maximum for cpuset_t at 1024. Changes have also been made to avoid static MAXCPU-sized arrays, replacing them with on-demand memory allocation. Additional work is required to continue reducing static allocations sized by MAXCPU and addressing scalability bottlenecks on very high core count systems, but the goal is to release FreeBSD 14 with a stable ABI and KBI with support for large CPU counts. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SquashFS port for FreeBSD kernel Links: Wiki page URL: https://wiki.freebsd.org/SummerOfCode2023Projects/ PortSquashFuseToTheFreeBSDKernel Source code URL: https://github.com/Mashijams/freebsd-src/tree/gsoc/squashfs Contact: Raghav Sharma SquashFS is a read-only file system that lets you compress whole file systems or single directories very efficiently. Support for it has been built into the Linux kernel since 2009 and is very common in embedded Linux distributions. The goal of this project is to add SquashFS support for the FreeBSD kernel, with the aim of being able to boot FreeBSD from an in-memory SquashFS file system. Currently, the driver is compatible with the 13.2 FreeBSD release. The driver is able to correctly parse the SquashFS disk file with working mount(8) support. Linux SquashFS supports many compression options like zstd, lzo2, zlib, etc…​ based on the user’s preference, and of course, our driver supports all those compressions as well. Planned future work includes adding directories, files, extended attributes, and symlinks read support. The project is still a work in progress under the mentorship from Chuck Tuffli and is expected to complete by the end of the Google Summer of Code program. Sponsor: The Google Summer of Code 2023 program ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Pf Improvements Links: D40911 URL: https://reviews.freebsd.org/D40911 D40861 URL: https://reviews.freebsd.org/D40861 D40862 URL: https://reviews.freebsd.org/D40862 D40863 URL: https://reviews.freebsd.org/D40863 D40864 URL: https://reviews.freebsd.org/D40864 D40865 URL: https://reviews.freebsd.org/D40865 D40866 URL: https://reviews.freebsd.org/D40866 D40867 URL: https://reviews.freebsd.org/D40867 D40868 URL: https://reviews.freebsd.org/D40868 D40869 URL: https://reviews.freebsd.org/D40869 D40870 URL: https://reviews.freebsd.org/D40870 Contact: Kajetan Staszkiewicz Contact: Naman Sood Contact: Kristof Provost pf(4) is one of the firewalls included in FreeBSD, and is probably the most popular. pf was created by the OpenBSD project and subsequently ported to FreeBSD. Backport OpenBSD Syntax Kajetan introduced the OpenBSD syntax of "scrub" operations in "match" and "pass" rules. Existing rules remain supported, but now OpenBSD style "scrub" configuration is also supported. pfsync Protocol Versioning The pfsync(4) protocol version can now be configured, allowing for protocol changes while still supporting state synchronisation between disparate kernel versions. The primary benefit is to allow protocol changes enabling new functionality. pfsync: Transport over IPv6 pfsync traffic can now be carried over IPv6 as well. Naman finished the work started by Luiz Amaral. SCTP There is work in progress to support SCTP in pf. That support includes filtering on port numbers, state tracking, pfsync failover and returning ABORT chunks for rejected connections. Sponsor: InnoGames GmbH Sponsor: Orange Business Services Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Network Interface API (IfAPI) Links: Original project page URL: link:https://wiki.freebsd.org/projects/ifnet Contact: Justin Hibbits Started back in 2014, the IfAPI (formerly DrvAPI) goal is to hide the ifnet(9) structure from network drivers. Instead, all accesses to members will go through accessor functions. This allows the network stack to be changed without recompiling drivers, as well as potentially allowing a single driver to support multiple versions of FreeBSD. As of now this goal has been achieved in the base system, but several ports need to be updated to use the IfAPI. There is a tool to automate most of the conversion, in tools/ifnet/convert_ifapi.sh. Documentation is also forthcoming, but could use help on that. ifnet(9) needs a lot of cleanup, as even some information in it currently is out of date. Sponsor: Juniper Networks, Inc. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Making Netgraph Lock-Free Links: Wiki Page URL: https://wiki.freebsd.org/SummerOfCode2023Projects/ LocklessSynchronizationBetweenNodesInNetgraph Repo URL: https://github.com/zinh88/epoch-netgraph Contact: Zain Khan Netgraph helps us implement custom or complex networking functions by letting us arrange kernel objects called nodes in a graph connected using hooks. Nodes may perform a well-defined set of actions on incoming packets, and may send the output to another connected node. To 'send' a packet to a neighbour can also be seen as calling a function on that neighbouring node. Now in a pre-SMP world, a thread (or the thread) would always see nodes as idle (not busy), so that their functions can immediately be called. Concurrency introduced the possibility of a busy node. Moreover, a journey of a packet also needs to take heed of changes in the structure of the graph, for example: the addressed node’s path may not remain intact due to no-longer-existing hooks or nodes in between, which may lead to cases such as referring to an object that has been freed. To counter such disasters, the existing source code uses a topology read-write mutex which protects data flow from restructuring events (and restructuring events from other restructuring events). We want to regain the same smooth flow for data which existed when concurrent cpus were not a thing. That is, data should simply never wait every time there is a restructuring event. At the same time we also obviously do not want to give the kernel reasons to panic. FreeBSD has its own set of concurrency-safe data structures and mechanisms. One of these mechanisms is Epoch. Epoch-based reclamation involves waiting for existing read-side critical sections to finish before the data structures need to be modified or reclaimed. Because the base system is being modified, this is also going to affect the design choices made before, such as queuing on messages, reference counting. This project involves a lot of testing. For now, some topology protection locks have been removed, and only simple graphs have been tested (with FreeBSD running on a VM). The real tests should be run on hardware with at least 4 CPU cores, I will do that when I get my hands on one. Sponsor: The Google Summer of Code '23 program ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Architectures Updating platform-specific features and bringing in support for new hardware platforms. SIMD enhancements for amd64 Links: SIMD dispatch framework draft URL: https://reviews.freebsd.org/D40693 Project proposal URL: link:http://fuz.su/~fuz/freebsd/ 2023-04-05_libc-proposal.txt 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, • a baseline implementation using SSE and SSE2 or alternatively 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 AMD64_ARCHLEVEL environment variable. While the current project only concerns amd64, the work may be expanded to other architectures like arm64 in the future. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Integrate mfsBSD into the release building tools Links: Wiki Article URL: https://wiki.freebsd.org/SummerOfCode2023Projects/ IntegrateMfsBSDIntoTheReleaseBuildingTools Project repository (integrate-mfsBSD-building branch) URL: https://github.com/ soobinrho/freebsd-src/tree/integrate-mfsBSD-building 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 media. It can be used for a variety of purposes, including diskless systems, recovery partitions and remotely overwriting other operating systems." Martin Matuska is both the author of the mfsBSD white paper and the maintainer of the mfsBSD repository. Purpose This project creates an additional target of the weekly snapshots of -current and -stable versions of mfsBSD images in the src/release makefile. Currently, only the release versions of mfsBSD images are produced, which means they tend to get out of sync with the tools in base. This project aims to address that problem. Location This is a GSoC 2023 (Google Summer of Code) project. As such, the official coding period is between May 29, 2023 and August 28, 2023. As a humble beginner in the open-source community, the author welcomes all comments / suggestions / pull requests in the project repository, which will be the location for all code throughout this period. Mentors: Juraj Lutter and Joseph Mingone Sponsor: The Google Summer of Code '23 program ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Cloud Updating cloud-specific features and bringing in support for new cloud platforms. FreeBSD as a Tier 1 cloud-init Platform Links: cloud-init Website URL: https://cloud-init.io/ cloud-init Documentation URL: https://cloudinit.readthedocs.io/en/latest/ cloud-init ongoing refactorization URL: https://github.com/canonical/cloud-init /blob/main/WIP-ONGOING-REFACTORIZATION.rst Contact: Mina Galić cloud-init is the standard way of provisioning servers in the cloud. Unfortunately, cloud-init support for operating systems other than Linux has been rather poor, and the lack of cloud-init support on FreeBSD is a hindrance to cloud providers who want to offer FreeBSD as a Tier 1 platform. To remedy the situation, this project aims to bring FreeBSD cloud-init support on par with Linux support. The broader plan is to lift support across all BSDs. This quarter has been going quite slowly, but I have managed to deliver a new milestone: • Ephemeral Networking classes have been rewritten and made platform independent. These are used by several cloud providers to initialize a temporary network before retrieving the actual configuration. • cloud-init has been successfully tested on Vultr. I hope that with the next release I can convince Vultr to switch their FreeBSD images to cloud-init. In addition to that, I have expanded rsyslog support for BSD. I’ve also added an rc script for cloud-init’s ds-identify, which should make zero-configuration setups orders of magnitude faster: ds-identify runs first and very quickly guesses the cloud provider the machine is running on. cloud-init then uses only that guess, instead of iterating and failing through a full list of all possible cloud providers. People building custom images can easily disable this (by removing /usr/local/etc/rc.d/dsidentify), and providing a specific listing themselves, shave off a few more milliseconds from their boot. The next steps will be to keep hacking away at the network refactoring tasks, and to add LXD support for FreeBSD, so it can be included in CI tests. The latter will include work on LXD, as well as work on the FreeBSD virtio subsystem. As always, I highly welcome early testers to checkout net/cloud-init-devel, and report bugs. Since the last report, cloud-init’s bug tracker has moved from Launchpad to GitHub, so this might reduce some friction. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 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 This project aims to port key OpenStack components such as keystone, nova, and neutron, so that FreeBSD can function as an OpenStack host. We started porting nova-novncproxy and nova-serialproxy to increase the ways to access the instance console. To lower the threshold for people who want to give it a try on the project, we also migrated our development environment from a physical machine to a virtual one. There is still a problem running bhyve VMs on top of Linux KVM. A detailed writeup for the issue can be found here. Other achievements include: • Sorting out network connectivity issues inside the instances • Able to spawn multiple instances • Porting from Python 3.8 to 3.9. In the next quarter, we will continue working on the console proxy services to make the overall workflow more fluent. The step-by-step documents for constructing a POC site can also be found in the docs repository. The patched version of each OpenStack component is under the same GitHub organization. People interested in helping with the project can first help check the documentation by following the installation guide. Feedback and help are always welcome. 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 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 To use them, when creating a virtual machine: . In Select an Image step, choose Community Images (PREVIEW) in Other items . Search FreeBSD Work in progress tasks: • Automating the image building and publishing process and merge to src/ release/. • Building and publishing ZFS-based images to Azure Marketplace □ All the required codes are merged to main branch, and can create ZFS-based images by specifying VMFS=zfs. □ Need to make the build process more automatic and collaborating with release engineering to start generating snapshots. • Building and publishing Hyper-V gen2 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 in Microsoft are working on several tasks sponsored by Microsoft: • Porting Hyper-V guest support to aarch64 □ https://bugs.freebsd.org/267654 □ https://bugs.freebsd.org/272461 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, including the recently announced M7a "EPYC" instances, which should be supported in FreeBSD 14.0-RELEASE. Weekly FreeBSD snapshots were recently changed from "UEFI" boot mode to "UEFI Preferred" boot mode, allowing them to gain the boot performance improvement offered by UEFI while still supporting "bare metal" and "previous generation" instance types which are not compatible with UEFI. This change will be present in FreeBSD 14.0-RELEASE. The EC2 boot scripts were recently updated to support IMDSv2. This change will be present in FreeBSD 14.0-RELEASE. If users of FreeBSD 13.2 require any of these updates, the author can provide FreeBSD "13.2-RELEASE plus updates" AMIs. 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: • fernape@ has been appointed as a new Doceng team member. • The www/gohugo port maintainership has been transferred to doceng@ since it is a critical part of our documentation infrastructure. This was agreed with the former maintainer. • Improvements to the translation workflow (described in the following sections). Porter’s Handbook USES=nextcloud has been documented. FDP Primer A new chapter focusing on Weblate has been added to the FreeBSD Documentation Project Primer for New Contributors. This comprehensive chapter provides step-by-step guidance on joining the FreeBSD translators team, both for translating online on Weblate and offline. It offers valuable insights and practical suggestions for efficient translation, proofreading, and testing processes. Furthermore, this chapter equips contributors with the necessary knowledge to formally submit their translations to the documentation repository, ensuring a seamless integration of their work. 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/ Q2 2023 Status • 15 languages • 183 registered users • New Weblate server The FreeBSD Weblate instance now operates on a dedicated server, significantly improving its speed and enhancing the efficiency of translation work. Our heartfelt appreciation goes to ebrandi@ for providing this hardware upgrade. 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: 32%) • Norwegian (nb-no) (progress: 1%) • Persian (fa-ir) (progress: 3%) • Polish (progress: 1%) • Portuguese (pt-br) (progress: 22%) • Sinhala (si) (progress: 1%) • Spanish (es) (progress: 33%) • 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 is being reworked. 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 is divided into four phases: 1. Redesign of the Documentation Portal Create a new design, responsive and with global search. (Complete) 2. Redesign of the Manual Pages on web Scripts to generate the HTML pages using mandoc. (Complete) Public instance on https://man-dev.FreeBSD.org 3. Redesign of the Ports page on web Ports scripts to create an applications portal. (Work in progress) 4. Redesign of the FreeBSD main website New design, responsive and dark theme. (Work in progress) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 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 ports had various updates: • devel/qt5-webengine was repaired when building with Clang 16. This is in preparation for the upcoming release of FreeBSD 14. • devel/qt5-qmake was repaired to deal with an edge case where installing qmake on an otherwise Qt-less system would cause weird errors. Qt6 ports had various updates: • devel/qt6-tools was repaired when building with Clang 16. This is preparation for the upcoming release of FreeBSD 14. The accessibility/at-spi2-core port — essential for accessible technologies on the desktop — was updated to release 2.48.0. The accessibility/at-spi2-core port now has better support for non-X11 desktops. This is an improvement for Wayland-based systems. Thanks to Jan Beich for landing that. The graphics/poppler port — a base for many PDF viewers — was updated to 23.05. The ports-mgmt/packagekit-qt port is a new addition to the tree to pave the way for graphical package managers on FreeBSD. 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 updated to 5.105, .106 and .107. • KDE Gear updated to 23.04.0, then .1 and .2 with bugfixes. • KDE Plasma Desktop was updated to version 5.27.4, then .5 and .6 with bugfixes. Related Ports Deprecations: • graphics/ikona, an icon-viewer written in Rust with Qt bindings, has been abandoned upstream. • polish/kadu, a chat application once popular in Poland, is deprecated and upstream has disappeared. • sysutils/plasma5-ksysguard, a system monitoring application, is deprecated upstream and will no longer update. Updates: • astro/kstars, an interactive planetarium, was updated to release 3.6.4. • devel/qcoro, a C++ coroutines implementation, was updated to 0.9.0. • devel/qtcreator, an integrated development environment for Qt, C++, and more, was updated to release 10.0.2. • games/gcompris-qt, an education suite for children aged 3-12, was updated to release 3.2. • graphics/kphotoalbum, a photo album and display utility, was updated to release 5.10.0. • net-im/tokodon, a Mastodon social network client, joins KDE Gear. • textproc/kdiff3, a text-differencing utility, was updated to release 1.10.1. New Software: • devel/kommit, a Git client, was added. It is a rename of previous package gitklient. • multimedia/kasts is a new podcast-listening and enjoyment application from the KDE community. • textproc/arianna is a mobile-oriented e-book reader from the KDE community that makes reading FreeBSD documentation a joy. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 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 Upstream has released GCC 13. As announced in the past status report, I plan to attempt an update of GCC_DEFAULT right from the first GCC 13 release, thus much of this quarter’s work has been in preparation of this. With the release of GCC 13.1 (first GCC 13 release: I remind that GCC counts minor version releases starting from 1), two new ports have been created in the ports tree: • lang/gcc13, tracking GCC 13 releases; • lang/gcc14-devel, tracking snapshots from the new GCC 14 upstream branch. The *-devel ports Support for .init_array and .fini_array has been enabled. FreeBSD supports both since commit 83aa9cc00c2d. The default bootstrap option on i386, amd64, and aarch64 has been reverted from LTO_BOOTSTRAP to STANDARD_BOOTSTRAP: • LTO bootstrap produces too many failures on the package builders for those architectures • LTO_BOOTSTRAP remains available for users who want it. Those changes will be forwarded to the production ports. The production ports Upstream has released GCC 13, for which the new port lang/gcc13 has been created. GCC 11 and GCC 12 have been updated upstream and a new release of GCC 10 is planned. All corresponding ports now need to be updated. To ease the work of both ports maintainers and users, I plan to test and update together all the following changes: • updates of lang/gcc10, lang/gcc11, lang/gcc12; • update of GCC_DEFAULT to 13; • enabling of .init_array and .fini_array on the production ports; • switching back from LTO_BOOTSTRAP to STANDARD_BOOTSTRAP on the production ports. This will provide the following advantages: • more testing with less exp-runs; • fewer builds for ports users. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Puppet Links: Puppet URL: https://puppet.com/docs/puppet/latest/puppet_index.html Contact: Puppet Team Puppet is a Free Software configuration management tool, composed of a source of trust (Puppet Server) that describes the expected configuration of machines with a domain-specific language, and an agent (Puppet Agent) on each node which enforces that the actual configuration matches the expected one. An optional database (PuppetDB) can be setup for reporting and describing advanced schemas where the configuration of a machine depends on the configuration of another one. The Puppet team is maintaining ports for Puppet and related tools. Puppet 8 has been recently released and has been added to the ports tree. Puppet 6 has reached End of Life and has been deprecated. It is now expired. Users of Puppet 6 are therefore advised to update to Puppet 7 or Puppet 8. For now, Puppet 7 remains the default Puppet version for ports depending on Puppet. The Puppet Community is hard at work making sure the various Puppet modules work with the latest code and at the time of writing this report, updating to Puppet 8 may be challenging. The situation is getting better every day, and we expect to switch to Puppet 8 as the default version of Puppet in a few months, when the wave of module updates is finished. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ MITRE Caldera on FreeBSD Links: MITRE Caldera URL: https://caldera.mitre.org/ Red Canary URL: https://www.redcanary.com/ Contact: José Alonso Cárdenas Márquez MITRE Caldera is a cybersecurity platform designed to easily automate adversary emulation, assist manual red teams, and automate incident response. It is built on the MITRE ATT&CK® framework and is an active research project at MITRE. MITRE Caldera (security/caldera) was added to the ports tree in April 2023. This port includes support for the Atomic Red Team Project used by the MITRE Caldera atomic plugin. The main goal of this work is enhancing visibility of FreeBSD as a useful platform for information security or cybersecurity. Additionally, you can test a MITRE Caldera infrastructure easily using https:// github.com/alonsobsd/caldera-makejail or https://github.com/AppJail-makejails/ caldera from AppJail. AppJail is a good tool for managing jail containers from the command line. People interested in helping with the project are welcome. Current version: 4.2.0 To Do • Add Caldera testing infrastructure makejail. • Add FreeBSD to platforms officially supported by MITRE Caldera, see https:/ /github.com/mitre/caldera/pull/2752. • Add FreeBSD to platforms officially supported by Red Canary, see https:// github.com/redcanaryco/atomic-red-team/pull/2450. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Wazuh on FreeBSD Links: Wazuh URL: https://www.wazuh.com/ Contact: José Alonso Cárdenas Márquez Wazuh is a free and open source platform used for threat prevention, detection, and response. It is capable of protecting workloads across on-premises, virtualized, containerized, and cloud-based environments. The Wazuh solution consists of an endpoint security agent, deployed to the monitored systems, and a management server, which collects and analyzes data gathered by the agents. Wazuh features include full integration with Elastic Stack and OpenSearch, providing a search engine and data visualization tool through which users can navigate security alerts. Wazuh porting to FreeBSD was started by Michael Muenz. His first Wazuh addition to the ports tree was security/wazuh-agent in September 2021. In July 2022, I took maintainership of this port and started porting other Wazuh components. Currently, all Wazuh components are ported or adapted: security/wazuh-manager, security/wazuh-agent, security/wazuh-server, security/wazuh-indexer, and security/wazuh-dashboard. On FreeBSD, security/wazuh-manager and security/wazuh-agent are compiled from Wazuh source code. security/wazuh-indexer is an adapted textproc/opensearch used for storing agents data. security/wazuh-server includes FreeBSD-oriented adaptions to configuration files. Runtime dependencies comprise security/ wazuh-manager, sysutils/beats8 (filebeat), and sysutils/logstash8. security/ wazuh-dashboard uses an adapted textproc/opensearch-dashboards and the wazuh-kibana-app plugin generated from wazuh-kibana-app source code for FreeBSD. The main goal of this work is enhancing visibility of FreeBSD as a useful platform for information security or cybersecurity. Additionally, you can easily test a Wazuh single-node infrastructure (All-in-one) using https://github.com/alonsobsd/wazuh-makejail or https:// github.com/AppJail-makejails/wazuh from AppJail. AppJail is a good tool for managing jail containers from the command line. People interested in helping with the project are welcome. Current version: 4.4.4 TODO • Add Wazuh cluster-mode infrastructure makejail (Work in progress) • Add FreeBSD to platforms officially supported by Wazuh Inc; see https:// github.com/wazuh/wazuh-kibana-app/pull/5413 • Add FreeBSD SCA Policy (Work in progress) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 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. PkgBase.live Links: Website URL: https://alpha.pkgbase.live/ Source URL: https://codeberg.org/pkgbase Contact: Mina Galić PkgBase.live, an unofficial repository for the FreeBSD PkgBase project, is back alive. As a service, PkgBase.live was inspired by https://up.bsd.lv/, which provided freebsd-update(8) for STABLE and CURRENT branches. up.bsd.live itself has gone on hiatus, so it was all the more reason to bring back PkgBase.live. Right now, we provide builds for: • FreeBSD 13.2-RELEASE • FreeBSD 13-STABLE • FreeBSD 14-CURRENT each for the following platforms: • amd64 • aarch64 • armv7 • i386 You may notice that RISCv64 is gone for now. The hardware is a powerful VPS in Vultr. The server and the jails running build jobs and serving packages are "self-hosting", meaning they were installed and are kept up-to-date with PkgBase. Because we have not figured out yet how to configure Vultr’s IPv6 in FreeBSD jails, PkgBase.live is not available over IPv6 for now. If you have experience with that, please contact us! Along with users and testers, we still highly encourage copy-cats. Hardware for PkgBase is kindly sponsored by a member of the FreeBSD community. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 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.5 was released, containing a number of bugfixes and features to set attributes (i.e. jail sysctl variables) from various contributors. It will be available in the 2023Q3 quarterly package set. 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. All Potluck containers have been rebuilt as FreeBSD 13.2 based images and are signed with Pot signify now. A Beginner’s Guide to Building a Virtual Datacenter on FreeBSD with Ansible, Pot and More has been written, explaining how a complex environment based on Pot and Potluck can be deployed with Ansible playbooks, including example nodes like MariaDB, Prometheus, Grafana, nginx, OpenLDAP or Traefik and container orchestration managed by Nomad and Consul. A patch by the pot team to improve Nomad security, a scheduler and orchestrator which supports Pot through sysutils/nomad-pot-driver, has been accepted upstream and will be part of Nomad 1.6.0. As always, feedback and patches are welcome. Sponsor: Honeyguide Group From nobody Thu Jul 27 20:00:54 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 4RBhTp5w25z4pXSF for ; Thu, 27 Jul 2023 20:01:02 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (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 4RBhTp0kf7z3HRt for ; Thu, 27 Jul 2023 20:01:02 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aetern.org header.s=fm3 header.b=MD6hiYp4; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=VjIWbtB2; spf=pass (mx1.freebsd.org: domain of yuri@aetern.org designates 64.147.123.24 as permitted sender) smtp.mailfrom=yuri@aetern.org Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id BAD61320092B for ; Thu, 27 Jul 2023 16:00:59 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Thu, 27 Jul 2023 16:00:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to; s=fm3; t=1690488059; x=1690574459; bh=ps jYY7S8pFY+BibSYRUZjJJMKGBxdtXZ/4LecZahs9w=; b=MD6hiYp4VfBcGp9WT9 Jgvy9Pigsa5rZkqtMLMd2dm0++hFxg8UA/bTrLeCCFlDRzmw19a01pyPZ6TTtde1 qsRRIetT9KWjJ+2u3y7tUnheAU2CR3XpDmWF9lUhvvtGR//Y2xE28auM+/WBb1qg ZgYC/+xSsQ+4MfJRSiVpKFLnfS4XqGRxxN6TOJCDGALLMoxnNk5pioJaJmXZ5ALc lEjDHpGsH5LE4RC4f2Eto+UpSIKQ4hMI3Wxui8r7lTdh3PqAIITWb6BK9FPv8bK2 Fw9BZNreyP9OGIeWOsSU/jaKjcNYGcz0DH+5ly5Xd2pR6va3b3+4Y8YIPReScPAF TctQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:message-id:mime-version:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1690488059; x=1690574459; bh=psjYY7S8pFY+B ibSYRUZjJJMKGBxdtXZ/4LecZahs9w=; b=VjIWbtB2fgMnMVxr2fBkayrtS8ar3 tAAaDAFxInc7LetHo0SDYrSKaiHdaVxg0APbK2nwd8qO+PrcfQpyavvyqJwpNlwk +P390XpJvXqBv38Bbmqf1dR+AFgerpujMOTjLMwArvBeow37kJJTzUpgXdJqqFrZ T+/dS4CBL0FJ9eyL6WlYeOsyKomGe+xAOw3c2ff+swmA5MY9SLX8TH0svA06tMuK 5tFOYJkIiqi4GXK+QoUrEESWYEuD8SlFl2Sz6Z8mEU3HTepcHEvbxwf6Za6Vyfna zF4crZWgpIbKkPPgDlROo786iX0u0i7Wvk1FJ4ETCaS2sSPwyA79OdhiQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrieeggdduudejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfvhffutgfgsehtjeertd dtvdejnecuhfhrohhmpegjuhhrihcuoeihuhhrihesrggvthgvrhhnrdhorhhgqeenucgg tffrrghtthgvrhhnpeegveekgeeufeduheejleeltddvfeeivddvfefhvdejgfefjeelge ehhedutedtueenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr ohhmpeihuhhrihesrggvthgvrhhnrdhorhhg X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Thu, 27 Jul 2023 16:00:58 -0400 (EDT) Message-ID: <217425d1-de2f-a1c0-7f26-9c95963f03f5@aetern.org> Date: Thu, 27 Jul 2023 22:00:54 +0200 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 Content-Language: en-US To: current@freebsd.org From: Yuri Subject: panic: Segment size is not aligned (smartpqi related) Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4RBhTp0kf7z3HRt X-Spamd-Bar: / X-Spamd-Result: default: False [-0.39 / 15.00]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.24]; R_DKIM_ALLOW(-0.20)[aetern.org:s=fm3,messagingengine.com:s=fm3]; XM_UA_NO_VERSION(0.01)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; local_wl_from(0.00)[yuri@aetern.org]; DKIM_TRACE(0.00)[aetern.org:+,messagingengine.com:+]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_from Hi, I'm getting the panic below trying to install latest current snapshot (20230720) on HPE Proliant 380 Gen10. There don't seem to be any recent changes to smartpqi driver itself so it's likely something else changed as this HBA didn't have *this* specific problem previously on this system. The panic happens after selecting the disk for ZFS pool and confirming that its contents are going to be destroyed. What's interesting, doing `gpart destroy -F da0` from installer shell didn't trigger this. I have not tried to bisect this yet as it's very time consuming (uploading iso images to remote site takes hours) and hoping someone could point out the problem. panic: Segment size is not aligned cpuid = 53 KDB: stack backtrace vpanic() panic() bounce_bus_dmamap_load_ma() at bounce_bus_dmamap_load_ma+0x402 bus_dmamap_load_mem() at bus_dmamap_load_mem+034a bus_dmamap_load_ccb() at bus_dmamap_load_ccb+05d pqi_map_request() at pqi_map_request+0x54 smartpqi_cam_action() at smartpqi_cam_action+0xca1 xpt_run_devq() at xpt_run_devq+0x2e9 xpt_action_default() at xpt_action_default+0x3fd dastart() at dastart+0x327 xpt_run_allocq() at xpt_run_allocq+0x9f dastrategy() at dastrategy+0x6d g_disk_start() at g_disk_start+0x36f g_io_request() at 0x2c2 g_io_request() at 0x2c2 g_io_request() at 0x2c2 g_dev_strategy() at g_dev_strategy+0x155 physio() at physio+0x4a1 devfs_write_f() at devfs_write_f+0xf3 dofilewrite(() at dofilewrite+0x82 sys_write() at sys_write+0xc2 amd64_syscall() at amd64_syscall+0x138 fast_syscall_common() at fast_syscall_common+0xf8 --- syscall (4, FreeBSD ELF64, write), rip = 0x2899740792ba, rsp = 0x289971621568, rbp = 0x289971621c00 --- From nobody Fri Jul 28 16:57:17 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 4RCDMj32jRz4pMfL for ; Fri, 28 Jul 2023 16:57:37 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic306-20.consmr.mail.gq1.yahoo.com (sonic306-20.consmr.mail.gq1.yahoo.com [98.137.68.83]) (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 4RCDMh0vDjz3vwc for ; Fri, 28 Jul 2023 16:57:35 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=FshsX6eo; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.68.83 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=1690563453; bh=8uKbpuQ+qprHvzesDJ3d8J2crzme3aUkpJscHPDGGwg=; h=From:Subject:Date:To:References:From:Subject:Reply-To; b=FshsX6eoQRE1nZvW7WSoybpfrPBhOqYfn+799wHhtUN1BDCBY+AjFW3gFB2JOACHZVtQxiMZE8iS2QBoAGkPtIRLQpIJ4z8vK5ocDPP8SJVm6Li5KHKcbVQ9NnVO3bQ126U03eWkW5P/fKMV+WRQZq9uLJdH7m+cvQdV5UwYPkxLSgX75Bkg1VQ5m43Ifr4Y5e79/7hDTpXktJZOOTlNQ0YsMda5Oy2+SI2EC81bk1nBmXgWhJTrNy4fOQC0pNayCoHAlY9eaQTQjTWivLYfdu8jbVV1ijJ7Bsru8kvvdGjZNjgkucF+cWBWkrXTxpIJA+fdfh12GfCsSOGJeEqEwA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1690563453; bh=uovPjThGbeux/oZ+ckH0OrEE0LGXDAgC/rP11Uo3PxF=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=SGTgnTXqKZQUuqg51seDY82//q87HUEHFDx+WbJKnbGKCpFrAsPcunBeF3TT/zS6hu1lDqSSigSBH7/IMCQccDdwqD3mxm4FsgQIKpuXV34eDYGL7wqoKLMVkYRld4eoSkrBLC1IqzSkJA2fy4uIEggOcIENor8eyAe2N2lAufFJW2PcbwxsJMWL4HdS0ZIfgRWVyeFtOB0pvUnG5JBdl9isR//mH7Aesif+7zPCjsW8UXa9TgVfa4JRzYNdV5Pg3VVrRITHiomqg7hYjnFMA00+ml0j/9ec07Mqq0VjA4UoLOiqmXcaVd5cPes+4vgqfedvNtrumFz76T0pFqkMpg== X-YMail-OSG: IM6ppncVM1mxjRzUwSl6r7uPc5y88BBPVfkcRFApPK79HnHrFQbHQj_M1a697AQ k5OkDk8wJ7XRN36or.XdAqaX35r81cp5yjrHGFM2.xHfRqJwByy0EBJwc7U.g1iOOpxX8Qm3lsOc SYuhl7FoKhSg.k8KQ2zG0.lIyxBkLssGw1u1EzMGRgEkOSLMBytef7yz2W9wo2yBeOpDoQc1_iij MkiNkia37rAMlLGlAVwI_ef4Z4k5f_wD.jSp_qjdDfBXPGk80f9zNzv6z85IEz9GdV32GomILYZc P94Ggo85pF4SFfviB1jpsih.4sVBH1cLuNUkclVFpVotMf7ze2p_C3xh1_bPYffq2Kr.rrrwHud1 kidcnR31XJMcCCJMk3AdNHGsTQzoExcxD.nwMbdtRhbaJlu.jMyUZ8UEL36WoNoW5VA6tcxHYut3 USnVmcSp7TP3QRMe.JpYuAMjQMIr9NT6UCW9epFEeMQ0h5Tj63HMGA47V799SyXcOcCa7FzrZyr_ KFGJhYe0PHsV3nmka17g0p6kTIWg.S26oJiTG7wuGvdTDnmu_6AbCAYbP3hS827Aa7mas2rRxyZz 07ZPGpsBx2zc5p1wg9cnxT6FIyCqQmWh.TWINvNQLzbDRKRSK0kRpLFICfAKTipucHF5x8qBy74q 5LoqcTo1JB83WaDZFdbPPqN71_EtZPJOeLS3nM41Wxj5e_xBWkljjjtMYzg64erXnk4bayXEsjJ_ 0UZlwpXdvrmIQoMBrvJ6pvCIY1IptGBZRbD6tbb685j5tbPXrOeZXiSoS9jAhREjEb5G5dXQVoCF XLxRP0EqJlz8wLl4OOiSeZbZTZ2VwFkrrr4lPW1aWFpNLmwOY4HXNduIpdz_StcSm.mTQrAO9CX9 3t2l4IsvkMRKJKaV5il_HPNVmFP8ixGrM_OGrYxA5Ur6wf0LHPTGxsUmPBgteXhnqP21p12xx19m 6UxRKcQLVt3465NsXtoYuLeHrMnx2x9.Esb5cmEyS7IrFX2V7ox_S4SZlFQnr3cVIpFZwOFW2rd1 EU4aGrcWcANDZoXGGXkpEsA.iyo3l8QHz64Xzhov4VXDd7g.FNxHFVQ0Y5PkcGTlq8Sgor2gBxNK ZjLs3O3DUP6AVNJJTp4zFGXyvT_fW0jJ99bxH8IrSxYSIWbxv5ChTuEQVNQh.ERnB7h3JzXS2Anr ezr3_P4LxFeMIU2i4RyN3JG.LzyH2CA_qvfP73sp3aLDqfS0HIOLQtWjagG2V18b_IQq_HfDdFnk UbOZhlilOC88B.mw9lpQmydlf6vim_PXc5CajJv9hf1Gg8AssicuGyvkScxYuhFN1vexEatPk50V 6UhD82kZrsa4qBJxnU11Cu83DObNhyQF7XKLiz5e1ZQaoFTRX5Bidsz3d4S4BGpIuOLZrI5DHqj6 Kyc92nbLB_0kmpU6F1xXj7PAmJAk_FpYdrCewvHK9lVKZsNdtdp0e93uQagnqMPBu4iVp28H6XgW aYMBlAhDpv40jaF3P.94Fww5QkrV6ZSG1dooOqo7ghE9aGlKMCy_in8EoEvQ9jWahEsDUqNBjtQF ZYRkaHkBkHMQF2xYl7f9TS0F0JEynVxPuMdbeq4RXtgjcvjm5T3jxfwgITHm.FqGN3TJgMjjZXP3 rWRSgIpMobhaiRWW8daqnfubrzSXQrukkW5V585TTAaaNENIiad9kQ9lCf3RPrg2a8f7n6lVaqlN Te_7c3T3cXxwuB3exIJaiC2GQfoJTvyG3HkervnTXOc.zDPFXTYZXMOmsx_.3kAqU8Dz7xa5eIZZ GKPQiqq5tNEy4azzPIRE86YMrOL9ykR52MJqbA.uOYLJn8Hz51qsxaTpoJCyRRcOg89o7evrserE nZluxzOJ4t5GxoUGr6gKaucfLrUDwxHIqXMkY6etpnWQmaUM9ZLTCO3j2YDzYrUUStplSCaI_R1x pu_rtrs5VLoW5_Gb37LFnih46uqQ7FNxQBx9DAvPWXz71L5q88xMnBUEFjHxhGgojMzhU6fzE0W2 fBgjrUQRoJ_glwuAXv1Dm7mHtUiZeK_5Mbqi5dPTyHmLk99ADcqw6UsJ0.y835jegym.Q9PAN4Lh h0GhKUtwrCj9vjqtHQsOedBB6FymfSNOzzFbqrsYAka2PFv9TcDYoMWwAFAmklf_DmlFgDvWA0Dt 4lCJB99VYYnanMesRnh7WFhlWUYUyibivOAHt15CXiMpI4hYBnEzzVAbZaZFiY0pjYXMXuFuEdty cqNqe8trVaf__uLLv4xLO1oMD1rg2xhGZKbkJDpKrDp4XysT8lgv8Qre1 X-Sonic-MF: X-Sonic-ID: 79484711-8b17-4b75-868e-730c3e80a43c Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.gq1.yahoo.com with HTTP; Fri, 28 Jul 2023 16:57:33 +0000 Received: by hermes--production-bf1-7c4db57b6-49kxr (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 53a96671854126c70e5d62001f81909c; Fri, 28 Jul 2023 16:57:29 +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 \(3731.700.6\)) Subject: delete-old status under /usr/ (amd64 context example) Message-Id: <686114F4-C1CE-4269-A1A8-57DEE897B2A0@yahoo.com> Date: Fri, 28 Jul 2023 09:57:17 -0700 To: Current FreeBSD X-Mailer: Apple Mail (2.3731.700.6) References: <686114F4-C1CE-4269-A1A8-57DEE897B2A0.ref@yahoo.com> X-Spamd-Result: default: False [-3.43 / 15.00]; NEURAL_HAM_SHORT(-0.99)[-0.995]; NEURAL_HAM_MEDIUM(-0.99)[-0.991]; NEURAL_HAM_LONG(-0.94)[-0.944]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.68.83:from]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[yahoo.com]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.68.83:from] X-Rspamd-Queue-Id: 4RCDMh0vDjz3vwc X-Spamd-Bar: --- I created a /tmp/main-amd64-installed-from-scratch/ and installed into = it with: installworld distrib-dirs distribution DB_FROM_SRC=3D1 installkernel in a boot context with: # uname -apKU FreeBSD amd64-ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT amd64 1400093 #106 = main-n264334-215bab7924f6-dirty: Tue Jul 25 18:49:51 PDT 2023 = root@amd64-ZFS:/usr/obj/BUILDs/main-amd64-nodbg-clang/usr/main-src/amd64.a= md64/sys/GENERIC-NODBG amd64 amd64 1400093 1400093 I use delete-old and delete-old-libs with -DBATCH_DELETE_OLD_FILES in my update procedures and have for years. delete-old use is a step in scripts, not a manual operation. (delete-old-libs use requires more timing control and so is less automatic.) I find the following when I look for potential old files in /usr/ = compared to what ended up in /tmp/main-amd64-installed-from-scratch/usr/ . Much = of the output seems to be old files that are still around but likely should not be. # diff -rq /tmp/main-amd64-installed-from-scratch/usr /usr \ | grep "Only in /usr/" | grep -v -E = "(/usr/local:|/usr/obj:|/usr/lib/debug/boot: kernel\.)" diff: = /tmp/main-amd64-installed-from-scratch/usr/share/locale/nn_NO.ISO8859-1/LC= _MESSAGES: Too many levels of symbolic links diff: = /tmp/main-amd64-installed-from-scratch/usr/share/locale/nn_NO.ISO8859-15/L= C_MESSAGES: Too many levels of symbolic links diff: = /tmp/main-amd64-installed-from-scratch/usr/share/locale/sl_SI.ISO8859-2/LC= _MESSAGES: No such file or directory Only in /usr/include/dev/hwpmc: hwpmc_beri.h Only in /usr/include/dev/wg: compat.h Only in /usr/include/dev/wg: crypto.h Only in /usr/include/dev/wg: version.h Only in /usr/include/dev/wg: wg_cookie.h Only in /usr/include/dev/wg: wg_noise.h Only in /usr/include/machine: ppireg.h Only in /usr/include/machine: timerreg.h Only in /usr/include/sys: _cscan_atomic.h Only in /usr/include/sys: _cscan_bus.h Only in /usr/lib/debug/usr/bin: timeout.debug Only in /usr/lib/debug/usr/tests/cddl/usr.sbin/dtrace/amd64: kinst Only in /usr/lib/debug/usr/tests/usr.bin: timeout Only in /usr/lib/include/dev/hwpmc: hwpmc_beri.h Only in /usr/lib/include/dev/wg: compat.h Only in /usr/lib/include/dev/wg: crypto.h Only in /usr/lib/include/dev/wg: version.h Only in /usr/lib/include/dev/wg: wg_cookie.h Only in /usr/lib/include/dev/wg: wg_noise.h Only in /usr/lib/include/machine: ppireg.h Only in /usr/lib/include/machine: timerreg.h Only in /usr/lib/include/sys: _cscan_atomic.h Only in /usr/lib/include/sys: _cscan_bus.h Only in /usr/share/certs/trusted: = Camerfirma_Chambers_of_Commerce_Root.pem Only in /usr/share/certs/trusted: Camerfirma_Global_Chambersign_Root.pem Only in /usr/share/certs/trusted: Certum_Root_CA.pem Only in /usr/share/certs/trusted: Chambers_of_Commerce_Root_-_2008.pem Only in /usr/share/certs/trusted: D-TRUST_Root_CA_3_2013.pem Only in /usr/share/certs/trusted: EC-ACC.pem Only in /usr/share/certs/trusted: = GeoTrust_Primary_Certification_Authority_-_G2.pem Only in /usr/share/certs/trusted: Global_Chambersign_Root_-_2008.pem Only in /usr/share/certs/trusted: OISTE_WISeKey_Global_Root_GA_CA.pem Only in /usr/share/certs/trusted: QuoVadis_Root_CA.pem Only in /usr/share/certs/trusted: Sonera_Class_2_Root_CA.pem Only in /usr/share/certs/trusted: Staat_der_Nederlanden_Root_CA_-_G3.pem Only in /usr/share/certs/trusted: SwissSign_Platinum_CA_-_G2.pem Only in /usr/share/certs/trusted: = Symantec_Class_1_Public_Primary_Certification_Authority_-_G6.pem Only in /usr/share/certs/trusted: = Symantec_Class_2_Public_Primary_Certification_Authority_-_G6.pem Only in /usr/share/certs/trusted: Trustis_FPS_Root_CA.pem Only in /usr/share/certs/trusted: = VeriSign_Universal_Root_Certification_Authority.pem Only in /usr/share/certs/trusted: = Verisign_Class_1_Public_Primary_Certification_Authority_-_G3.pem Only in /usr/share/certs/trusted: = Verisign_Class_2_Public_Primary_Certification_Authority_-_G3.pem Only in /usr/share/locale/hr_HR.ISO8859-2: LC_MESSAGES Only in /usr/share/locale/nl_BE.ISO8859-1: LC_MESSAGES Only in /usr/share/locale/nl_BE.ISO8859-15: LC_MESSAGES Only in /usr/share/locale/sr_RS.ISO8859-2: LC_MESSAGES Only in /usr/share/locale/zh_TW.Big5: LC_NUMERIC Only in /usr/share/man/man4/aarch64: aw_gpio.4.gz Only in /usr/share/man/man4/aarch64: aw_mmc.4.gz Only in /usr/share/man/man4/aarch64: aw_rtc.4.gz Only in /usr/share/man/man4/aarch64: aw_sid.4.gz Only in /usr/share/man/man4/aarch64: aw_spi.4.gz Only in /usr/share/man/man4/aarch64: aw_syscon.4.gz Only in /usr/share/man/man4/aarch64: bcm283x_pwm.4.gz Only in /usr/share/man/man4: ce.4.gz Only in /usr/share/man/man4: cp.4.gz Only in /usr/share/man/man4/i386: ce.4.gz Only in /usr/share/man/man4/i386: cp.4.gz Only in /usr/share/man/man4: if_an.4.gz Only in /usr/share/man/man5: portsnap.conf.5.gz Only in /usr/share/man/man8: apm.8.gz Only in /usr/share/man/man8: apmconf.8.gz diff: /tmp/main-amd64-installed-from-scratch/usr/tests/local: No such = file or directory diff: = /tmp/main-amd64-installed-from-scratch/usr/tests/sys/pjdfstest/tests/tests= /tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/t= ests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tes= ts/tests/tests/tests/tests/tests/tests: Too many levels of symbolic = links Only in /usr/share/man/man9: DOMAIN_SET.9.gz Only in /usr/share/man/man9: vm_page_sbusy.9.gz Only in /usr/share/man/man9: vm_page_sleep_if_busy.9.gz Only in /usr/share/man/man9: vm_page_xbusy.9.gz Only in /usr/share/openssl/man/man1: asn1parse.1.gz Only in /usr/share/openssl/man/man1: ca.1.gz Only in /usr/share/openssl/man/man1: ciphers.1.gz Only in /usr/share/openssl/man/man1: cms.1.gz Only in /usr/share/openssl/man/man1: crl.1.gz Only in /usr/share/openssl/man/man1: crl2pkcs7.1.gz Only in /usr/share/openssl/man/man1: dgst.1.gz Only in /usr/share/openssl/man/man1: dhparam.1.gz Only in /usr/share/openssl/man/man1: dsa.1.gz Only in /usr/share/openssl/man/man1: dsaparam.1.gz Only in /usr/share/openssl/man/man1: ec.1.gz Only in /usr/share/openssl/man/man1: ecparam.1.gz Only in /usr/share/openssl/man/man1: enc.1.gz Only in /usr/share/openssl/man/man1: engine.1.gz Only in /usr/share/openssl/man/man1: errstr.1.gz Only in /usr/share/openssl/man/man1: gendsa.1.gz Only in /usr/share/openssl/man/man1: genpkey.1.gz Only in /usr/share/openssl/man/man1: genrsa.1.gz Only in /usr/share/openssl/man/man1: list.1.gz Only in /usr/share/openssl/man/man1: nseq.1.gz Only in /usr/share/openssl/man/man1: ocsp.1.gz Only in /usr/share/openssl/man/man1: openssl-tsget.1.gz Only in /usr/share/openssl/man/man1: passwd.1.gz Only in /usr/share/openssl/man/man1: pkcs12.1.gz Only in /usr/share/openssl/man/man1: pkcs7.1.gz Only in /usr/share/openssl/man/man1: pkcs8.1.gz Only in /usr/share/openssl/man/man1: pkey.1.gz Only in /usr/share/openssl/man/man1: pkeyparam.1.gz Only in /usr/share/openssl/man/man1: pkeyutl.1.gz Only in /usr/share/openssl/man/man1: prime.1.gz Only in /usr/share/openssl/man/man1: rand.1.gz Only in /usr/share/openssl/man/man1: req.1.gz Only in /usr/share/openssl/man/man1: rsa.1.gz Only in /usr/share/openssl/man/man1: rsautl.1.gz Only in /usr/share/openssl/man/man1: s_client.1.gz Only in /usr/share/openssl/man/man1: s_server.1.gz Only in /usr/share/openssl/man/man1: s_time.1.gz Only in /usr/share/openssl/man/man1: sess_id.1.gz Only in /usr/share/openssl/man/man1: smime.1.gz Only in /usr/share/openssl/man/man1: speed.1.gz Only in /usr/share/openssl/man/man1: spkac.1.gz Only in /usr/share/openssl/man/man1: srp.1.gz Only in /usr/share/openssl/man/man1: storeutl.1.gz Only in /usr/share/openssl/man/man1: ts.1.gz Only in /usr/share/openssl/man/man1: verify.1.gz Only in /usr/share/openssl/man/man1: version.1.gz Only in /usr/share/openssl/man/man1: x509.1.gz Only in /usr/share/openssl/man/man3: ECDH_get_ex_data.3.gz Only in /usr/share/openssl/man/man3: ECDH_get_ex_new_index.3.gz Only in /usr/share/openssl/man/man3: ECDH_set_ex_data.3.gz Only in /usr/share/openssl/man/man3: ERR_GET_FUNC.3.gz Only in /usr/share/openssl/man/man3: EVP_PKEY_CTX_hkdf_mode.3.gz Only in /usr/share/openssl/man/man3: EVP_PKEY_set_alias_type.3.gz Only in /usr/share/openssl/man/man3: EVP_aes.3.gz Only in /usr/share/openssl/man/man3: EVP_aria.3.gz Only in /usr/share/openssl/man/man3: EVP_camellia.3.gz Only in /usr/share/openssl/man/man3: EVP_des.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_bytes.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_cleanup_entropy_fn.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_cleanup_nonce_fn.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_free.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_generate.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get0_master.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get0_private.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get0_public.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get_entropy_fn.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get_ex_data.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get_ex_new_index.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get_nonce_fn.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_instantiate.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_new.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_reseed.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_secure_new.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set_callbacks.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set_defaults.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set_ex_data.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set_reseed_defaults.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set_reseed_interval.3.gz Only in /usr/share/openssl/man/man3: = RAND_DRBG_set_reseed_time_interval.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_uninstantiate.3.gz Only in /usr/share/openssl/man/man3: RSA_padding_add_SSLv23.3.gz Only in /usr/share/openssl/man/man3: RSA_padding_check_SSLv23.3.gz Only in /usr/share/openssl/man/man7: RAND_DRBG.7.gz Only in /usr/share/openssl/man/man7: scrypt.7.gz Only in /usr/tests/atf_python/sys/net: netlink.py Only in /usr/tests/cddl/usr.sbin/dtrace/amd64: kinst Only in /usr/tests/lib/libarchive: test_fuzz.cab.uu Only in /usr/tests/lib/libarchive: test_fuzz.lzh.uu Only in /usr/tests/lib/libarchive: test_fuzz_1.iso.Z.uu Only in /usr/tests/lib/libbe: mnt Only in /usr/tests/lib/libc/tls: libh_tls_dlopen_p.a Only in /usr/tests/lib/libc/tls: libh_tls_dynamic_p.a Only in /usr/tests/libexec/rtld-elf: libpythagoras_p.a Only in /usr/tests/sys/netpfil/pf: checksum Only in /usr/tests/sys/netpfil/pf: fragmentation Only in /usr/tests/sys/netpfil/pf: rdr Only in /usr/tests/sys/netpfil/pf: scrub Only in /usr/tests/usr.bin/gh-bc: functions.sh Only in /usr/tests/usr.bin/gh-bc/tests: afl.py Only in /usr/tests/usr.bin/gh-bc/tests: bc_outputs Only in /usr/tests/usr.bin/gh-bc/tests/dc/errors: 34.txt Only in /usr/tests/usr.bin/gh-bc/tests: dc_outputs Only in /usr/tests/usr.bin/gh-bc/tests: diff.sh Only in /usr/tests/usr.bin/gh-bc/tests: radamsa.sh Only in /usr/tests/usr.bin/gh-bc/tests: radamsa.txt Only in /usr/tests/usr.bin/gh-bc/tests: randmath.py Only in /usr/tests/usr.bin: timeout Only in /usr/tests/usr.sbin/mixer: Kyuafile Only in /usr/tests/usr.sbin/mixer: mixer_test =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Fri Jul 28 17:51:44 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 4RCFZX60xBz4pwFx for ; Fri, 28 Jul 2023 17:52:04 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic311-24.consmr.mail.gq1.yahoo.com (sonic311-24.consmr.mail.gq1.yahoo.com [98.137.65.205]) (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 4RCFZW4Ns3z4Fsx for ; Fri, 28 Jul 2023 17:52:03 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=fvWLz41Z; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.65.205 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=1690566720; bh=NQKuCerad05FQAQCK2cZpxNLfvnrhvjh2/DU3+bSwbI=; h=From:Subject:Date:To:References:From:Subject:Reply-To; b=fvWLz41ZYSR5w39Hnvjkx1WHh7ohlw51NopwjO3TO3hc8eYGsU2NKPnr6isZOAjiJEcqJTmaroC/9TemKvLybE8l5oQPxUDWFDPuG4HI+SdaABBmpLBOZPbVR1UJzLlPOlkb2ozR8Ul4rSZs4bDPEzjhsXnq7PwJy+0NKCEId4h4m+UgfcIB41Qm1waMvwf76P6gBsdlMm9w2pkiGz93hZy4IDiyYGtk6xG8R0HHWW8m/TIQLT3NsXsVYMjX1bfMNLcYc213SSbYe+x4UuwC1kO3/jdX1dxMtvQYoT+Hl7JZwxCx/jFMsXqGNEbc/Gqq5l9egTJCj/sJFEuyi/S7Sg== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1690566720; bh=zYu8AgBbrwnfHAyMuQIf+fIM9fOpya/1k5O5znijRdf=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=Oqq+Ru8cHz2aEjo8MnQUkOdIaZFhEQtcvFesmkiFiu4NcBZ0syNP6p19fuBZdjFCJft4emhP3nKe7TQIeOiAzBbGTUyfxyRU11wTLepciMp3XpG8dwcO9Is9XfgSTTuNnYFkA3kENxOW9LhW0Zb5mZWmSq9vsMiXCqibbcD3hxvam/PexZSZsX8+isbpZO7R2Amhd2/VV9GjNFBQY5EUXIWC5mRrNriHPNT/lfYY0PMcW4mu4/SkeALnxylfSkcvgpMkfyN0Efq3DmLuFiDSVyZWpKB64P5hLIQa+WVTRtGpDXWwO1aRCx/J33loukwCGJfeFFZeZE657ZkGWmfF7A== X-YMail-OSG: MYwTIZsVM1lvYWGf4Zq7W7aylh3G3Hmya0yk_pofzOVHbPxJSDIb3YickauK7Ng IJT1vsLRGL2z1NjWFv6xISoxyKRJ.kOlgbnJJsra4HCSVYrooGcDI6NPisB0eXlyspNEdcum7yeS C5gQCJP2mLgaGQOx.dm6sVadRk3iTKpIGjVx3MtW_jEpDmJ_furFq5SXqzyNdNTji03YjD7nYOD9 CAnfBQaKHJZbKyhS4ug61KPAzzbx4TReblP7_1mdkEwt.pk_pVxHzL9gCXLExog8HQjDc48P.JDw 3MCDgNtI6gLciqvF_UTYNIxQSNx6lzcY012yYSgqHFyzCBKWKN4E73j.Idxv_R6xLj1eVfrx2ytb Rl9gjP06n1xpRMcLYLuRs5yu.ntpswXHlF4EG9RVeuwz1hwug8dNsYyn9WJtLnyJNkiPBSgQraOm lxx13kUuhYyf09GeVWYAWrknSikCgnjotEQJKxf2um9yHwejr0eI.anoWLD0M2TZZF0kcAPeTKb1 dHnu84J7uLYcYGrde8Z5LWx6KRr5qzxi.vAqNxq5sSlQM5WKUGXMCG4hAXYHf7RkDhEZWA59ZhoD jtkZkwD4_NNMDP69OXRCSTJJb1ona.FOcomSiyfsPB36mp2LUxvMCvAX09op.mmHRp3xK6mcyIXB bAQ5Ke.y9I2JyeXoyVt4t0JSKfz5jsU9DA5M8FOFID91oa2VHHA.oIF2RId_MkBKI4NuhUZwrfCR SzaFGrHFh0bZ6spSrUaCSWHUwxSrV6H16gaNi3oUv2hnIOfjlLJiw8AOY2Q2k84GUttlKLsp3KE8 A5O9aNZc8_6A2_DHtO968BF0nl94RQay21caY0.DdlRVt2ZxJc28w3Vxveh1O6OnhJl2cYluNS7H q7vlISmuY8DmhWN322H4ER6h3HrC38Ege.CQwh_RCgOuoBNxuyx2I9G7pk9J.sGYwQfxH2gFyFP9 uM8wdnUOZ3XhRwvHqk8y7q5LWqQmt8c07x7.QG7OWXUQE50rwfTiwR7mvpG8ILm9FWlTD7pT5Tbu .N5a7hubC5CTDWYpdtPYL9vygrNbpSgYecmCjFSU8p_q8r30ifPsaJ65QQjnumQEeyZ3V6UzTqgO ywm1D6inxNIsAYBwKMm6kHKgWxsng6AAHr9rHxhHC8qpny0HcX2ZoTwNA4BXBs_bErdfyktrWhUk UeIEp4Hgw40gW2p0W5UtmbGdwo52RwbEBTVW.eSv5Vq15ad1VLVESZcMB8NLWIDnsEZQy.6hv2XV ZLMxnT6gC7bs.ptCy2s1JBc57Sw1bEyFGYQmMch.EprWwDkTN.L4Ia35yRMPtXKWqiHzyaHIdaX9 cc_VVSSyLHTZBDpzveh52grxEx35CrnaP4GvEGSAG2r8sdOFD9dUbWazOH4d8TK5_CGRhhW6j7id WVbDjLiDmdpavSYYIqh1P9sb93sYS3_XBtlTvHFruKasaBSijgb4g2iBmsKrTmwwFspmCC5XFMAh bK0SYQ9g4aC5KAMd3L25hu8nJ2_TYhaadqgTMggr9RaYc3jT7R7iK6DcbTzMPcGk6YzvhVHtml8R ibNkrOyuQIMNrnevSIGpsJsTLDzqNzM77SYr7wMHCFxBumBzLPNl1FbrVeafE6SxuFibaarDjq5b ckfB7qufz2aywgMGsATEwoIZ8JByPBzSejcc6ClhuSsQ.OJyDdzML0Wp_EgpXwjTUi6y9rtirbD1 nCVPxK1agWf6WW1BwO.foQ24Bck6h4t2lh7MahrP1zN.g0mkMgFyTL5awMd5Euh.WzjNIYAmlBsB Qry8R5zvxMu8BEtB05cKGGPK2e4.o6IviUpdtjmHdLStXVrmdT1baitjw1dO1PqG3ndt76PViolZ 4pU2uVy9lLoxi25qSsVfbU1IFUBDAlkF7MPLhhPcs1XjNKC1kXc_xNjzVTDf9nNDfcFtL.EQkJcY XuazJczkxkWPyrbLxYvPoMZl0k7xEl.cheVHOOxx4m10_zSgwiqjEqrM3imrsfZY9gbbx6v7n0tq vJgJPrENi4gJdXRMBmexwuDL9Xqz48crp_w8rhniMWVBkMgRtnsPyqaZG7Us9iyNLhPZo1Qg9ly8 uUt1Ew8l0rHHV6NvytIe.QbaxbsiA7U6n40SBpekujXYEU0H5upClGQmOsiqbqNLDRjMiE5Jp1oW INkqbNEVRsuPJ8nwqtbeGT4JVjZUB0xnSQTBvnz0zADmitn4w6Wm0lG5OxbKl5jgYWwKuri65gBQ 1_dcv1pxHWZ38AKqlmEfQs95VKHTpMIjxO3rGU.bIECyJ2l88TIJgZcRexr2LUg-- X-Sonic-MF: X-Sonic-ID: 52822e1b-7424-4f4a-af34-45a8a4e45389 Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.gq1.yahoo.com with HTTP; Fri, 28 Jul 2023 17:52:00 +0000 Received: by hermes--production-ne1-549c7f6c44-9w7gj (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID fb3440c6c57c09745f05f7171ecc14ef; Fri, 28 Jul 2023 17:51:55 +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 \(3731.700.6\)) Subject: delete-old status under /usr/ (aarch64 context example this time) Message-Id: <42C003AA-2B46-470B-8DE4-7A556FD9E8D8@yahoo.com> Date: Fri, 28 Jul 2023 10:51:44 -0700 To: Current FreeBSD X-Mailer: Apple Mail (2.3731.700.6) References: <42C003AA-2B46-470B-8DE4-7A556FD9E8D8.ref@yahoo.com> X-Spamd-Result: default: False [-3.44 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-0.996]; NEURAL_HAM_MEDIUM(-0.99)[-0.992]; NEURAL_HAM_LONG(-0.95)[-0.949]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; MV_CASE(0.50)[]; 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_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.65.205:from]; BLOCKLISTDE_FAIL(0.00)[98.137.65.205:server fail]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[yahoo.com]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.65.205:from] X-Rspamd-Queue-Id: 4RCFZW4Ns3z4Fsx X-Spamd-Bar: --- This is similar to my earlier amd64 report but shows in files associated with the recent old-arm cleanout and lib32 addition as well, for example. Again a comparison to a from-scratch install into an empty directry via: installworld distrib-dirs distribution DB_FROM_SRC=3D1 installkernel # uname -apKU FreeBSD CA72-16Gp-ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT aarch64 1400093 = #102 main-n264334-215bab7924f6-dirty: Wed Jul 26 02:02:48 PDT 2023 = root@CA72-16Gp-ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm6= 4.aarch64/sys/GENERIC-NODBG-CA72 arm64 aarch64 1400093 1400093 I use delete-old and delete-old-libs with -DBATCH_DELETE_OLD_FILES in my update procedures and have for years. delete-old use is a step in scripts, not a manual operation. (delete-old-libs use requires more timing control and so is less automatic.) I find the following when I look for potential old files in /usr/ = compared to what ended up in /tmp/main-amd64-installed-from-scratch/usr/ . Much = of the output seems to be old files that are still around but likely should not be. # diff -rq /tmp/main-CA72-installed-from-scratch/usr /usr | grep "Only = in /usr/" | grep -v -E "(/usr/local:|/usr/obj:|/usr/lib/debug/boot: = kernel\.)" diff: = /tmp/main-CA72-installed-from-scratch/usr/share/locale/nn_NO.ISO8859-1/LC_= MESSAGES: Too many levels of symbolic links diff: = /tmp/main-CA72-installed-from-scratch/usr/share/locale/nn_NO.ISO8859-15/LC= _MESSAGES: Too many levels of symbolic links diff: = /tmp/main-CA72-installed-from-scratch/usr/share/locale/sl_SI.ISO8859-2/LC_= MESSAGES: No such file or directory Only in /usr/include/dev/hwpmc: hwpmc_beri.h Only in /usr/include/dev/wg: compat.h Only in /usr/include/dev/wg: crypto.h Only in /usr/include/dev/wg: version.h Only in /usr/include/dev/wg: wg_cookie.h Only in /usr/include/dev/wg: wg_noise.h Only in /usr/include/machine: asmacros.h Only in /usr/include/machine: atags.h Only in /usr/include/machine: atomic-v6.h Only in /usr/include/machine: blockio.h Only in /usr/include/machine: cpu-v6.h Only in /usr/include/machine: fdt.h Only in /usr/include/machine: fiq.h Only in /usr/include/machine: ieee.h Only in /usr/include/machine: limits.h Only in /usr/include/machine: pl310.h Only in /usr/include/machine: platform.h Only in /usr/include/machine: platformvar.h Only in /usr/include/machine: pmap-v6.h Only in /usr/include/machine: pmap_var.h Only in /usr/include/machine: pte-v6.h Only in /usr/include/machine: sc_machdep.h Only in /usr/include/machine: swi.h Only in /usr/include/machine: utrap.h Only in /usr/include/sys: _cscan_atomic.h Only in /usr/include/sys: _cscan_bus.h Only in /usr/lib/debug/sbin: bsdlabel.debug Only in /usr/lib/debug/sbin: fdisk.debug Only in /usr/lib/debug/usr/bin: timeout.debug Only in /usr/lib/debug/usr/tests/cddl/usr.sbin/dtrace/amd64: kinst Only in /usr/lib/debug/usr/tests/lib/libc/sys: brk_test.debug Only in /usr/lib/debug/usr/tests/lib/libthr: swapcontext_test.debug Only in /usr/lib/debug/usr/tests/usr.bin: timeout Only in /usr/lib/include/dev/hwpmc: hwpmc_beri.h Only in /usr/lib/include/dev/wg: compat.h Only in /usr/lib/include/dev/wg: crypto.h Only in /usr/lib/include/dev/wg: version.h Only in /usr/lib/include/dev/wg: wg_cookie.h Only in /usr/lib/include/dev/wg: wg_noise.h Only in /usr/lib/include/machine: asmacros.h Only in /usr/lib/include/machine: atags.h Only in /usr/lib/include/machine: atomic-v6.h Only in /usr/lib/include/machine: blockio.h Only in /usr/lib/include/machine: cpu-v6.h Only in /usr/lib/include/machine: fdt.h Only in /usr/lib/include/machine: fiq.h Only in /usr/lib/include/machine: ieee.h Only in /usr/lib/include/machine: limits.h Only in /usr/lib/include/machine: pl310.h Only in /usr/lib/include/machine: platform.h Only in /usr/lib/include/machine: platformvar.h Only in /usr/lib/include/machine: pmap-v6.h Only in /usr/lib/include/machine: pmap_var.h Only in /usr/lib/include/machine: pte-v6.h Only in /usr/lib/include/machine: sc_machdep.h Only in /usr/lib/include/machine: swi.h Only in /usr/lib/include/machine: utrap.h Only in /usr/lib/include/sys: _cscan_atomic.h Only in /usr/lib/include/sys: _cscan_bus.h Only in /usr/share/certs/trusted: = Camerfirma_Chambers_of_Commerce_Root.pem Only in /usr/share/certs/trusted: Camerfirma_Global_Chambersign_Root.pem Only in /usr/share/certs/trusted: Certum_Root_CA.pem Only in /usr/share/certs/trusted: Chambers_of_Commerce_Root_-_2008.pem Only in /usr/share/certs/trusted: D-TRUST_Root_CA_3_2013.pem Only in /usr/share/certs/trusted: EC-ACC.pem Only in /usr/share/certs/trusted: = GeoTrust_Primary_Certification_Authority_-_G2.pem Only in /usr/share/certs/trusted: Global_Chambersign_Root_-_2008.pem Only in /usr/share/certs/trusted: OISTE_WISeKey_Global_Root_GA_CA.pem Only in /usr/share/certs/trusted: QuoVadis_Root_CA.pem Only in /usr/share/certs/trusted: Sonera_Class_2_Root_CA.pem Only in /usr/share/certs/trusted: Staat_der_Nederlanden_Root_CA_-_G3.pem Only in /usr/share/certs/trusted: SwissSign_Platinum_CA_-_G2.pem diff: /tmp/main-CA72-installed-from-scratch/usr/tests/local: No such = file or directory diff: = /tmp/main-CA72-installed-from-scratch/usr/tests/sys/pjdfstest/tests/tests/= tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/te= sts/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/test= s/tests/tests/tests/tests/tests/tests: Too many levels of symbolic links Only in /usr/share/certs/trusted: = Symantec_Class_1_Public_Primary_Certification_Authority_-_G6.pem Only in /usr/share/certs/trusted: = Symantec_Class_2_Public_Primary_Certification_Authority_-_G6.pem Only in /usr/share/certs/trusted: Trustis_FPS_Root_CA.pem Only in /usr/share/certs/trusted: = VeriSign_Universal_Root_Certification_Authority.pem Only in /usr/share/certs/trusted: = Verisign_Class_1_Public_Primary_Certification_Authority_-_G3.pem Only in /usr/share/certs/trusted: = Verisign_Class_2_Public_Primary_Certification_Authority_-_G3.pem Only in /usr/share/doc/legal: sdma-imx6q.LICENSE Only in /usr/share/locale/hr_HR.ISO8859-2: LC_MESSAGES Only in /usr/share/locale/nl_BE.ISO8859-1: LC_MESSAGES Only in /usr/share/locale/nl_BE.ISO8859-15: LC_MESSAGES Only in /usr/share/locale/sr_RS.ISO8859-2: LC_MESSAGES Only in /usr/share/locale/zh_TW.Big5: LC_NUMERIC Only in /usr/share/man/man2: arm_drain_writebuf.2.gz Only in /usr/share/man/man2: arm_sync_icache.2.gz Only in /usr/share/man/man4/aarch64: aw_gpio.4.gz Only in /usr/share/man/man4/aarch64: aw_mmc.4.gz Only in /usr/share/man/man4/aarch64: aw_rtc.4.gz Only in /usr/share/man/man4/aarch64: aw_sid.4.gz Only in /usr/share/man/man4/aarch64: aw_spi.4.gz Only in /usr/share/man/man4/aarch64: aw_syscon.4.gz Only in /usr/share/man/man4/aarch64: bcm283x_pwm.4.gz Only in /usr/share/man/man4: ce.4.gz Only in /usr/share/man/man4: cp.4.gz Only in /usr/share/man/man4/i386: ce.4.gz Only in /usr/share/man/man4/i386: cp.4.gz Only in /usr/share/man/man4: if_an.4.gz Only in /usr/share/man/man5: portsnap.conf.5.gz Only in /usr/share/man/man8: bsdlabel.8.gz Only in /usr/share/man/man8: fdisk.8.gz Only in /usr/share/man/man9: DOMAIN_SET.9.gz Only in /usr/share/man/man9: vm_page_sbusy.9.gz Only in /usr/share/man/man9: vm_page_sleep_if_busy.9.gz Only in /usr/share/man/man9: vm_page_xbusy.9.gz Only in /usr/share/openssl/man/man1: asn1parse.1.gz Only in /usr/share/openssl/man/man1: ca.1.gz Only in /usr/share/openssl/man/man1: ciphers.1.gz Only in /usr/share/openssl/man/man1: cms.1.gz Only in /usr/share/openssl/man/man1: crl.1.gz Only in /usr/share/openssl/man/man1: crl2pkcs7.1.gz Only in /usr/share/openssl/man/man1: dgst.1.gz Only in /usr/share/openssl/man/man1: dhparam.1.gz Only in /usr/share/openssl/man/man1: dsa.1.gz Only in /usr/share/openssl/man/man1: dsaparam.1.gz Only in /usr/share/openssl/man/man1: ec.1.gz Only in /usr/share/openssl/man/man1: ecparam.1.gz Only in /usr/share/openssl/man/man1: enc.1.gz Only in /usr/share/openssl/man/man1: engine.1.gz Only in /usr/share/openssl/man/man1: errstr.1.gz Only in /usr/share/openssl/man/man1: gendsa.1.gz Only in /usr/share/openssl/man/man1: genpkey.1.gz Only in /usr/share/openssl/man/man1: genrsa.1.gz Only in /usr/share/openssl/man/man1: list.1.gz Only in /usr/share/openssl/man/man1: nseq.1.gz Only in /usr/share/openssl/man/man1: ocsp.1.gz Only in /usr/share/openssl/man/man1: openssl-tsget.1.gz Only in /usr/share/openssl/man/man1: passwd.1.gz Only in /usr/share/openssl/man/man1: pkcs12.1.gz Only in /usr/share/openssl/man/man1: pkcs7.1.gz Only in /usr/share/openssl/man/man1: pkcs8.1.gz Only in /usr/share/openssl/man/man1: pkey.1.gz Only in /usr/share/openssl/man/man1: pkeyparam.1.gz Only in /usr/share/openssl/man/man1: pkeyutl.1.gz Only in /usr/share/openssl/man/man1: prime.1.gz Only in /usr/share/openssl/man/man1: rand.1.gz Only in /usr/share/openssl/man/man1: req.1.gz Only in /usr/share/openssl/man/man1: rsa.1.gz Only in /usr/share/openssl/man/man1: rsautl.1.gz Only in /usr/share/openssl/man/man1: s_client.1.gz Only in /usr/share/openssl/man/man1: s_server.1.gz Only in /usr/share/openssl/man/man1: s_time.1.gz Only in /usr/share/openssl/man/man1: sess_id.1.gz Only in /usr/share/openssl/man/man1: smime.1.gz Only in /usr/share/openssl/man/man1: speed.1.gz Only in /usr/share/openssl/man/man1: spkac.1.gz Only in /usr/share/openssl/man/man1: srp.1.gz Only in /usr/share/openssl/man/man1: storeutl.1.gz Only in /usr/share/openssl/man/man1: ts.1.gz Only in /usr/share/openssl/man/man1: verify.1.gz Only in /usr/share/openssl/man/man1: version.1.gz Only in /usr/share/openssl/man/man1: x509.1.gz Only in /usr/share/openssl/man/man3: ECDH_get_ex_data.3.gz Only in /usr/share/openssl/man/man3: ECDH_get_ex_new_index.3.gz Only in /usr/share/openssl/man/man3: ECDH_set_ex_data.3.gz Only in /usr/share/openssl/man/man3: ERR_GET_FUNC.3.gz Only in /usr/share/openssl/man/man3: EVP_PKEY_CTX_hkdf_mode.3.gz Only in /usr/share/openssl/man/man3: EVP_PKEY_set_alias_type.3.gz Only in /usr/share/openssl/man/man3: EVP_aes.3.gz Only in /usr/share/openssl/man/man3: EVP_aria.3.gz Only in /usr/share/openssl/man/man3: EVP_camellia.3.gz Only in /usr/share/openssl/man/man3: EVP_des.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_bytes.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_cleanup_entropy_fn.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_cleanup_nonce_fn.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_free.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_generate.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get0_master.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get0_private.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get0_public.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get_entropy_fn.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get_ex_data.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get_ex_new_index.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get_nonce_fn.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_instantiate.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_new.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_reseed.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_secure_new.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set_callbacks.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set_defaults.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set_ex_data.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set_reseed_defaults.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set_reseed_interval.3.gz Only in /usr/share/openssl/man/man3: = RAND_DRBG_set_reseed_time_interval.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_uninstantiate.3.gz Only in /usr/share/openssl/man/man3: RSA_padding_add_SSLv23.3.gz Only in /usr/share/openssl/man/man3: RSA_padding_check_SSLv23.3.gz Only in /usr/share/openssl/man/man7: RAND_DRBG.7.gz Only in /usr/share/openssl/man/man7: scrypt.7.gz Only in /usr/tests/atf_python/sys/net: netlink.py Only in /usr/tests/cddl/usr.sbin/dtrace/amd64: kinst Only in /usr/tests/lib/libarchive: test_fuzz.cab.uu Only in /usr/tests/lib/libarchive: test_fuzz.lzh.uu Only in /usr/tests/lib/libarchive: test_fuzz_1.iso.Z.uu Only in /usr/tests/lib/libbe: mnt Only in /usr/tests/lib/libc/sys: brk_test Only in /usr/tests/lib/libc/tls: libh_tls_dlopen_p.a Only in /usr/tests/lib/libc/tls: libh_tls_dynamic_p.a Only in /usr/tests/lib/libthr: swapcontext_test Only in /usr/tests/libexec/rtld-elf: libpythagoras_p.a Only in /usr/tests/sys/netpfil/pf: checksum Only in /usr/tests/sys/netpfil/pf: fragmentation Only in /usr/tests/sys/netpfil/pf: rdr Only in /usr/tests/sys/netpfil/pf: scrub Only in /usr/tests/usr.bin/gh-bc: .log_bc.txt Only in /usr/tests/usr.bin/gh-bc: .log_bc_test.txt Only in /usr/tests/usr.bin/gh-bc: .log_dc.txt Only in /usr/tests/usr.bin/gh-bc: .log_dc_test.txt Only in /usr/tests/usr.bin/gh-bc: functions.sh Only in /usr/tests/usr.bin/gh-bc/tests: afl.py Only in /usr/tests/usr.bin/gh-bc/tests: bc_outputs Only in /usr/tests/usr.bin/gh-bc/tests/dc/errors: 34.txt Only in /usr/tests/usr.bin/gh-bc/tests: dc_outputs Only in /usr/tests/usr.bin/gh-bc/tests: diff.sh Only in /usr/tests/usr.bin/gh-bc/tests: radamsa.sh Only in /usr/tests/usr.bin/gh-bc/tests: radamsa.txt Only in /usr/tests/usr.bin/gh-bc/tests: randmath.py Only in /usr/tests/usr.bin: timeout Only in /usr/tests/usr.sbin/mixer: Kyuafile Only in /usr/tests/usr.sbin/mixer: mixer_test =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Fri Jul 28 18:12:01 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 4RCG1t3pddz4p6m1 for ; Fri, 28 Jul 2023 18:12:18 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic305-20.consmr.mail.gq1.yahoo.com (sonic305-20.consmr.mail.gq1.yahoo.com [98.137.64.83]) (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 4RCG1s2cm2z4LXp for ; Fri, 28 Jul 2023 18:12:17 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=Lks+rm+5; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.64.83 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=1690567935; bh=xkJR1on2DEX9XYZtP9Er9I7thOEUdw6KmTThQIZIOog=; h=From:Subject:Date:References:To:In-Reply-To:From:Subject:Reply-To; b=Lks+rm+5J16T/TUO4dK9wZFs4gqbKO7gOvN8P/7nCo4451ABEM3T7A/7zoi55Jrm6pVk8RsGjRuKdtEWiKwpx6a8qsSCr4guwbay9GY6Iv7KTkDnV/WYK7o+mR9NyyD9iBVJMcDnFHT7QjbObvn6MzJBLpWzs0uAf+1LaRXnikgtpC6LZU9JgYA+kifN+dgXVcHA6th1VTmRAYlLFb82vdRMvldipzabPIA+CH8sfB/2q4yazYTR3RjXLQEu4ur2m8vD7ZC/sy66h1osZkQAh8a40BbN0Suq80LVFrxvOVR/X0PeclRPBANiIHff1T2V2KNrrDX21uj2sizphwHtFw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1690567935; bh=ux4Bnnjs1H8U6W1nn+wU5wUNtxZ15BLM3Z5lhvyqCqh=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=gMyTZIx/L1iOc+9gV67ztXNxznHdND9uae++EReSFU89zq99DqWrC0uNZwaWNxfwTeJrjJW0RapryH/E+gyd+hApf9vemXGXsMw/LHJyq+HP/y9mRj7org2X5M7LdAi60yPXKXi2HSnic4f/jqaA8uEzM43Mka/vOwBa1uV+Gyln15RGNJzRPhZLQkcNYJQoX5uVTTbaVI2wR2p36r0FXEmcaZhoUgo2avhFAuCqHQ+iHFC5s/Zkqk9i8dFRFAYtMNfMPxWbPR/WqijiCu80fWTBh6i/4H1p2Ecososaup1jCdkM9giyjAl8jlTdujQiFG/Q8EUVQ5iIDWJWt29+fw== X-YMail-OSG: smdRtN0VM1kEd4dgHVisGQvNQwZ05jQJX3LUinc_antZ7Tp740Q.gY6HHAHb_sC izD6dWpoWfflKKBwyAnl7JMVZ9fE8YofU5pWlKG74HYmy1gvAXuY_4bgoAHjm8rRTaVBCc5ZmynQ ZzKjv3XB7G76wR45GNtMnUAGqegk566mnS1awQYSdS6sbfZe6ddZLKdY79lZb4KghDDnhp99iR20 7U7QA4lcK_IAxUKvz06.DbmwpwQQ2nuUaYAZjga.821zOeJRl4S2Xpz6.c42sZWkDfI6VWdOMTcz InGdJHJ5btDAFo1hUgGsArvDqYvVSajJ1R4QVR_nSRaVzB6ImYowwnWS_LyQAzVKqQOdM2RtgLsc 7JOSmUNc9xWzZRNkt7zt7.iQiTL7DvbCxaYXUAcEWFAyFIg_jcRLmvhY0ZHsW052ZZO8ioI1hvFr DIoXfJhAXz6CtE7uHvwpKmDPsWbMMWrn2pSi9C_3nxlCl2pHgFwqFRdYPn9XQarDWztP.3sD7fHq .tkiNJsoaVaKqQiN8VG7DyDvHtzlkWOD9yYh3uWk4qhq2E6sDv5ApAnY9uiRFBoASLlFEJ2V4JS0 wwXVEjNPkKXCLt9YscEL_WsTeFDfAA8btS.B3alAo20ewUDxjEe_wiEsnGqNVqSPDkyd_oCKvn0U QqTv240mbiBJKy7x5zS7LUc0kt0BiI1BgbjVzqEEcYG5iyAShKpbR2o8ZaWc7ghiZH2S3mm9C6.9 OGQPwdNzTfpPukIyz7CNaqD7VUekVkHhWEf3xedxB4cU7Tf2q6fyzZGX5cVhQvvTVIpnCgJBCSs_ EOW1YTJ4vdk2zYnO9qECwbKDPs84mCapeIKhcw1fZv9__j.9iAT0SO5uMhp1oiTAIdvZKiPMVEX5 KZBxRSPHwR2pSOc_hcS9S6aPUT5hAsJVeir1hOWfx_yQZ7eR9_IaWmWOCb7ctRbggoInSVPKCvCL mMkaVJVcHMWfcmO_em8E6KTvtr.Yh6Xh3HxsOdcfIdRr0OP0NYTTX7n9eBJfeE9ZaAFzim3F3zlT 1w_UHE2U8SnGn3c3_xl_N40I6MHmgKrLdfKrUcSTxGCRKfmMc3JWvy2cK4DRzC6vPrcjag1Y.3Za wlFCUiPohjrnhmjYSfmVqHJmudaY6ptyfKFvc1ntHhKhpQmvMKfKv80YxJ.WPVdbFJCXnF2V24ab 8Jh3X8N9NfscC3cOVuyd1HzyQ_6rGVXhZ_ViNLs.wy2YDWYvUiySiONgvxcamKJYoyxvFw9_O7R0 aRgsVRvzqjvCLOfs6aE.tjruz8DwDxhD3WCTqjj5lHcJ8YUmU9vXhVBb.TODwm8uATSnozLjIbg. Hb8KaKr2fht9PqQ6MAZicTcm4.ct3bqxzpRs_SIyGCtrgZ016.BKOMPBEmFdeZ.vYN0G6dC2RBLl cbyNnopYjBRclb0kbKOahxH7YwovYWchk0XWy7wZWX2dmh7VRzksrppEfJR3GkmA4TEXqT6m3BTZ _eYMgDHNBwb6KHSS77Z0V326MbM84ghXgngZ3b94SPuMBAx9iXnqKJ8h5CURurttwxCowuRMHqR0 Y4BzJa5AQIOrRplBKNwOhn2oW1ydoJtp4BZtW1ztBOG2osOkZ0drZ4qXKJ3ec2vYp1pMIt45i5Wn l4rox.lbNBdpU.9frBRhbbUyN3kXF0U.FxluILZG75IXu4Wm4bRUSUsOiUg9kE0jQstHbQThYYsJ ZBCXl2X5gimXRb_6RnXZ9zlmaNNtsmYE4f1tYSoOf9M3cnGbrFDrYTUBpR7TMREikZN9e78LmyRZ WaPPGKKrBHQF.Ue6IONKoAI7_.5vjn.P1DHgjElmzo9QNkcTXlO2AAhKEXPQUlYsBPl0RcBhduwN _GVEEpbdNEg0zAVLq0oaGOd7WrdGh5Di2iGcm3WmoaYqVh_qbcTalke9M5fsd9jEsQjkICat_8dF ndqH_UIv.PrPzYysEqlQnGIJWC8lwEMwnBDpZApp4oLFIdcVTeQQOrNLvgxE1wfynqdDgX6EhkvC ytNENNGFmFYXnxF2lc0oaOvaBhgg0ElK3_tqI4zGYnPfLzGMRUNiDZ4O3A8VllnbuhTYSvc7lJPP 10Joac4VS95jQ6bepjqACv6BXv2lPrDQBPR_rnKu4qlVoXXYCNM7tEqmlqMzD2xSQ3yLnUfs1LF6 FGWfPTo9GxOWtnQDvG_iTs1gTfTiQe30qqGbGR3WEtb16uxillYv67J.MDnAm3PIWNbCnieGzQy_ eIrQQCYEltBsGdaJMIDEX2rVrGpEIBj2PqlPJYvyCBiNwMYstn8AT8dQsp1zoJA-- X-Sonic-MF: X-Sonic-ID: 511eb088-6107-45a5-b52d-0da024f7bf6b Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.gq1.yahoo.com with HTTP; Fri, 28 Jul 2023 18:12:15 +0000 Received: by hermes--production-gq1-7d844d8954-tbq9x (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 5d2bd0589110a308d32196f4980e4b46; Fri, 28 Jul 2023 18:12:12 +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 \(3731.700.6\)) Subject: Re: delete-old status under /usr/ (aarch64 context example this time) Date: Fri, 28 Jul 2023 11:12:01 -0700 References: <42C003AA-2B46-470B-8DE4-7A556FD9E8D8@yahoo.com> To: Current FreeBSD In-Reply-To: <42C003AA-2B46-470B-8DE4-7A556FD9E8D8@yahoo.com> Message-Id: X-Mailer: Apple Mail (2.3731.700.6) X-Spamd-Result: default: False [-3.41 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-0.996]; NEURAL_HAM_MEDIUM(-0.99)[-0.988]; NEURAL_HAM_LONG(-0.93)[-0.930]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.64.83:from]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[yahoo.com]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.64.83:from] X-Rspamd-Queue-Id: 4RCG1s2cm2z4LXp X-Spamd-Bar: --- On Jul 28, 2023, at 10:51, Mark Millard wrote: > This is similar to my earlier amd64 report but shows in files > associated with the recent old-arm cleanout and lib32 addition > as well, for example. Again a comparison to a from-scratch > install into an empty directry via: >=20 > installworld distrib-dirs distribution DB_FROM_SRC=3D1 installkernel >=20 > # uname -apKU > FreeBSD CA72-16Gp-ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT aarch64 = 1400093 #102 main-n264334-215bab7924f6-dirty: Wed Jul 26 02:02:48 PDT = 2023 = root@CA72-16Gp-ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm6= 4.aarch64/sys/GENERIC-NODBG-CA72 arm64 aarch64 1400093 1400093 >=20 > I use delete-old and delete-old-libs with -DBATCH_DELETE_OLD_FILES > in my update procedures and have for years. delete-old use is a > step in scripts, not a manual operation. (delete-old-libs use > requires more timing control and so is less automatic.) >=20 > I find the following when I look for potential old files in /usr/ = compared > to what ended up in /tmp/main-amd64-installed-from-scratch/usr/ . Much = of > the output seems to be old files that are still around but likely = should > not be. >=20 > # diff -rq /tmp/main-CA72-installed-from-scratch/usr /usr | grep "Only = in /usr/" | grep -v -E "(/usr/local:|/usr/obj:|/usr/lib/debug/boot: = kernel\.)" > diff: = /tmp/main-CA72-installed-from-scratch/usr/share/locale/nn_NO.ISO8859-1/LC_= MESSAGES: Too many levels of symbolic links > diff: = /tmp/main-CA72-installed-from-scratch/usr/share/locale/nn_NO.ISO8859-15/LC= _MESSAGES: Too many levels of symbolic links > diff: = /tmp/main-CA72-installed-from-scratch/usr/share/locale/sl_SI.ISO8859-2/LC_= MESSAGES: No such file or directory > Only in /usr/include/dev/hwpmc: hwpmc_beri.h > Only in /usr/include/dev/wg: compat.h > Only in /usr/include/dev/wg: crypto.h > Only in /usr/include/dev/wg: version.h > Only in /usr/include/dev/wg: wg_cookie.h > Only in /usr/include/dev/wg: wg_noise.h > Only in /usr/include/machine: asmacros.h > Only in /usr/include/machine: atags.h > Only in /usr/include/machine: atomic-v6.h > Only in /usr/include/machine: blockio.h > Only in /usr/include/machine: cpu-v6.h > Only in /usr/include/machine: fdt.h > Only in /usr/include/machine: fiq.h > Only in /usr/include/machine: ieee.h > Only in /usr/include/machine: limits.h > Only in /usr/include/machine: pl310.h > Only in /usr/include/machine: platform.h > Only in /usr/include/machine: platformvar.h > Only in /usr/include/machine: pmap-v6.h > Only in /usr/include/machine: pmap_var.h > Only in /usr/include/machine: pte-v6.h > Only in /usr/include/machine: sc_machdep.h > Only in /usr/include/machine: swi.h > Only in /usr/include/machine: utrap.h > Only in /usr/include/sys: _cscan_atomic.h > Only in /usr/include/sys: _cscan_bus.h > Only in /usr/lib/debug/sbin: bsdlabel.debug > Only in /usr/lib/debug/sbin: fdisk.debug > Only in /usr/lib/debug/usr/bin: timeout.debug > Only in /usr/lib/debug/usr/tests/cddl/usr.sbin/dtrace/amd64: kinst > Only in /usr/lib/debug/usr/tests/lib/libc/sys: brk_test.debug > Only in /usr/lib/debug/usr/tests/lib/libthr: swapcontext_test.debug > Only in /usr/lib/debug/usr/tests/usr.bin: timeout > Only in /usr/lib/include/dev/hwpmc: hwpmc_beri.h > Only in /usr/lib/include/dev/wg: compat.h > Only in /usr/lib/include/dev/wg: crypto.h > Only in /usr/lib/include/dev/wg: version.h > Only in /usr/lib/include/dev/wg: wg_cookie.h > Only in /usr/lib/include/dev/wg: wg_noise.h > Only in /usr/lib/include/machine: asmacros.h > Only in /usr/lib/include/machine: atags.h > Only in /usr/lib/include/machine: atomic-v6.h > Only in /usr/lib/include/machine: blockio.h > Only in /usr/lib/include/machine: cpu-v6.h > Only in /usr/lib/include/machine: fdt.h > Only in /usr/lib/include/machine: fiq.h > Only in /usr/lib/include/machine: ieee.h > Only in /usr/lib/include/machine: limits.h > Only in /usr/lib/include/machine: pl310.h > Only in /usr/lib/include/machine: platform.h > Only in /usr/lib/include/machine: platformvar.h > Only in /usr/lib/include/machine: pmap-v6.h > Only in /usr/lib/include/machine: pmap_var.h > Only in /usr/lib/include/machine: pte-v6.h > Only in /usr/lib/include/machine: sc_machdep.h > Only in /usr/lib/include/machine: swi.h > Only in /usr/lib/include/machine: utrap.h > Only in /usr/lib/include/sys: _cscan_atomic.h > Only in /usr/lib/include/sys: _cscan_bus.h > Only in /usr/share/certs/trusted: = Camerfirma_Chambers_of_Commerce_Root.pem > Only in /usr/share/certs/trusted: = Camerfirma_Global_Chambersign_Root.pem > Only in /usr/share/certs/trusted: Certum_Root_CA.pem > Only in /usr/share/certs/trusted: Chambers_of_Commerce_Root_-_2008.pem > Only in /usr/share/certs/trusted: D-TRUST_Root_CA_3_2013.pem > Only in /usr/share/certs/trusted: EC-ACC.pem > Only in /usr/share/certs/trusted: = GeoTrust_Primary_Certification_Authority_-_G2.pem > Only in /usr/share/certs/trusted: Global_Chambersign_Root_-_2008.pem > Only in /usr/share/certs/trusted: OISTE_WISeKey_Global_Root_GA_CA.pem > Only in /usr/share/certs/trusted: QuoVadis_Root_CA.pem > Only in /usr/share/certs/trusted: Sonera_Class_2_Root_CA.pem > Only in /usr/share/certs/trusted: = Staat_der_Nederlanden_Root_CA_-_G3.pem > Only in /usr/share/certs/trusted: SwissSign_Platinum_CA_-_G2.pem > diff: /tmp/main-CA72-installed-from-scratch/usr/tests/local: No such = file or directory > diff: = /tmp/main-CA72-installed-from-scratch/usr/tests/sys/pjdfstest/tests/tests/= tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/te= sts/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/test= s/tests/tests/tests/tests/tests/tests: Too many levels of symbolic links > Only in /usr/share/certs/trusted: = Symantec_Class_1_Public_Primary_Certification_Authority_-_G6.pem > Only in /usr/share/certs/trusted: = Symantec_Class_2_Public_Primary_Certification_Authority_-_G6.pem > Only in /usr/share/certs/trusted: Trustis_FPS_Root_CA.pem > Only in /usr/share/certs/trusted: = VeriSign_Universal_Root_Certification_Authority.pem > Only in /usr/share/certs/trusted: = Verisign_Class_1_Public_Primary_Certification_Authority_-_G3.pem > Only in /usr/share/certs/trusted: = Verisign_Class_2_Public_Primary_Certification_Authority_-_G3.pem > Only in /usr/share/doc/legal: sdma-imx6q.LICENSE > Only in /usr/share/locale/hr_HR.ISO8859-2: LC_MESSAGES > Only in /usr/share/locale/nl_BE.ISO8859-1: LC_MESSAGES > Only in /usr/share/locale/nl_BE.ISO8859-15: LC_MESSAGES > Only in /usr/share/locale/sr_RS.ISO8859-2: LC_MESSAGES > Only in /usr/share/locale/zh_TW.Big5: LC_NUMERIC > Only in /usr/share/man/man2: arm_drain_writebuf.2.gz > Only in /usr/share/man/man2: arm_sync_icache.2.gz > Only in /usr/share/man/man4/aarch64: aw_gpio.4.gz > Only in /usr/share/man/man4/aarch64: aw_mmc.4.gz > Only in /usr/share/man/man4/aarch64: aw_rtc.4.gz > Only in /usr/share/man/man4/aarch64: aw_sid.4.gz > Only in /usr/share/man/man4/aarch64: aw_spi.4.gz > Only in /usr/share/man/man4/aarch64: aw_syscon.4.gz > Only in /usr/share/man/man4/aarch64: bcm283x_pwm.4.gz > Only in /usr/share/man/man4: ce.4.gz > Only in /usr/share/man/man4: cp.4.gz > Only in /usr/share/man/man4/i386: ce.4.gz > Only in /usr/share/man/man4/i386: cp.4.gz > Only in /usr/share/man/man4: if_an.4.gz > Only in /usr/share/man/man5: portsnap.conf.5.gz > Only in /usr/share/man/man8: bsdlabel.8.gz > Only in /usr/share/man/man8: fdisk.8.gz > Only in /usr/share/man/man9: DOMAIN_SET.9.gz > Only in /usr/share/man/man9: vm_page_sbusy.9.gz > Only in /usr/share/man/man9: vm_page_sleep_if_busy.9.gz > Only in /usr/share/man/man9: vm_page_xbusy.9.gz > Only in /usr/share/openssl/man/man1: asn1parse.1.gz > Only in /usr/share/openssl/man/man1: ca.1.gz > Only in /usr/share/openssl/man/man1: ciphers.1.gz > Only in /usr/share/openssl/man/man1: cms.1.gz > Only in /usr/share/openssl/man/man1: crl.1.gz > Only in /usr/share/openssl/man/man1: crl2pkcs7.1.gz > Only in /usr/share/openssl/man/man1: dgst.1.gz > Only in /usr/share/openssl/man/man1: dhparam.1.gz > Only in /usr/share/openssl/man/man1: dsa.1.gz > Only in /usr/share/openssl/man/man1: dsaparam.1.gz > Only in /usr/share/openssl/man/man1: ec.1.gz > Only in /usr/share/openssl/man/man1: ecparam.1.gz > Only in /usr/share/openssl/man/man1: enc.1.gz > Only in /usr/share/openssl/man/man1: engine.1.gz > Only in /usr/share/openssl/man/man1: errstr.1.gz > Only in /usr/share/openssl/man/man1: gendsa.1.gz > Only in /usr/share/openssl/man/man1: genpkey.1.gz > Only in /usr/share/openssl/man/man1: genrsa.1.gz > Only in /usr/share/openssl/man/man1: list.1.gz > Only in /usr/share/openssl/man/man1: nseq.1.gz > Only in /usr/share/openssl/man/man1: ocsp.1.gz > Only in /usr/share/openssl/man/man1: openssl-tsget.1.gz > Only in /usr/share/openssl/man/man1: passwd.1.gz > Only in /usr/share/openssl/man/man1: pkcs12.1.gz > Only in /usr/share/openssl/man/man1: pkcs7.1.gz > Only in /usr/share/openssl/man/man1: pkcs8.1.gz > Only in /usr/share/openssl/man/man1: pkey.1.gz > Only in /usr/share/openssl/man/man1: pkeyparam.1.gz > Only in /usr/share/openssl/man/man1: pkeyutl.1.gz > Only in /usr/share/openssl/man/man1: prime.1.gz > Only in /usr/share/openssl/man/man1: rand.1.gz > Only in /usr/share/openssl/man/man1: req.1.gz > Only in /usr/share/openssl/man/man1: rsa.1.gz > Only in /usr/share/openssl/man/man1: rsautl.1.gz > Only in /usr/share/openssl/man/man1: s_client.1.gz > Only in /usr/share/openssl/man/man1: s_server.1.gz > Only in /usr/share/openssl/man/man1: s_time.1.gz > Only in /usr/share/openssl/man/man1: sess_id.1.gz > Only in /usr/share/openssl/man/man1: smime.1.gz > Only in /usr/share/openssl/man/man1: speed.1.gz > Only in /usr/share/openssl/man/man1: spkac.1.gz > Only in /usr/share/openssl/man/man1: srp.1.gz > Only in /usr/share/openssl/man/man1: storeutl.1.gz > Only in /usr/share/openssl/man/man1: ts.1.gz > Only in /usr/share/openssl/man/man1: verify.1.gz > Only in /usr/share/openssl/man/man1: version.1.gz > Only in /usr/share/openssl/man/man1: x509.1.gz > Only in /usr/share/openssl/man/man3: ECDH_get_ex_data.3.gz > Only in /usr/share/openssl/man/man3: ECDH_get_ex_new_index.3.gz > Only in /usr/share/openssl/man/man3: ECDH_set_ex_data.3.gz > Only in /usr/share/openssl/man/man3: ERR_GET_FUNC.3.gz > Only in /usr/share/openssl/man/man3: EVP_PKEY_CTX_hkdf_mode.3.gz > Only in /usr/share/openssl/man/man3: EVP_PKEY_set_alias_type.3.gz > Only in /usr/share/openssl/man/man3: EVP_aes.3.gz > Only in /usr/share/openssl/man/man3: EVP_aria.3.gz > Only in /usr/share/openssl/man/man3: EVP_camellia.3.gz > Only in /usr/share/openssl/man/man3: EVP_des.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_bytes.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_cleanup_entropy_fn.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_cleanup_nonce_fn.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_free.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_generate.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_get0_master.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_get0_private.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_get0_public.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_get_entropy_fn.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_get_ex_data.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_get_ex_new_index.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_get_nonce_fn.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_instantiate.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_new.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_reseed.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_secure_new.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_set.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_set_callbacks.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_set_defaults.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_set_ex_data.3.gz > Only in /usr/share/openssl/man/man3: = RAND_DRBG_set_reseed_defaults.3.gz > Only in /usr/share/openssl/man/man3: = RAND_DRBG_set_reseed_interval.3.gz > Only in /usr/share/openssl/man/man3: = RAND_DRBG_set_reseed_time_interval.3.gz > Only in /usr/share/openssl/man/man3: RAND_DRBG_uninstantiate.3.gz > Only in /usr/share/openssl/man/man3: RSA_padding_add_SSLv23.3.gz > Only in /usr/share/openssl/man/man3: RSA_padding_check_SSLv23.3.gz > Only in /usr/share/openssl/man/man7: RAND_DRBG.7.gz > Only in /usr/share/openssl/man/man7: scrypt.7.gz > Only in /usr/tests/atf_python/sys/net: netlink.py > Only in /usr/tests/cddl/usr.sbin/dtrace/amd64: kinst > Only in /usr/tests/lib/libarchive: test_fuzz.cab.uu > Only in /usr/tests/lib/libarchive: test_fuzz.lzh.uu > Only in /usr/tests/lib/libarchive: test_fuzz_1.iso.Z.uu > Only in /usr/tests/lib/libbe: mnt > Only in /usr/tests/lib/libc/sys: brk_test > Only in /usr/tests/lib/libc/tls: libh_tls_dlopen_p.a > Only in /usr/tests/lib/libc/tls: libh_tls_dynamic_p.a > Only in /usr/tests/lib/libthr: swapcontext_test > Only in /usr/tests/libexec/rtld-elf: libpythagoras_p.a > Only in /usr/tests/sys/netpfil/pf: checksum > Only in /usr/tests/sys/netpfil/pf: fragmentation > Only in /usr/tests/sys/netpfil/pf: rdr > Only in /usr/tests/sys/netpfil/pf: scrub > Only in /usr/tests/usr.bin/gh-bc: .log_bc.txt > Only in /usr/tests/usr.bin/gh-bc: .log_bc_test.txt > Only in /usr/tests/usr.bin/gh-bc: .log_dc.txt > Only in /usr/tests/usr.bin/gh-bc: .log_dc_test.txt > Only in /usr/tests/usr.bin/gh-bc: functions.sh > Only in /usr/tests/usr.bin/gh-bc/tests: afl.py > Only in /usr/tests/usr.bin/gh-bc/tests: bc_outputs > Only in /usr/tests/usr.bin/gh-bc/tests/dc/errors: 34.txt > Only in /usr/tests/usr.bin/gh-bc/tests: dc_outputs > Only in /usr/tests/usr.bin/gh-bc/tests: diff.sh > Only in /usr/tests/usr.bin/gh-bc/tests: radamsa.sh > Only in /usr/tests/usr.bin/gh-bc/tests: radamsa.txt > Only in /usr/tests/usr.bin/gh-bc/tests: randmath.py > Only in /usr/tests/usr.bin: timeout > Only in /usr/tests/usr.sbin/mixer: Kyuafile > Only in /usr/tests/usr.sbin/mixer: mixer_test >=20 Mike Karels point out that my being a tester of early versions of the lib32 changes has lead to the following: QUOTE I'll note that /usr/include/machine includes some of the headers I added in intermediate versions of the lib32 patches, but were not in the committed version. Hence, they aren't in the lists for delete-old. Example: atomic-v6.h. END QUOTE =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Fri Jul 28 21:16:10 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 4RCL6K56Jbz4p7kw for ; Fri, 28 Jul 2023 21:16:25 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic310-21.consmr.mail.gq1.yahoo.com (sonic310-21.consmr.mail.gq1.yahoo.com [98.137.69.147]) (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 4RCL6J1ZPWz46lL for ; Fri, 28 Jul 2023 21:16:24 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=b7IExhVu; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.69.147 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=1690578982; bh=4fuxyk1XGg1l0lnHraDDhTZ/lPbEh3XVTBBqI+nLZDo=; h=From:Subject:Date:References:To:In-Reply-To:From:Subject:Reply-To; b=b7IExhVupW+XF4m6cPcwHtpHgfWl1VvF2XehYxPHnbgKd37Vbd9lTzzMrhwbUEHrb2SKhw2b+7ZvljoDrkS7A38owjyWXM8ZXyfynHT+hlN7r0NNdMoxlZm+UEh4jId6oJdIXY09eEGQ71N3w1dl+EAOZxC+HoqvjpZXOScb7X2MGm/Pw5kYCWKxBDGax2TJX3j34nJe2DgHGKADI2DKBeWNWW3uSHP0aoAeOvzCchXOOrEJWlj7CSysKHGb/nWBlCAp0zc7qCmxQJJD2tOOukJtjpSrtMMCZrdXoNU1Rj3i9saumJgHX6wWrUUBop4kJNyU0TFic2MfAWHTKYWXVA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1690578982; bh=6XiUpV6lUKJc9JEBWKO/Khy5cFlTgByODZ/TEPZr0MN=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=Lfone6e4zhSyDZZHRTo52bJdCpsUiKdfN9ws9FKCWwNZrfHEy1h+xWL5CC3H9T8mXN33409FpYHIu89vvjw3N68+WxEmdYJoEXTarear4D6OcaMbeYo3EqFisAvyPVNJ/XapCrb8TBxU0w1rIcsLAg+yltQ9PjANnKk1MJ7CrHM1BH0kvF4bdaYVXQRrYcAR88p/xEtee3UqcZjxVBAY6UPbJVEBSoyOku5P+b5wwgt+q5ZldQwvaC/+4PtEc1RZZN7MB64hvKrC0kqeRcp42dKa9SjD7XHVc/kSxuXc3BcHjVX9JbmV0QiZWnQ7yoBaXZFzkSItty0fB3NnruTc8A== X-YMail-OSG: r6uOoIUVM1kPFjqqCaSy.1NMSIuoLe_kYWuP5tEpVwh0cONyCWPwFGzYEXbl_hW ug9ShQ3N5OwBORldgX5wg6EePocJar2eZ3RWuO0ylZs4ql7w.b.HTiJ5LotjKcUsSdmgK8g3qUdn BzSEPorJEBfiJamvKKsWZQ1Ki8hfmvzkY1jqBEX3ubV6z4C7tzefJYy_I1oHzp1kYzOEwPCpxVvo EG793KejDnCnaesoT9C3jPSTyTQiUMerPE.j9pbvyJqmNPlBBxmEsrLg3bfu9522kbp26.OR0ofL vR4mN0gIynTMiUP54KTADu8JOkuTVq65pXEV93rNPqgmDzVZbZ9T1zuy3rWozTxrnw1XaocP3RPm qSLVVedPKtuXwdd4TCLsTrD0PAF0ljHnnxPH.GLdmy_AJFw9cf09KIcwpBrNl3xYltIjRIzLkr6k QFHZH1byZrcYl9JZO8j_qmXRMlDZYTCfE8miax6AD5LDEzkhojjK4BBT2_tE1iMapcyqknclx6l7 RZC3XqKrqkpy1jZO3pw6xNsRdgIoy8NoCzQHPIki.A_ph6mPlHHQgEBc_xtI9g5VZnf6cNRbq40_ bOpDaYGbeKMl.zWY0blF28Ulth0P3wLEBo7P0AIupTo6yAm97fiQb0vvLGpyUDQC3LHpPflP6bJI ZuUTo0WsyoHAwEC8cR7KhPuR895uGRhvyJFpPBFGP0gMiAfAIANa5pqnf_sGV57HRKGd3JnMFkkK 3IRUWgqRg1EZllXF7FEU62q7TV3XSugoE0f69hHJjotkckTJ7ALZD5x.j3P4YdEuqr2wTLIBpp8z xpnafQx6KLbPQDEFBlX9JtLR7ekUQi3ePboIHL_LKr9WixF2Q0oZYQK_Cg3dD6YiD7ncJQNVx6ST SExHqKoEvT40jbSH5TXspnxLLG.z6gWVHAxtPQqQcBNI3HbpAjwdrndlFKNryXcs91SKu7.VTSQE Ws4k903TSTFUscTtt_D2PyW7q3m4P4LjD.7pfE93oM7PhitDgCpdaUwoBjCJ4ZHE54dbZyfc3n0K MeqfztSPaW3r4gzvVBSzvusApMHyqvJju48vZ2drQmEsZQQi8uDbjuxhovh_29ZFSPwxSWvAf2Oq v1y2l8ZD4UJ2bltSPqSwvmbvRU.8T5VjFk.6f5PZrOUZXYz7ldtPFq2Qq2DhN2opCZpysgrh28Hs _qwoIHv_Talmg3c4guSonG7IXnpR2d1pD6B2wJzZ7umpcL6iOWINMs9xKLkg_cefGwAGtjYuGK57 fL.5kEagtZBs9e3RKyUmm5fo4WYmK.gSy0O7JtCjim0PaSeOliKd9fTGbEWG1jl6qjy45Cs5E6Sc b681WLCI0HbW8kWxdJNzY8afL1MLbMRUuuv8ERFrU6VWs5Q5fccOJkpY5zd_f6kHJ2COvlHnJM_Q wkEDnIoxcN1P29vCuRmHzqRdVnWsH5o_mpq21OqgBFWmaL52lwdJ8dQXxb4JzNXblXqhUsQ0a3x7 1ZKxTZ3I.anfqcVyCROgnkNHi0Aal6JrhKw9YFGkrfal_m2WSXsoPpbBi7vluBIWjp0sljrDqZ25 kaCS3F1me17piVYsDODCo7EAlUqeYDoHqQJ6BYd9ZN9u70XHoXFk.Gw_01RxQklyO2sHZekwuqco LPQyaMTnTQZAaPStDImlnYjlq4JvdUrU4Ph0sL3aCk8RyMMS5NUCwL8ogFJg8vF_aHEXBlfvWK45 CgtQR.HIPDB7jwFYthc7RtFSOpBGtpzyFYFQOcLW8S304HhbNgQtst_pD_51p6_ygUpRWV2RBRS. 8Q3ux3rfbAQJ6xWI3bXafyN1WKbCPppYodUeItc5fWu.innnjzrXJdpqr5JjVIyrlAnszZsU0MFh uziHrLrP8BhNFDJe0Cvdif491NF6otF8rR5dEeZmsAuA3er9AF6qUJd0n8KdO3K4Q9NZvGmyOZ68 LiJ25us4g61BbmpUnzRMA44kRNGWRte2858r1O_rMTbPDlGwoyttpMOwAfzpQnw7HWnHCDaKcTBo 0NVQvaK9QbK6md2Ykaz2U1f31.dUjW4wT4zLQksUaik_lqO5zWPWIjdIpUAofUu9VAHcN6GGs0BJ jPAHoOLXRGDN74tBZ0t54qvEm_po9gXtG5S7Hssoi08eSg.1ip0r277MyyS5QgUu1i05PDEzHG4a ZMjFkDcv0jhBL.xORpN1nhc2OUy.TPW4z1_RL1lBklaDYuvtflWt5nJOCaQ.xwaiWMqR4KOFsV.l nHM_8A9QZGTFoWKG45srUdKHPD9Yv8_qmaPSfbSW8dacJm8jZ9qs1bG2HVOwI8A-- X-Sonic-MF: X-Sonic-ID: 7401d97c-a78b-4248-8576-afa5d69c8d0a Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.gq1.yahoo.com with HTTP; Fri, 28 Jul 2023 21:16:22 +0000 Received: by hermes--production-gq1-7d844d8954-4ltdk (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 0677e90ca51ae3fab6bb8e5067d1b7c3; Fri, 28 Jul 2023 21:16:21 +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 \(3731.700.6\)) Subject: Re: delete-old status under /usr/ (aarch64 context example this time) Date: Fri, 28 Jul 2023 14:16:10 -0700 References: <42C003AA-2B46-470B-8DE4-7A556FD9E8D8@yahoo.com> To: Current FreeBSD In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3731.700.6) X-Spamd-Result: default: False [-2.51 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_LONG(-0.81)[-0.809]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; MV_CASE(0.50)[]; NEURAL_HAM_SHORT(-0.20)[-0.204]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.69.147:from]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[yahoo.com]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.69.147:from] X-Rspamd-Queue-Id: 4RCL6J1ZPWz46lL X-Spamd-Bar: -- On Jul 28, 2023, at 11:12, Mark Millard wrote: > On Jul 28, 2023, at 10:51, Mark Millard wrote: >=20 >> This is similar to my earlier amd64 report but shows in files >> associated with the recent old-arm cleanout and lib32 addition >> as well, for example. Again a comparison to a from-scratch >> install into an empty directry via: >>=20 >> installworld distrib-dirs distribution DB_FROM_SRC=3D1 installkernel >>=20 >> # uname -apKU >> FreeBSD CA72-16Gp-ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT aarch64 = 1400093 #102 main-n264334-215bab7924f6-dirty: Wed Jul 26 02:02:48 PDT = 2023 = root@CA72-16Gp-ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm6= 4.aarch64/sys/GENERIC-NODBG-CA72 arm64 aarch64 1400093 1400093 >>=20 >> I use delete-old and delete-old-libs with -DBATCH_DELETE_OLD_FILES >> in my update procedures and have for years. delete-old use is a >> step in scripts, not a manual operation. (delete-old-libs use >> requires more timing control and so is less automatic.) >>=20 >> I find the following when I look for potential old files in /usr/ = compared >> to what ended up in /tmp/main-amd64-installed-from-scratch/usr/ . = Much of >> the output seems to be old files that are still around but likely = should >> not be. >>=20 >> # diff -rq /tmp/main-CA72-installed-from-scratch/usr /usr | grep = "Only in /usr/" | grep -v -E = "(/usr/local:|/usr/obj:|/usr/lib/debug/boot: kernel\.)" >> diff: = /tmp/main-CA72-installed-from-scratch/usr/share/locale/nn_NO.ISO8859-1/LC_= MESSAGES: Too many levels of symbolic links >> diff: = /tmp/main-CA72-installed-from-scratch/usr/share/locale/nn_NO.ISO8859-15/LC= _MESSAGES: Too many levels of symbolic links >> diff: = /tmp/main-CA72-installed-from-scratch/usr/share/locale/sl_SI.ISO8859-2/LC_= MESSAGES: No such file or directory >> Only in /usr/include/dev/hwpmc: hwpmc_beri.h >> Only in /usr/include/dev/wg: compat.h >> Only in /usr/include/dev/wg: crypto.h >> Only in /usr/include/dev/wg: version.h >> Only in /usr/include/dev/wg: wg_cookie.h >> Only in /usr/include/dev/wg: wg_noise.h >> Only in /usr/include/machine: asmacros.h >> Only in /usr/include/machine: atags.h >> Only in /usr/include/machine: atomic-v6.h >> Only in /usr/include/machine: blockio.h >> Only in /usr/include/machine: cpu-v6.h >> Only in /usr/include/machine: fdt.h >> Only in /usr/include/machine: fiq.h >> Only in /usr/include/machine: ieee.h >> Only in /usr/include/machine: limits.h >> Only in /usr/include/machine: pl310.h >> Only in /usr/include/machine: platform.h >> Only in /usr/include/machine: platformvar.h >> Only in /usr/include/machine: pmap-v6.h >> Only in /usr/include/machine: pmap_var.h >> Only in /usr/include/machine: pte-v6.h >> Only in /usr/include/machine: sc_machdep.h >> Only in /usr/include/machine: swi.h >> Only in /usr/include/machine: utrap.h >> Only in /usr/include/sys: _cscan_atomic.h >> Only in /usr/include/sys: _cscan_bus.h >> Only in /usr/lib/debug/sbin: bsdlabel.debug >> Only in /usr/lib/debug/sbin: fdisk.debug >> Only in /usr/lib/debug/usr/bin: timeout.debug >> Only in /usr/lib/debug/usr/tests/cddl/usr.sbin/dtrace/amd64: kinst >> Only in /usr/lib/debug/usr/tests/lib/libc/sys: brk_test.debug >> Only in /usr/lib/debug/usr/tests/lib/libthr: swapcontext_test.debug >> Only in /usr/lib/debug/usr/tests/usr.bin: timeout >> Only in /usr/lib/include/dev/hwpmc: hwpmc_beri.h >> Only in /usr/lib/include/dev/wg: compat.h >> Only in /usr/lib/include/dev/wg: crypto.h >> Only in /usr/lib/include/dev/wg: version.h >> Only in /usr/lib/include/dev/wg: wg_cookie.h >> Only in /usr/lib/include/dev/wg: wg_noise.h >> Only in /usr/lib/include/machine: asmacros.h >> Only in /usr/lib/include/machine: atags.h >> Only in /usr/lib/include/machine: atomic-v6.h >> Only in /usr/lib/include/machine: blockio.h >> Only in /usr/lib/include/machine: cpu-v6.h >> Only in /usr/lib/include/machine: fdt.h >> Only in /usr/lib/include/machine: fiq.h >> Only in /usr/lib/include/machine: ieee.h >> Only in /usr/lib/include/machine: limits.h >> Only in /usr/lib/include/machine: pl310.h >> Only in /usr/lib/include/machine: platform.h >> Only in /usr/lib/include/machine: platformvar.h >> Only in /usr/lib/include/machine: pmap-v6.h >> Only in /usr/lib/include/machine: pmap_var.h >> Only in /usr/lib/include/machine: pte-v6.h >> Only in /usr/lib/include/machine: sc_machdep.h >> Only in /usr/lib/include/machine: swi.h >> Only in /usr/lib/include/machine: utrap.h >> Only in /usr/lib/include/sys: _cscan_atomic.h >> Only in /usr/lib/include/sys: _cscan_bus.h >> Only in /usr/share/certs/trusted: = Camerfirma_Chambers_of_Commerce_Root.pem >> Only in /usr/share/certs/trusted: = Camerfirma_Global_Chambersign_Root.pem >> Only in /usr/share/certs/trusted: Certum_Root_CA.pem >> Only in /usr/share/certs/trusted: = Chambers_of_Commerce_Root_-_2008.pem >> Only in /usr/share/certs/trusted: D-TRUST_Root_CA_3_2013.pem >> Only in /usr/share/certs/trusted: EC-ACC.pem >> Only in /usr/share/certs/trusted: = GeoTrust_Primary_Certification_Authority_-_G2.pem >> Only in /usr/share/certs/trusted: Global_Chambersign_Root_-_2008.pem >> Only in /usr/share/certs/trusted: OISTE_WISeKey_Global_Root_GA_CA.pem >> Only in /usr/share/certs/trusted: QuoVadis_Root_CA.pem >> Only in /usr/share/certs/trusted: Sonera_Class_2_Root_CA.pem >> Only in /usr/share/certs/trusted: = Staat_der_Nederlanden_Root_CA_-_G3.pem >> Only in /usr/share/certs/trusted: SwissSign_Platinum_CA_-_G2.pem >> diff: /tmp/main-CA72-installed-from-scratch/usr/tests/local: No such = file or directory >> diff: = /tmp/main-CA72-installed-from-scratch/usr/tests/sys/pjdfstest/tests/tests/= tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/te= sts/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/test= s/tests/tests/tests/tests/tests/tests: Too many levels of symbolic links >> Only in /usr/share/certs/trusted: = Symantec_Class_1_Public_Primary_Certification_Authority_-_G6.pem >> Only in /usr/share/certs/trusted: = Symantec_Class_2_Public_Primary_Certification_Authority_-_G6.pem >> Only in /usr/share/certs/trusted: Trustis_FPS_Root_CA.pem >> Only in /usr/share/certs/trusted: = VeriSign_Universal_Root_Certification_Authority.pem >> Only in /usr/share/certs/trusted: = Verisign_Class_1_Public_Primary_Certification_Authority_-_G3.pem >> Only in /usr/share/certs/trusted: = Verisign_Class_2_Public_Primary_Certification_Authority_-_G3.pem >> Only in /usr/share/doc/legal: sdma-imx6q.LICENSE >> Only in /usr/share/locale/hr_HR.ISO8859-2: LC_MESSAGES >> Only in /usr/share/locale/nl_BE.ISO8859-1: LC_MESSAGES >> Only in /usr/share/locale/nl_BE.ISO8859-15: LC_MESSAGES >> Only in /usr/share/locale/sr_RS.ISO8859-2: LC_MESSAGES >> Only in /usr/share/locale/zh_TW.Big5: LC_NUMERIC >> Only in /usr/share/man/man2: arm_drain_writebuf.2.gz >> Only in /usr/share/man/man2: arm_sync_icache.2.gz >> Only in /usr/share/man/man4/aarch64: aw_gpio.4.gz >> Only in /usr/share/man/man4/aarch64: aw_mmc.4.gz >> Only in /usr/share/man/man4/aarch64: aw_rtc.4.gz >> Only in /usr/share/man/man4/aarch64: aw_sid.4.gz >> Only in /usr/share/man/man4/aarch64: aw_spi.4.gz >> Only in /usr/share/man/man4/aarch64: aw_syscon.4.gz >> Only in /usr/share/man/man4/aarch64: bcm283x_pwm.4.gz >> Only in /usr/share/man/man4: ce.4.gz >> Only in /usr/share/man/man4: cp.4.gz >> Only in /usr/share/man/man4/i386: ce.4.gz >> Only in /usr/share/man/man4/i386: cp.4.gz >> Only in /usr/share/man/man4: if_an.4.gz >> Only in /usr/share/man/man5: portsnap.conf.5.gz >> Only in /usr/share/man/man8: bsdlabel.8.gz >> Only in /usr/share/man/man8: fdisk.8.gz >> Only in /usr/share/man/man9: DOMAIN_SET.9.gz >> Only in /usr/share/man/man9: vm_page_sbusy.9.gz >> Only in /usr/share/man/man9: vm_page_sleep_if_busy.9.gz >> Only in /usr/share/man/man9: vm_page_xbusy.9.gz >> Only in /usr/share/openssl/man/man1: asn1parse.1.gz >> Only in /usr/share/openssl/man/man1: ca.1.gz >> Only in /usr/share/openssl/man/man1: ciphers.1.gz >> Only in /usr/share/openssl/man/man1: cms.1.gz >> Only in /usr/share/openssl/man/man1: crl.1.gz >> Only in /usr/share/openssl/man/man1: crl2pkcs7.1.gz >> Only in /usr/share/openssl/man/man1: dgst.1.gz >> Only in /usr/share/openssl/man/man1: dhparam.1.gz >> Only in /usr/share/openssl/man/man1: dsa.1.gz >> Only in /usr/share/openssl/man/man1: dsaparam.1.gz >> Only in /usr/share/openssl/man/man1: ec.1.gz >> Only in /usr/share/openssl/man/man1: ecparam.1.gz >> Only in /usr/share/openssl/man/man1: enc.1.gz >> Only in /usr/share/openssl/man/man1: engine.1.gz >> Only in /usr/share/openssl/man/man1: errstr.1.gz >> Only in /usr/share/openssl/man/man1: gendsa.1.gz >> Only in /usr/share/openssl/man/man1: genpkey.1.gz >> Only in /usr/share/openssl/man/man1: genrsa.1.gz >> Only in /usr/share/openssl/man/man1: list.1.gz >> Only in /usr/share/openssl/man/man1: nseq.1.gz >> Only in /usr/share/openssl/man/man1: ocsp.1.gz >> Only in /usr/share/openssl/man/man1: openssl-tsget.1.gz >> Only in /usr/share/openssl/man/man1: passwd.1.gz >> Only in /usr/share/openssl/man/man1: pkcs12.1.gz >> Only in /usr/share/openssl/man/man1: pkcs7.1.gz >> Only in /usr/share/openssl/man/man1: pkcs8.1.gz >> Only in /usr/share/openssl/man/man1: pkey.1.gz >> Only in /usr/share/openssl/man/man1: pkeyparam.1.gz >> Only in /usr/share/openssl/man/man1: pkeyutl.1.gz >> Only in /usr/share/openssl/man/man1: prime.1.gz >> Only in /usr/share/openssl/man/man1: rand.1.gz >> Only in /usr/share/openssl/man/man1: req.1.gz >> Only in /usr/share/openssl/man/man1: rsa.1.gz >> Only in /usr/share/openssl/man/man1: rsautl.1.gz >> Only in /usr/share/openssl/man/man1: s_client.1.gz >> Only in /usr/share/openssl/man/man1: s_server.1.gz >> Only in /usr/share/openssl/man/man1: s_time.1.gz >> Only in /usr/share/openssl/man/man1: sess_id.1.gz >> Only in /usr/share/openssl/man/man1: smime.1.gz >> Only in /usr/share/openssl/man/man1: speed.1.gz >> Only in /usr/share/openssl/man/man1: spkac.1.gz >> Only in /usr/share/openssl/man/man1: srp.1.gz >> Only in /usr/share/openssl/man/man1: storeutl.1.gz >> Only in /usr/share/openssl/man/man1: ts.1.gz >> Only in /usr/share/openssl/man/man1: verify.1.gz >> Only in /usr/share/openssl/man/man1: version.1.gz >> Only in /usr/share/openssl/man/man1: x509.1.gz >> Only in /usr/share/openssl/man/man3: ECDH_get_ex_data.3.gz >> Only in /usr/share/openssl/man/man3: ECDH_get_ex_new_index.3.gz >> Only in /usr/share/openssl/man/man3: ECDH_set_ex_data.3.gz >> Only in /usr/share/openssl/man/man3: ERR_GET_FUNC.3.gz >> Only in /usr/share/openssl/man/man3: EVP_PKEY_CTX_hkdf_mode.3.gz >> Only in /usr/share/openssl/man/man3: EVP_PKEY_set_alias_type.3.gz >> Only in /usr/share/openssl/man/man3: EVP_aes.3.gz >> Only in /usr/share/openssl/man/man3: EVP_aria.3.gz >> Only in /usr/share/openssl/man/man3: EVP_camellia.3.gz >> Only in /usr/share/openssl/man/man3: EVP_des.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_bytes.3.gz >> Only in /usr/share/openssl/man/man3: = RAND_DRBG_cleanup_entropy_fn.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_cleanup_nonce_fn.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_free.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_generate.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_get0_master.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_get0_private.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_get0_public.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_get_entropy_fn.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_get_ex_data.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_get_ex_new_index.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_get_nonce_fn.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_instantiate.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_new.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_reseed.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_secure_new.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_set.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_set_callbacks.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_set_defaults.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_set_ex_data.3.gz >> Only in /usr/share/openssl/man/man3: = RAND_DRBG_set_reseed_defaults.3.gz >> Only in /usr/share/openssl/man/man3: = RAND_DRBG_set_reseed_interval.3.gz >> Only in /usr/share/openssl/man/man3: = RAND_DRBG_set_reseed_time_interval.3.gz >> Only in /usr/share/openssl/man/man3: RAND_DRBG_uninstantiate.3.gz >> Only in /usr/share/openssl/man/man3: RSA_padding_add_SSLv23.3.gz >> Only in /usr/share/openssl/man/man3: RSA_padding_check_SSLv23.3.gz >> Only in /usr/share/openssl/man/man7: RAND_DRBG.7.gz >> Only in /usr/share/openssl/man/man7: scrypt.7.gz >> Only in /usr/tests/atf_python/sys/net: netlink.py >> Only in /usr/tests/cddl/usr.sbin/dtrace/amd64: kinst >> Only in /usr/tests/lib/libarchive: test_fuzz.cab.uu >> Only in /usr/tests/lib/libarchive: test_fuzz.lzh.uu >> Only in /usr/tests/lib/libarchive: test_fuzz_1.iso.Z.uu >> Only in /usr/tests/lib/libbe: mnt >> Only in /usr/tests/lib/libc/sys: brk_test >> Only in /usr/tests/lib/libc/tls: libh_tls_dlopen_p.a >> Only in /usr/tests/lib/libc/tls: libh_tls_dynamic_p.a >> Only in /usr/tests/lib/libthr: swapcontext_test >> Only in /usr/tests/libexec/rtld-elf: libpythagoras_p.a >> Only in /usr/tests/sys/netpfil/pf: checksum >> Only in /usr/tests/sys/netpfil/pf: fragmentation >> Only in /usr/tests/sys/netpfil/pf: rdr >> Only in /usr/tests/sys/netpfil/pf: scrub >> Only in /usr/tests/usr.bin/gh-bc: .log_bc.txt >> Only in /usr/tests/usr.bin/gh-bc: .log_bc_test.txt >> Only in /usr/tests/usr.bin/gh-bc: .log_dc.txt >> Only in /usr/tests/usr.bin/gh-bc: .log_dc_test.txt >> Only in /usr/tests/usr.bin/gh-bc: functions.sh >> Only in /usr/tests/usr.bin/gh-bc/tests: afl.py >> Only in /usr/tests/usr.bin/gh-bc/tests: bc_outputs >> Only in /usr/tests/usr.bin/gh-bc/tests/dc/errors: 34.txt >> Only in /usr/tests/usr.bin/gh-bc/tests: dc_outputs >> Only in /usr/tests/usr.bin/gh-bc/tests: diff.sh >> Only in /usr/tests/usr.bin/gh-bc/tests: radamsa.sh >> Only in /usr/tests/usr.bin/gh-bc/tests: radamsa.txt >> Only in /usr/tests/usr.bin/gh-bc/tests: randmath.py >> Only in /usr/tests/usr.bin: timeout >> Only in /usr/tests/usr.sbin/mixer: Kyuafile >> Only in /usr/tests/usr.sbin/mixer: mixer_test >>=20 >=20 > Mike Karels point out that my being a tester of early versions > of the lib32 changes has lead to the following: >=20 > QUOTE > I'll note that /usr/include/machine includes some of the headers I > added in intermediate versions of the lib32 patches, but were not in > the committed version. Hence, they aren't in the lists for = delete-old. > Example: atomic-v6.h. > END QUOTE I'm adding a list from another system where some pc98 files showed up in the list under /usr/tests/usr.bin/mkimg/ . # uname -apKU FreeBSD R64-RPi-4-3-2v1p2 14.0-CURRENT FreeBSD 14.0-CURRENT #76 = main-n264171-2a0c0aea4209-dirty: Sat Jul 15 00:36:13 PDT 2023 = root@CA72-16Gp-ZFS:/usr/obj/BUILDs/main-CA53-nodbg-clang/usr/main-src/arm6= 4.aarch64/sys/GENERIC-NODBG-CA53 arm64 aarch64 1400093 1400093 # diff -rq /tmp/main-CA53-installed-from-scratch/usr /usr | grep "Only = in /usr/" | grep -v -E "(/usr/local:|/usr/obj:|/usr/lib/debug/boot: = kernel\.)" | sort diff: = /tmp/main-CA53-installed-from-scratch/usr/share/locale/nn_NO.ISO8859-1/LC_= MESSAGES: Too many levels of symbolic links diff: = /tmp/main-CA53-installed-from-scratch/usr/share/locale/nn_NO.ISO8859-15/LC= _MESSAGES: Too many levels of symbolic links diff: = /tmp/main-CA53-installed-from-scratch/usr/share/locale/sl_SI.ISO8859-2/LC_= MESSAGES: No such file or directory diff: /tmp/main-CA53-installed-from-scratch/usr/tests/local: No such = file or directory diff: = /tmp/main-CA53-installed-from-scratch/usr/tests/sys/pjdfstest/tests/tests/= tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/te= sts/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/test= s/tests/tests/tests/tests/tests/tests: Too many levels of symbolic links Only in /usr/include/cam/mmc: mmc_sdio.h Only in /usr/include/cam/scsi: scsi_dvcfg.h Only in /usr/include/cam/scsi: scsi_low.h Only in /usr/include/dev/hwpmc: hwpmc_beri.h Only in /usr/include/dev/hwpmc: hwpmc_pentium.h Only in /usr/include/dev/hwpmc: hwpmc_piv.h Only in /usr/include/dev/hwpmc: hwpmc_ppro.h Only in /usr/include/dev/wg: compat.h Only in /usr/include/dev/wg: crypto.h Only in /usr/include/dev/wg: version.h Only in /usr/include/dev/wg: wg_cookie.h Only in /usr/include/dev/wg: wg_noise.h Only in /usr/include/dev: nand Only in /usr/include/fs: nandfs Only in /usr/include/net: if_tapvar.h Only in /usr/include/net: iso88025.h Only in /usr/include/netinet: sctp_dtrace_declare.h Only in /usr/include/netinet: sctp_dtrace_define.h Only in /usr/include/sys: _cscan_atomic.h Only in /usr/include/sys: _cscan_bus.h Only in /usr/include/sys: _kstack_cache.h Only in /usr/include/sys: _vm_domain.h Only in /usr/include/sys: epoch_private.h Only in /usr/include/sys: gzio.h Only in /usr/include/sys: sockstate.h Only in /usr/include/sys: sun_disklabel.h Only in /usr/include/vm: vm_domain.h Only in /usr/lib/debug/boot: kerdbg Only in /usr/lib/debug/usr/bin: c++filt.debug Only in /usr/lib/debug/usr/bin: dc.debug Only in /usr/lib/debug/usr/bin: timeout.debug Only in /usr/lib/debug/usr/bin: zstreamdump.debug Only in /usr/lib/debug/usr/tests/bin: rcp Only in /usr/lib/debug/usr/tests/cddl/usr.sbin/dtrace/amd64: kinst Only in /usr/lib/debug/usr/tests/lib: libpam Only in /usr/lib/debug/usr/tests/usr.bin: timeout Only in /usr/lib/debug/usr: lib32 Only in /usr/lib/include/cam/mmc: mmc_sdio.h Only in /usr/lib/include/cam/scsi: scsi_dvcfg.h Only in /usr/lib/include/cam/scsi: scsi_low.h Only in /usr/lib/include/dev/hwpmc: hwpmc_beri.h Only in /usr/lib/include/dev/hwpmc: hwpmc_pentium.h Only in /usr/lib/include/dev/hwpmc: hwpmc_piv.h Only in /usr/lib/include/dev/hwpmc: hwpmc_ppro.h Only in /usr/lib/include/dev/wg: compat.h Only in /usr/lib/include/dev/wg: crypto.h Only in /usr/lib/include/dev/wg: version.h Only in /usr/lib/include/dev/wg: wg_cookie.h Only in /usr/lib/include/dev/wg: wg_noise.h Only in /usr/lib/include/dev: nand Only in /usr/lib/include/fs: nandfs Only in /usr/lib/include/net: if_tapvar.h Only in /usr/lib/include/net: iso88025.h Only in /usr/lib/include/netinet: sctp_dtrace_declare.h Only in /usr/lib/include/netinet: sctp_dtrace_define.h Only in /usr/lib/include/sys: _cscan_atomic.h Only in /usr/lib/include/sys: _cscan_bus.h Only in /usr/lib/include/sys: _kstack_cache.h Only in /usr/lib/include/sys: _vm_domain.h Only in /usr/lib/include/sys: epoch_private.h Only in /usr/lib/include/sys: gzio.h Only in /usr/lib/include/sys: sockstate.h Only in /usr/lib/include/sys: sun_disklabel.h Only in /usr/lib/include/vm: vm_domain.h Only in /usr/share/certs/trusted: AddTrust_External_Root.pem Only in /usr/share/certs/trusted: AddTrust_Low-Value_Services_Root.pem Only in /usr/share/certs/trusted: = Camerfirma_Chambers_of_Commerce_Root.pem Only in /usr/share/certs/trusted: Camerfirma_Global_Chambersign_Root.pem Only in /usr/share/certs/trusted: Certum_Root_CA.pem Only in /usr/share/certs/trusted: Chambers_of_Commerce_Root_-_2008.pem Only in /usr/share/certs/trusted: D-TRUST_Root_CA_3_2013.pem Only in /usr/share/certs/trusted: EC-ACC.pem Only in /usr/share/certs/trusted: EE_Certification_Centre_Root_CA.pem Only in /usr/share/certs/trusted: GeoTrust_Global_CA.pem Only in /usr/share/certs/trusted: = GeoTrust_Primary_Certification_Authority.pem Only in /usr/share/certs/trusted: = GeoTrust_Primary_Certification_Authority_-_G2.pem Only in /usr/share/certs/trusted: = GeoTrust_Primary_Certification_Authority_-_G3.pem Only in /usr/share/certs/trusted: GeoTrust_Universal_CA.pem Only in /usr/share/certs/trusted: GeoTrust_Universal_CA_2.pem Only in /usr/share/certs/trusted: Global_Chambersign_Root_-_2008.pem Only in /usr/share/certs/trusted: LuxTrust_Global_Root_2.pem Only in /usr/share/certs/trusted: OISTE_WISeKey_Global_Root_GA_CA.pem Only in /usr/share/certs/trusted: QuoVadis_Root_CA.pem Only in /usr/share/certs/trusted: Sonera_Class_2_Root_CA.pem Only in /usr/share/certs/trusted: Staat_der_Nederlanden_Root_CA_-_G2.pem Only in /usr/share/certs/trusted: Staat_der_Nederlanden_Root_CA_-_G3.pem Only in /usr/share/certs/trusted: SwissSign_Platinum_CA_-_G2.pem Only in /usr/share/certs/trusted: = Symantec_Class_1_Public_Primary_Certification_Authority_-_G4.pem Only in /usr/share/certs/trusted: = Symantec_Class_1_Public_Primary_Certification_Authority_-_G6.pem Only in /usr/share/certs/trusted: = Symantec_Class_2_Public_Primary_Certification_Authority_-_G4.pem Only in /usr/share/certs/trusted: = Symantec_Class_2_Public_Primary_Certification_Authority_-_G6.pem Only in /usr/share/certs/trusted: Taiwan_GRCA.pem Only in /usr/share/certs/trusted: Trustis_FPS_Root_CA.pem Only in /usr/share/certs/trusted: = VeriSign_Class_3_Public_Primary_Certification_Authority_-_G4.pem Only in /usr/share/certs/trusted: = VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.pem Only in /usr/share/certs/trusted: = VeriSign_Universal_Root_Certification_Authority.pem Only in /usr/share/certs/trusted: = Verisign_Class_1_Public_Primary_Certification_Authority_-_G3.pem Only in /usr/share/certs/trusted: = Verisign_Class_2_Public_Primary_Certification_Authority_-_G3.pem Only in /usr/share/certs/trusted: = Verisign_Class_3_Public_Primary_Certification_Authority_-_G3.pem Only in /usr/share/certs/trusted: thawte_Primary_Root_CA.pem Only in /usr/share/certs/trusted: thawte_Primary_Root_CA_-_G2.pem Only in /usr/share/certs/trusted: thawte_Primary_Root_CA_-_G3.pem Only in /usr/share/examples/printing: README Only in /usr/share/locale/hr_HR.ISO8859-2: LC_MESSAGES Only in /usr/share/locale/nl_BE.ISO8859-15: LC_MESSAGES Only in /usr/share/locale/nl_BE.ISO8859-1: LC_MESSAGES Only in /usr/share/locale/sr_RS.ISO8859-2: LC_MESSAGES Only in /usr/share/locale/zh_TW.Big5: LC_NUMERIC Only in /usr/share/man/man4/aarch64: aw_gpio.4.gz Only in /usr/share/man/man4/aarch64: aw_mmc.4.gz Only in /usr/share/man/man4/aarch64: aw_rtc.4.gz Only in /usr/share/man/man4/aarch64: aw_sid.4.gz Only in /usr/share/man/man4/aarch64: aw_spi.4.gz Only in /usr/share/man/man4/aarch64: aw_syscon.4.gz Only in /usr/share/man/man4/aarch64: bcm283x_pwm.4.gz Only in /usr/share/man/man4/i386: ce.4.gz Only in /usr/share/man/man4/i386: cp.4.gz Only in /usr/share/man/man4: ce.4.gz Only in /usr/share/man/man4: cp.4.gz Only in /usr/share/man/man4: if_an.4.gz Only in /usr/share/man/man4: smartpqi.4.gz Only in /usr/share/man/man4: sparc64 Only in /usr/share/man/man5: portsnap.conf.5.gz Only in /usr/share/man/man8: sparc64 Only in /usr/share/man/man9: DOMAIN_SET.9.gz Only in /usr/share/man/man9: vm_page_sbusy.9.gz Only in /usr/share/man/man9: vm_page_sleep_if_busy.9.gz Only in /usr/share/man/man9: vm_page_xbusy.9.gz Only in /usr/share/nls: en_US.US-ASCII Only in /usr/share/openssl/man/man1: asn1parse.1.gz Only in /usr/share/openssl/man/man1: ca.1.gz Only in /usr/share/openssl/man/man1: ciphers.1.gz Only in /usr/share/openssl/man/man1: cms.1.gz Only in /usr/share/openssl/man/man1: crl.1.gz Only in /usr/share/openssl/man/man1: crl2pkcs7.1.gz Only in /usr/share/openssl/man/man1: dgst.1.gz Only in /usr/share/openssl/man/man1: dhparam.1.gz Only in /usr/share/openssl/man/man1: dsa.1.gz Only in /usr/share/openssl/man/man1: dsaparam.1.gz Only in /usr/share/openssl/man/man1: ec.1.gz Only in /usr/share/openssl/man/man1: ecparam.1.gz Only in /usr/share/openssl/man/man1: enc.1.gz Only in /usr/share/openssl/man/man1: engine.1.gz Only in /usr/share/openssl/man/man1: errstr.1.gz Only in /usr/share/openssl/man/man1: gendsa.1.gz Only in /usr/share/openssl/man/man1: genpkey.1.gz Only in /usr/share/openssl/man/man1: genrsa.1.gz Only in /usr/share/openssl/man/man1: list.1.gz Only in /usr/share/openssl/man/man1: nseq.1.gz Only in /usr/share/openssl/man/man1: ocsp.1.gz Only in /usr/share/openssl/man/man1: openssl-tsget.1.gz Only in /usr/share/openssl/man/man1: passwd.1.gz Only in /usr/share/openssl/man/man1: pkcs12.1.gz Only in /usr/share/openssl/man/man1: pkcs7.1.gz Only in /usr/share/openssl/man/man1: pkcs8.1.gz Only in /usr/share/openssl/man/man1: pkey.1.gz Only in /usr/share/openssl/man/man1: pkeyparam.1.gz Only in /usr/share/openssl/man/man1: pkeyutl.1.gz Only in /usr/share/openssl/man/man1: prime.1.gz Only in /usr/share/openssl/man/man1: rand.1.gz Only in /usr/share/openssl/man/man1: req.1.gz Only in /usr/share/openssl/man/man1: rsa.1.gz Only in /usr/share/openssl/man/man1: rsautl.1.gz Only in /usr/share/openssl/man/man1: s_client.1.gz Only in /usr/share/openssl/man/man1: s_server.1.gz Only in /usr/share/openssl/man/man1: s_time.1.gz Only in /usr/share/openssl/man/man1: sess_id.1.gz Only in /usr/share/openssl/man/man1: smime.1.gz Only in /usr/share/openssl/man/man1: speed.1.gz Only in /usr/share/openssl/man/man1: spkac.1.gz Only in /usr/share/openssl/man/man1: srp.1.gz Only in /usr/share/openssl/man/man1: storeutl.1.gz Only in /usr/share/openssl/man/man1: ts.1.gz Only in /usr/share/openssl/man/man1: verify.1.gz Only in /usr/share/openssl/man/man1: version.1.gz Only in /usr/share/openssl/man/man1: x509.1.gz Only in /usr/share/openssl/man/man3: ECDH_get_ex_data.3.gz Only in /usr/share/openssl/man/man3: ECDH_get_ex_new_index.3.gz Only in /usr/share/openssl/man/man3: ECDH_set_ex_data.3.gz Only in /usr/share/openssl/man/man3: ERR_GET_FUNC.3.gz Only in /usr/share/openssl/man/man3: EVP_PKEY_CTX_hkdf_mode.3.gz Only in /usr/share/openssl/man/man3: EVP_PKEY_set_alias_type.3.gz Only in /usr/share/openssl/man/man3: EVP_aes.3.gz Only in /usr/share/openssl/man/man3: EVP_aria.3.gz Only in /usr/share/openssl/man/man3: EVP_camellia.3.gz Only in /usr/share/openssl/man/man3: EVP_des.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_bytes.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_cleanup_entropy_fn.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_cleanup_nonce_fn.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_free.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_generate.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get0_master.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get0_private.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get0_public.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get_entropy_fn.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get_ex_data.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get_ex_new_index.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_get_nonce_fn.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_instantiate.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_new.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_reseed.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_secure_new.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set_callbacks.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set_defaults.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set_ex_data.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set_reseed_defaults.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_set_reseed_interval.3.gz Only in /usr/share/openssl/man/man3: = RAND_DRBG_set_reseed_time_interval.3.gz Only in /usr/share/openssl/man/man3: RAND_DRBG_uninstantiate.3.gz Only in /usr/share/openssl/man/man3: RSA_padding_add_SSLv23.3.gz Only in /usr/share/openssl/man/man3: RSA_padding_check_SSLv23.3.gz Only in /usr/share/openssl/man/man7: RAND_DRBG.7.gz Only in /usr/share/openssl/man/man7: scrypt.7.gz Only in /usr/tests/atf_python/sys/net: netlink.py Only in /usr/tests/bin: rcp Only in /usr/tests/cddl/usr.sbin/dtrace/amd64: kinst Only in /usr/tests/gnu/usr.bin/diff: Kyuafile Only in /usr/tests/gnu/usr.bin/diff: d_mallocv1.in Only in /usr/tests/gnu/usr.bin/diff: d_mallocv2.in Only in /usr/tests/gnu/usr.bin/diff: diff_test Only in /usr/tests/lib/libarchive: = test_compat_pax_libarchive_2x.tar.Z.uu Only in /usr/tests/lib/libarchive: test_fuzz.cab.uu Only in /usr/tests/lib/libarchive: test_fuzz.lzh.uu Only in /usr/tests/lib/libarchive: test_fuzz_1.iso.Z.uu Only in /usr/tests/lib/libarchive: test_read_pax_schily_xattr.tar.uu Only in /usr/tests/lib/libbe: mnt Only in /usr/tests/lib/libc/tls: libh_tls_dlopen_p.a Only in /usr/tests/lib/libc/tls: libh_tls_dynamic_p.a Only in /usr/tests/lib: libpam Only in /usr/tests/libexec/rtld-elf: libpythagoras_p.a Only in /usr/tests/sbin/pfctl/files: pfctl_test_descr.sh Only in /usr/tests/sys/geom/class/eli: attach_d_test Only in /usr/tests/sys/geom/class/eli: configure_b_B_test Only in /usr/tests/sys/geom/class/eli: detach_l_test Only in /usr/tests/sys/geom/class/eli: init_B_test Only in /usr/tests/sys/geom/class/eli: init_J_test Only in /usr/tests/sys/geom/class/eli: init_a_test Only in /usr/tests/sys/geom/class/eli: init_alias_test Only in /usr/tests/sys/geom/class/eli: init_i_P_test Only in /usr/tests/sys/geom/class/eli: integrity_copy_test Only in /usr/tests/sys/geom/class/eli: integrity_data_test Only in /usr/tests/sys/geom/class/eli: integrity_hmac_test Only in /usr/tests/sys/geom/class/eli: nokey_test Only in /usr/tests/sys/geom/class/eli: onetime_a_test Only in /usr/tests/sys/geom/class/eli: onetime_d_test Only in /usr/tests/sys/geom/class/eli: readonly_test Only in /usr/tests/sys/netpfil/pf: checksum Only in /usr/tests/sys/netpfil/pf: fragmentation Only in /usr/tests/sys/netpfil/pf: rdr Only in /usr/tests/sys/netpfil/pf: scrub Only in /usr/tests/usr.bin/gh-bc/tests/dc/errors: 34.txt Only in /usr/tests/usr.bin/gh-bc/tests: afl.py Only in /usr/tests/usr.bin/gh-bc/tests: diff.sh Only in /usr/tests/usr.bin/gh-bc/tests: radamsa.sh Only in /usr/tests/usr.bin/gh-bc/tests: radamsa.txt Only in /usr/tests/usr.bin/gh-bc/tests: randmath.py Only in /usr/tests/usr.bin/gh-bc: functions.sh Only in /usr/tests/usr.bin/hexdump: d_hexdump_dflag_a.out Only in /usr/tests/usr.bin/hexdump: d_hexdump_dflag_b.out Only in /usr/tests/usr.bin/hexdump: d_hexdump_dflag_c.out Only in /usr/tests/usr.bin/hexdump: d_hexdump_oflag_a.out Only in /usr/tests/usr.bin/hexdump: d_hexdump_oflag_b.out Only in /usr/tests/usr.bin/hexdump: d_hexdump_oflag_c.out Only in /usr/tests/usr.bin/hexdump: d_hexdump_xflag_a.out Only in /usr/tests/usr.bin/hexdump: d_hexdump_xflag_b.out Only in /usr/tests/usr.bin/hexdump: d_hexdump_xflag_c.out Only in /usr/tests/usr.bin/indent: nsac.0 Only in /usr/tests/usr.bin/indent: nsac.0.pro Only in /usr/tests/usr.bin/indent: nsac.0.stdout Only in /usr/tests/usr.bin/indent: sac.0 Only in /usr/tests/usr.bin/indent: sac.0.pro Only in /usr/tests/usr.bin/indent: sac.0.stdout Only in /usr/tests/usr.bin/mkimg: img-1x1-4096-pc98.qcow Only in /usr/tests/usr.bin/mkimg: img-1x1-4096-pc98.qcow2 Only in /usr/tests/usr.bin/mkimg: img-1x1-4096-pc98.raw Only in /usr/tests/usr.bin/mkimg: img-1x1-4096-pc98.vhd Only in /usr/tests/usr.bin/mkimg: img-1x1-4096-pc98.vhdf Only in /usr/tests/usr.bin/mkimg: img-1x1-4096-pc98.vmdk Only in /usr/tests/usr.bin/mkimg: img-1x1-512-pc98.qcow Only in /usr/tests/usr.bin/mkimg: img-1x1-512-pc98.qcow2 Only in /usr/tests/usr.bin/mkimg: img-1x1-512-pc98.raw Only in /usr/tests/usr.bin/mkimg: img-1x1-512-pc98.vhd Only in /usr/tests/usr.bin/mkimg: img-1x1-512-pc98.vhdf Only in /usr/tests/usr.bin/mkimg: img-1x1-512-pc98.vmdk Only in /usr/tests/usr.bin/mkimg: img-63x255-4096-pc98.qcow Only in /usr/tests/usr.bin/mkimg: img-63x255-4096-pc98.qcow2 Only in /usr/tests/usr.bin/mkimg: img-63x255-4096-pc98.raw Only in /usr/tests/usr.bin/mkimg: img-63x255-4096-pc98.vhd Only in /usr/tests/usr.bin/mkimg: img-63x255-4096-pc98.vhdf Only in /usr/tests/usr.bin/mkimg: img-63x255-4096-pc98.vmdk Only in /usr/tests/usr.bin/mkimg: img-63x255-512-pc98.qcow Only in /usr/tests/usr.bin/mkimg: img-63x255-512-pc98.qcow2 Only in /usr/tests/usr.bin/mkimg: img-63x255-512-pc98.raw Only in /usr/tests/usr.bin/mkimg: img-63x255-512-pc98.vhd Only in /usr/tests/usr.bin/mkimg: img-63x255-512-pc98.vhdf Only in /usr/tests/usr.bin/mkimg: img-63x255-512-pc98.vmdk Only in /usr/tests/usr.bin: timeout Only in /usr/tests/usr.sbin/mixer: Kyuafile Only in /usr/tests/usr.sbin/mixer: mixer_test This same system showed /usr/lib/debug/usr/tests/lib/googletest/ files that I'd already cleaned out before doing the above list. The older list showed: Only in /usr/lib/debug/usr/tests/lib/googletest/gmock: = gmock_stress_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gmock_main: = gmock-actions_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gmock_main: = gmock-cardinalities_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gmock_main: = gmock-generated-actions_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gmock_main: = gmock-generated-function-mockers_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gmock_main: = gmock-generated-internal-utils_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gmock_main: = gmock-generated-matchers_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gmock_main: = gmock-internal-utils_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gmock_main: = gmock-matchers_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gmock_main: = gmock-more-actions_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gmock_main: = gmock-nice-strict_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gmock_main: = gmock-port_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gmock_main: = gmock-spec-builders_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gmock_main: = gmock_ex_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gmock_main: = gmock_link_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gmock_main: = gmock_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest: = googletest-param-test-test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest: = gtest-unittest-api_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest: = gtest_environment_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest: = gtest_no_test_unittest.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest: = gtest_premature_exit_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest: = gtest_repeat_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest: = gtest_stress_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest: = gtest_throw_on_failure_ex_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = googletest-death-test-test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = googletest-filepath-test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = googletest-linked-ptr-test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = googletest-listener-test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = googletest-message-test.debug diff: = /tmp/main-CA53-installed-from-scratch/usr/share/locale/nn_NO.ISO8859-1/LC_= MESSAGES: Too many levels of symbolic links diff: = /tmp/main-CA53-installed-from-scratch/usr/share/locale/nn_NO.ISO8859-15/LC= _MESSAGES: Too many levels of symbolic links diff: = /tmp/main-CA53-installed-from-scratch/usr/share/locale/sl_SI.ISO8859-2/LC_= MESSAGES: No such file or directory Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = googletest-options-test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = googletest-port-test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = googletest-printers-test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = googletest-test-part-test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = gtest-typed-test_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = gtest_main_unittest.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = gtest_pred_impl_unittest.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = gtest_prod_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = gtest_skip_in_environment_setup_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = gtest_skip_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = gtest_sole_header_test.debug Only in /usr/lib/debug/usr/tests/lib/googletest/gtest_main: = gtest_unittest.debug Similarly there was a block of /usr/share/examples/etc/ files that I'd already cleaned out (putting back what the new temporary install had afterwards). The older list showed: Only in /usr/share/examples/etc: apmd.conf Only in /usr/share/examples/etc: auto_master Only in /usr/share/examples/etc: blacklistd.conf Only in /usr/share/examples/etc: crontab Only in /usr/share/examples/etc: csh.cshrc Only in /usr/share/examples/etc: csh.login Only in /usr/share/examples/etc: csh.logout Only in /usr/share/examples/etc: ddb.conf Only in /usr/share/examples/etc/defaults: bluetooth.device.conf Only in /usr/share/examples/etc/defaults: devfs.rules Only in /usr/share/examples/etc/defaults: periodic.conf Only in /usr/share/examples/etc/defaults: rc.conf Only in /usr/share/examples/etc: devd.conf Only in /usr/share/examples/etc: devfs.conf Only in /usr/share/examples/etc: dhclient.conf Only in /usr/share/examples/etc: disktab Only in /usr/share/examples/etc: fbtab Only in /usr/share/examples/etc: freebsd-update.conf Only in /usr/share/examples/etc: ftpusers Only in /usr/share/examples/etc: gettytab Only in /usr/share/examples/etc: group Only in /usr/share/examples/etc: hosts Only in /usr/share/examples/etc: hosts.allow Only in /usr/share/examples/etc: hosts.equiv Only in /usr/share/examples/etc: hosts.lpd Only in /usr/share/examples/etc: inetd.conf Only in /usr/share/examples/etc: libalias.conf Only in /usr/share/examples/etc: libmap.conf Only in /usr/share/examples/etc: locate.rc Only in /usr/share/examples/etc: login.access Only in /usr/share/examples/etc: login.conf Only in /usr/share/examples/etc: mac.conf Only in /usr/share/examples/etc: mail.rc Only in /usr/share/examples/etc: motd Only in /usr/share/examples/etc: netconfig Only in /usr/share/examples/etc: netstart Only in /usr/share/examples/etc: network.subr Only in /usr/share/examples/etc: networks Only in /usr/share/examples/etc: newsyslog.conf Only in /usr/share/examples/etc: nscd.conf Only in /usr/share/examples/etc: nsmb.conf Only in /usr/share/examples/etc: nsswitch.conf Only in /usr/share/examples/etc: ntp.conf Only in /usr/share/examples/etc: opieaccess Only in /usr/share/examples/etc: pccard_ether Only in /usr/share/examples/etc: pf.os Only in /usr/share/examples/etc: phones Only in /usr/share/examples/etc: printcap Only in /usr/share/examples/etc: profile Only in /usr/share/examples/etc: protocols Only in /usr/share/examples/etc: rc Only in /usr/share/examples/etc: rc.bsdextended Only in /usr/share/examples/etc: rc.firewall Only in /usr/share/examples/etc: rc.initdiskless Only in /usr/share/examples/etc: rc.resume Only in /usr/share/examples/etc: rc.sendmail diff: /tmp/main-CA53-installed-from-scratch/usr/tests/local: No such = file or directory Only in /usr/share/examples/etc: rc.shutdown Only in /usr/share/examples/etc: rc.subr Only in /usr/share/examples/etc: rc.suspend Only in /usr/share/examples/etc: regdomain.xml Only in /usr/share/examples/etc: remote Only in /usr/share/examples/etc: rpc Only in /usr/share/examples/etc: services Only in /usr/share/examples/etc: shells Only in /usr/share/examples/etc: sysctl.conf Only in /usr/share/examples/etc: syslog.conf Only in /usr/share/examples/etc: termcap.small Only in /usr/share/examples/etc: ttys Only in /usr/share/examples/printing: README For reference, after copying over the new temporaries files to that cleaned out area: # find /usr/share/examples/etc/ -print /usr/share/examples/etc/ /usr/share/examples/etc/defaults /usr/share/examples/etc/README.examples /usr/share/examples/etc/bsd-style-copyright /usr/share/examples/etc/make.conf /usr/share/examples/etc/wpa_supplicant.conf =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Fri Jul 28 23:07: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 4RCNZr2nrSz4pjKG for ; Fri, 28 Jul 2023 23:07:48 +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 4RCNZq0TWlz3LpK; Fri, 28 Jul 2023 23:07:46 +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: 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 36SN7bo7026285; Sat, 29 Jul 2023 00:07:37 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 36SN7b7v026284; Sat, 29 Jul 2023 00:07:37 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202307282307.36SN7b7v026284@donotpassgo.dyslexicfish.net> Date: Sat, 29 Jul 2023 00:07:37 +0100 Organization: Dyslexic Fish To: freebsd-current@freebsd.org Cc: jamie@catflap.org, pstef@freebsd.org Subject: ps(1) bugs and problems 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]); Sat, 29 Jul 2023 00:07:37 +0100 (BST) X-Spamd-Result: default: False [-3.70 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[catflap.org,none]; R_SPF_ALLOW(-0.20)[+mx:dyslexicfish.net]; MIME_GOOD(-0.10)[text/plain]; RCVD_NO_TLS_LAST(0.10)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ARC_NA(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; BLOCKLISTDE_FAIL(0.00)[209.250.224.51:server fail,2001:19f0:7400:8808:123::1:server fail]; RCVD_COUNT_THREE(0.00)[3]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[jamie]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; HAS_ORG_HEADER(0.00)[]; TO_DN_NONE(0.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US] X-Rspamd-Queue-Id: 4RCNZq0TWlz3LpK X-Spamd-Bar: --- I have a program that produces a list of PIDS, that are supplied via '-p' to /bin/ps and are sorted with '-d'. After a late upgrade on a particular machine, I've just been bitten by the modifications to "ps" to unconditionaly add recurive descendancy PID lookups to the '-d' option when a pid is specified. There is nothing in the man pages or docs to suggest that this should be a thing, but there you go. Rather than just patch it out, Would a patch to allow the previous behaviour as an option (even if the option isn't default) be accepted? In addition, there is a bug in that ps now goes into a memory-sucking endless-loop if you do: ps -dp0 The manual page is no longer accurate either: '-d' says "Note that this option has no effect if the “command” column is not the last column displayed." That is no longer true, it doesn't matter what column is displayed last, if you use '-p', '-d' now completely changes the output title: ps: extend the non-standard option -d (tree view) to work with -p https://cgit.freebsd.org/src/commit/bin/ps/ps.c?id=ca8c0d5e811048ad67d0955642c5b486e9c0f3d2 author: Piotr Pawel Stefaniak 2020-05-07 16:56:18 +0000 commit: ca8c0d5e811048ad67d0955642c5b486e9c0f3d2 (patch) tree: 374be17aead18daf2e3c7477a4573f60ce62d8f0 /bin/ps/ps.c Cheers, Jamie From nobody Sat Jul 29 08:05:06 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 4RCcVz2fghz4qFFS for ; Sat, 29 Jul 2023 08:05:15 +0000 (UTC) (envelope-from bsd@orsolic.org) Received: from mail-4323.proton.ch (mail-4323.proton.ch [185.70.43.23]) (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 "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RCcVx0NTbz3hdt for ; Sat, 29 Jul 2023 08:05:12 +0000 (UTC) (envelope-from bsd@orsolic.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=orsolic.org header.s=protonmail header.b=o9itt2YD; spf=none (mx1.freebsd.org: domain of bsd@orsolic.org has no SPF policy when checking 185.70.43.23) smtp.mailfrom=bsd@orsolic.org; dmarc=pass (policy=none) header.from=orsolic.org Date: Sat, 29 Jul 2023 08:05:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orsolic.org; s=protonmail; t=1690617908; x=1690877108; bh=lfSGJeUUPqkl4AFRHh88KeYLG0108Wd87p5uOj24WxQ=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=o9itt2YDzOpEKl0u8fQEQs0GkuiObDmSuKMdlUQIhfQWYsW9NWdtE1TVWU77kxG0N NLGjEZ3aqKZ5d1xZiKR0WozQERlkQb8fVYgWQW5Kt5u5UOSB4+5QKG1H+D9Bdg0BkK ZSVBM8sIPnFX/nT60yxVDeJnnVkJELf27rWEmFVN2esPhp2Pd+ZNu5bKz8M9XtTUO7 fRnSsVPZLx1JBWfaJLg9SeLPp3Zk2JCxYWiq+uEpxIqNBwUk4GiF+r1VbNsXJUBG5f 03sL90RfYuvYTCA7WQUKnppHQJOdCvvTPoq+xdCWYWse9mGQgh6pHnFjMCPo+hvLM2 /tzGhdmKcgc6w== To: "freebsd-current@freebsd.org" From: Pero Orsolic Subject: CURRENT with ZFS not bootable when built with LLVM from ports Message-ID: Feedback-ID: 80848137:user:proton 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 [-4.20 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[orsolic.org,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[185.70.43.23:from]; R_DKIM_ALLOW(-0.20)[orsolic.org:s=protonmail]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+]; TO_DN_EQ_ADDR_ALL(0.00)[]; DKIM_TRACE(0.00)[orsolic.org:+]; RCPT_COUNT_ONE(0.00)[1]; FREEFALL_USER(0.00)[bsd]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4RCcVx0NTbz3hdt X-Spamd-Bar: ---- Building -CURRENT (2023-07-17 be4c7f273508) without system compiler (with L= LVM16 from ports) results in unbootable system:Preloaded elf kernel "/boot/= kernel/kernel" at 0xffffffff82328000. Preloaded elf obj module "/boot/kernel/zfs.ko" at 0xffffffff82329090. Preloaded boot_entropy_cache "/boot/entropy" at 0xffffffff823298f8. Preloaded elf obj module "/boot/kernel/cryptodev.ko" at 0xffffffff82329950. Preloaded hostuuid "/etc/hostid" at 0xffffffff8232a140. kldload: unexpected relocation type 42, symbol index 8662 link_elf_obj: symbol __stack_chk_guard undefined KLD file zfs.ko - could not finalize loading Patching and rebuilding LLVM16 with this patch results in bootable system: Patch was taken from: https://cgit.freebsd.org/src/commit/?h=3Dstable/13&id=3De8e5d75e6a9676e76c3= bfd6d1d52561ffbb40846 Few months ago it was possible to use LLVM from ports to build kernel and w= orld, but I don't remember the details. This patch was tested in bhyve VM and on real hardware. On real hardware it was possible to boot system without patched compiler wh= en zfs.ko (options ZFS and GEOM_ELI with devices crypto and cryptodev) is b= uilt into the kernel. But then other modules (acpi_ibm, iic, drm, i915kms, acpi_video, ... pf, va= rious ng_* and so on) will fail to load with same reason. Didn't try including zfs.ko into the kernel in the VM. Bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272740 From nobody Sat Jul 29 19:28:13 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 4RCvg14g6jz4qL8x for ; Sat, 29 Jul 2023 19:28:13 +0000 (UTC) (envelope-from pstef@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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 4RCvg148K3z3mMR; Sat, 29 Jul 2023 19:28:13 +0000 (UTC) (envelope-from pstef@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1690658893; 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=MhG+Rxm38hcS63DX3m9zVYnf1SWo3KHNB/Xjku6wJgk=; b=GblTOEDIxkAjbkWDXqsHw2dH7WRjOUEVE66Bu+imN1fI7RZfcxgmFhwycFVm2dZ/n8+caa m81zV5daI6oq3uFJP322ARNYmLf5Vchn0OesPqsGHaoKXsTei8JERvhBJMhnyVDzzc5Lrf Ct5XOSHwRYTdYqMADpeVSI+xyRN5+WwMotSnMRP0KGBneSUOjSHQE7x69grZYshuRqdIGW zh8n/innPeXb0jrIy+OBoOjL4uW/9ueHPnHrW12zX0vioVFmXaCYQo1fkgLtmjBhyHBYTQ PAjipcomfbK9TPUYkEQTPceetaOxnl0Wu90JI5OWejqwbjocqn/W9d8flYjaxw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1690658893; 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=MhG+Rxm38hcS63DX3m9zVYnf1SWo3KHNB/Xjku6wJgk=; b=LfDmYR8l7w5D+R3HDByR85KlbFJE3fy+crABSQ0QEq3SBiwe8p2PtUmQbTgqwUZLUr533+ sGjc60TtPdlMEd696md0q1cxLDkrIp7JpPBMXfr9tv0qH5oG4/mB+o2sT+CHhy390Z3Lk/ RoKR+5cXlW1d7CymoChkJv5ehvW0/NpTYTCRd3ZiJsFHOAConONip7XBEoxU+3KAJPOm47 rkGPKws7Pi/qOUxee3xv4keEuSfDqumRUdgpKgdf4wWboe8Uwhp7lpsihXkQ2cfwQAAmnX yxgs6NczNU3zyIklv+tSTpTI8rzZV8vIWG07629mSUiaKJYddL1liGa0dhSpOg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1690658893; a=rsa-sha256; cv=none; b=D9dQETkPBfEwjEki7WsVjPTuBltmXHM7gO16FcvcC8htfTixbqm6hF57qFwGMEJFQwQE+q yNScVuUGJ7YpwYQkg9SGZCgh2qbCAyVyie/p5PDELVERK64ZvfYVghLXSbKoKEq8URT1vT jGEp5qpBlv5gw+3GHpQpTaE8XcBhTfCDl5SQy1ESO4I4pmEMjChg/jl7E3S5OmlIHQqPqE ztjAkuyik9tnYTCZn+gnaIKRim3i8EliCS/LqUIo0mXN51Tj5+AO1o1gF11Q6LHVPj6oDa cpB4mXmne8bEk6pNnZvC2E6IlMURodDlXkBGCOhMbJPBkpK6LUwouEt6TPFZVg== Received: by freefall.freebsd.org (Postfix, from userid 1403) id 593C8BF76; Sat, 29 Jul 2023 19:28:13 +0000 (UTC) Date: Sat, 29 Jul 2023 19:28:13 +0000 From: "Piotr P. Stefaniak" To: Jamie Landeg-Jones Cc: freebsd-current@freebsd.org Subject: Re: ps(1) bugs and problems Message-ID: References: <202307282307.36SN7b7v026284@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=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <202307282307.36SN7b7v026284@donotpassgo.dyslexicfish.net> On 2023-07-29 00:07:37, Jamie Landeg-Jones wrote: >I have a program that produces a list of PIDS, that are supplied via '-p' >to /bin/ps and are sorted with '-d'. What language is it written in? What is the use case? >After a late upgrade on a particular machine, I've just been bitten >by the modifications to "ps" to unconditionaly add recurive descendancy >PID lookups to the '-d' option when a pid is specified. I understand that the behavioral change affected programs/scripts in a way that requires adjustment and I do try to limit that as much as possible. But this feature was a needed one and I thought it should "just work" when -d was combined with -p, as opposed to adding a new flag to the program. Now that you've corrected my thinking, I plan to revert that change and re-introduce the feature as a separate option, see https://reviews.freebsd.org/D41231 for review. >There is nothing in the man pages or docs to suggest that this should >be a thing, but there you go. I intend to revert the change so there's no plan to update this in the manual page. >Rather than just patch it out, Would a patch to allow the previous >behaviour as an option (even if the option isn't default) be accepted? Feel free to discuss D41231 or provide an other patch. >In addition, there is a bug in that ps now goes into a memory-sucking >endless-loop if you do: > >ps -dp0 Thanks for this report, it was an oversight of the corner case that the parent PID of the PID 0 is also 0. >The manual page is no longer accurate either: > >'-d' says "Note that this option has no effect if the “command” >column is not the last column displayed." > >That is no longer true, it doesn't matter what column is displayed last, >if you use '-p', '-d' now completely changes the output > >title: ps: extend the non-standard option -d (tree view) to work with -p >https://cgit.freebsd.org/src/commit/bin/ps/ps.c?id=ca8c0d5e811048ad67d0955642c5b486e9c0f3d2 > >author: Piotr Pawel Stefaniak 2020-05-07 16:56:18 +0000 >commit: ca8c0d5e811048ad67d0955642c5b486e9c0f3d2 (patch) >tree: 374be17aead18daf2e3c7477a4573f60ce62d8f0 /bin/ps/ps.c My plan is to revert that. Piotr