From nobody Mon Nov 07 10:51:11 2022 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 4N5ShQ4RpZz4gfQ7 for ; Mon, 7 Nov 2022 10:51:18 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 4N5ShN68nyz4KKQ; Mon, 7 Nov 2022 10:51:15 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from kalamity.joker.local (123-1-88-210.area1b.commufa.jp [123.1.88.210]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 2A7ApBkc005769; Mon, 7 Nov 2022 19:51:12 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Mon, 7 Nov 2022 19:51:11 +0900 From: Tomoaki AOKI To: Graham Perrin Cc: freebsd-current@freebsd.org Subject: Re: linsysfs on /usr/src/sys (linsysfs, local) Message-Id: <20221107195111.78a575dc7769531e040dbcb4@dec.sakura.ne.jp> In-Reply-To: <8e3e8a1f-495e-6c53-7450-5e22e6b50025@freebsd.org> References: <3e925370-3f09-101d-e4f3-5fa2c7f28c83@freebsd.org> <8e3e8a1f-495e-6c53-7450-5e22e6b50025@freebsd.org> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) 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-Rspamd-Queue-Id: 4N5ShN68nyz4KKQ X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp X-Spamd-Result: default: False [-1.60 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_DKIM_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_LAST(0.00)[]; HAS_ORG_HEADER(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[sakura.ne.jp]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Mon, 7 Nov 2022 03:03:25 +0000 Graham Perrin wrote: > On 29/10/2022 21:30, Graham Perrin wrote: > > > Subject: poudriere jail update from source: syscall.mk does not exist > > > After updating to yesterday's > > aba921bd9e1869dae9ae4cc6e0c048f997401034, I aimed for a routine update > > of the jail that I used for poudriere. > > > > > > poudriere jail -u -J 1 -j main > > … > > ===> lib/libc (install) > > make[5]: "/usr/src/lib/libc/sys/Makefile.inc" line 9: Cannot open > > /usr/src/sys/sys/syscall.mk > > make[5]: Fatal errors encountered -- cannot continue > > make[5]: stopped in /usr/src/lib/libc > > *** Error code 1 > > … > > > bdrewery and others in IRC helped me to realise an offending mount. > > > With linux_enable: YES, > > root@mowa219-gjp4-8570p-freebsd:~ # mount | grep sys > linsysfs on /usr/src/sys (linsysfs, local) > root@mowa219-gjp4-8570p-freebsd:~ # exit > logout > % grep linsysfs /etc/fstab > # linsysfs      /compat/linux/sys       linsysfs > rw                         0     0 > # linsysfs        /compat/ubuntu/sys      linsysfs > rw,late                    0     0 > % > > > After linux_enable: NO and a reboot, > > % sysrc -f /etc/rc.conf linux_enable > linux_enable: NO > % mount | grep sys > % date ; uname -aKU > Wed 2 Nov 2022 19:06:01 GMT > FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #24 > main-n258900-aba921bd9e18: Sat Oct 29 14:39:59 BST 2022 > grahamperrin@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG > amd64 1400073 1400073 > % sudo service linux onestart > grahamperrin's password: > kldload: an error occurred while loading module linux. Please check > dmesg(8) for more details. > /etc/rc.d/linux: WARNING: Unable to load kernel module linux > kldload: an error occurred while loading module linux64. Please check > dmesg(8) for more details. > /etc/rc.d/linux: WARNING: Unable to load kernel module linux64 > % mount | grep sys > linsysfs on /compat/linux/sys (linsysfs, local) > % sudo sysrc linux_enable="YES" > linux_enable: NO -> YES > % > > > With linux_enable: YES (re-enabled) and a reboot, the clobber of > /usr/src/sys recurred. Possibly because there is a symlink /sys pointing to /usr/sys? The symlink is there historically, but already doesn't appear on `man hier` or /etc/mtree/. I finally found the revision 2878 at Mon Sep 19 01:40:40 1994 UTC [1] stopped creating the symlink automatically using /etc/mtree/. If the installation is old, kept-on-updating one, it would be time to delete the symlink. [1] https://cgit.freebsd.org/src/commit/etc/mtree/BSD.root.dist?id=c27b58e1b62e792e35a27bc5fd261e04293b076e > > ---- > > Resolved through an OS update on 3rd November: > > % uname -aKU > FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #25 > main-n259004-2c10be9e06d4: Thu Nov  3 00:14:52 GMT 2022 > grahamperrin@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG > amd64 1400073 1400073 > -- Tomoaki AOKI