Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > muc.lists.freebsd.emulation > #12833
| From | bugzilla-noreply@freebsd.org |
|---|---|
| Newsgroups | muc.lists.freebsd.emulation |
| Subject | [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update |
| Date | 2026-02-03 21:35 +0000 |
| Organization | Newsgate at muc.de e.V. |
| Message-ID | <bug-291151-4077-30iKNqtBiP@https.bugs.freebsd.org/bugzilla/> (permalink) |
| References | <bug-291151-4077@https.bugs.freebsd.org/bugzilla/> |
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. -- Posted automagically by a mail2news gateway at muc.de e.V. Please direct questions, flames, donations, etc. to news-admin@muc.de
Back to muc.lists.freebsd.emulation | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE since latest freebsd-update bugzilla-noreply@freebsd.org - 2025-11-22 13:28 +0000 [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE since latest freebsd-update bugzilla-noreply@freebsd.org - 2025-12-05 23:41 +0000 [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE since latest freebsd-update bugzilla-noreply@freebsd.org - 2026-01-29 14:46 +0000 [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE since latest freebsd-update bugzilla-noreply@freebsd.org - 2026-02-01 01:53 +0000 [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update bugzilla-noreply@freebsd.org - 2026-02-03 13:22 +0000 [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update bugzilla-noreply@freebsd.org - 2026-02-03 13:27 +0000 [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update bugzilla-noreply@freebsd.org - 2026-02-03 15:46 +0000 [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update bugzilla-noreply@freebsd.org - 2026-02-03 21:35 +0000 [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update bugzilla-noreply@freebsd.org - 2026-02-03 22:24 +0000 [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update bugzilla-noreply@freebsd.org - 2026-02-03 23:51 +0000 [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update bugzilla-noreply@freebsd.org - 2026-02-04 00:28 +0000
csiph-web