Date: Mon, 31 Jul 2017 23:38:51 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 221050] emulators/virtualbox-ose: Bridged network doesn't work (11.1-RELEASE) Message-ID: <bug-221050-8075-SBp05Mi0N0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221050-8075@https.bugs.freebsd.org/bugzilla/> References: <bug-221050-8075@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221050 rkoberman@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rkoberman@gmail.com --- Comment #14 from rkoberman@gmail.com --- (In reply to John Hood from comment #13) Just to clarify for people, while developers try to not adjust the KBI with= in a major release, it has never been a commitment. The bottom line is that all kernel modules from ports should be re-built ev= ery time the kernel is updated. For those running releases, this is for every release as well as security patches which involve a kernel replacement whet= her by a re-build or freebsd-update. For those of us running stable, it is every time the kernel is updated. While lsof does not involve a kernel module, it does poke around in the ker= nel and will break far more easily with kernel changes than modules as it does = its poking outside the documented KBI. If you build kernels from source, you can list ports needing updating in /etc/src.conf like this: PORTS_MODULES=3Demulators/virtualbox-ose-kmod sysutils/lsof If you install packages you need to wait until a package build has been completed after a release. This is usually two or three days, but I have se= en it take as long as a week. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221050-8075-SBp05Mi0N0>