Date: Mon, 27 Jun 2016 23:58:14 -0600 From: Warner Losh <imp@bsdimp.com> To: Jakub Lach <jakub_lach@mailplus.pl> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: What are current dependencies of cd9660 kernel module? Message-ID: <CANCZdfqzV7DC34rGT7QxLbgqM%2BA_ZdVKBQcveQNqUieo89mOkg@mail.gmail.com> In-Reply-To: <1467092336283-6109948.post@n5.nabble.com> References: <1467053628941-6109797.post@n5.nabble.com> <CAN6yY1tY8ygn5hMtYX36OzJfry_Nv%2BQ7gCku4TjA5O5FwJKz8g@mail.gmail.com> <1467056804437-6109817.post@n5.nabble.com> <1467067188002-6109896.post@n5.nabble.com> <1467092336283-6109948.post@n5.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 27, 2016 at 11:38 PM, Jakub Lach <jakub_lach@mailplus.pl> wrote: > Hello again, > > After a rebuild (so also powercycling), I've loaded the module just fine. > I wonder what state the system was before, but now works. The usual cause of this is updating the kernel w/o updating modules. Or you did an installkernel w/o a reboot. The cd9660 module only depends n the kernel version because all modules depend on that to guard against such foot shooting. Chances are good a simple reboot would have fixed this. There's some anti-footshooting code to load it from kernel.old, but I've not tested that in years, so maybe it's no longer working (or you did multiple installkernels. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqzV7DC34rGT7QxLbgqM%2BA_ZdVKBQcveQNqUieo89mOkg>