Date: Tue, 27 Feb 2007 08:31:10 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Joe Auty <joe@netmusician.org> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: kernel panic at boot on any 6.x OS *SOLVED!* Message-ID: <44y7mjg21t.fsf@Lowell-Desk.lan> In-Reply-To: <07E8C3BD-8764-488B-8CD7-D8A106D922C1@netmusician.org> (Joe Auty's message of "Tue\, 27 Feb 2007 01\:28\:07 -0500") References: <39E24107-964D-414C-95D1-5B1C376291E4@netmusician.org> <001001c759a6$438d5ed0$3c01a8c0@coolf89ea26645> <73B261EE-79C5-4773-B563-9D9FCA16B4C8@netmusician.org> <20070227043324.GX844@turion.vk2pj.dyndns.org> <07E8C3BD-8764-488B-8CD7-D8A106D922C1@netmusician.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Joe Auty <joe@netmusician.org> writes: > I guess the trick here was not considering that user space apps would > be trying to do a kldload, and that calling upon a module that is > either missing in /boot/kernel or /boot/modules or resides outside > of /boot can trigger these panics. That is because they are *not* user-space applications. They are kernel-space code. There is a "PORTS_MODULES" variable documented for make.conf(5) which is intended for just this problem. I haven't used it, though, and offhand I can't find the macro definition for it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44y7mjg21t.fsf>