Date: Tue, 03 Feb 2026 21:35:20 +0000 From: bugzilla-noreply@freebsd.org To: emulation@FreeBSD.org Subject: [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update Message-ID: <bug-291151-4077-30iKNqtBiP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-291151-4077@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291151 --- Comment #6 from Jason W. Bacon <jwb@freebsd.org> --- (In reply to Alex S from comment #5) That's possible. Generally I would notice if one of the normal three linux mounts was missing, especially over such a long period and multiple reboots, but there's a chance I overlooked it. /dev/nda0p2 226G 46G 162G 22% / devfs 1.0K 0B 1.0K 0% /dev /dev/nda0p1 260M 1.3M 259M 1% /boot/efi fdescfs 1.0K 0B 1.0K 0% /dev/fd procfs 8.0K 0B 8.0K 0% /proc map -hosts 0B 0B 0B 100% /net linprocfs 8.0K 0B 8.0K 0% /compat/linux/proc tmpfs 7.1G 4.0K 7.1G 0% /compat/linux/dev/shm linsysfs 8.0K 0B 8.0K 0% /compat/linux/sys I'll see if I can reproduce the issue and keep an eye on the mounts. In any case, we'll need to figure out how freebsd-update broke it. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-291151-4077-30iKNqtBiP>