Date: Tue, 19 Sep 2000 08:16:05 +0100 From: Roger Hardiman <roger@cs.strath.ac.uk> To: "Daniel C. Sobral" <dcs@newsguy.com> Cc: Roger Hardiman <roger@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/boot/forth loader.conf Message-ID: <39C712B4.19CD4FE1@cs.strath.ac.uk> References: <200009170723.AAA43421@freefall.freebsd.org> <39C65421.1138C451@newsguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Daniel C. Sobral" wrote: > > Roger Hardiman wrote: > > > > roger 2000/09/17 00:23:44 PDT > > > > Modified files: (Branch: RELENG_4) > > sys/boot/forth loader.conf > > Log: > > Place bktr_mem before bktr so the modules load in the correct order > > Huh? This shouldn't be necessary! First, nothing is run until the kernel > boots, and, by then, both modules have (or haven't) already been loaded. > Second, it should be handled by dependency if it's a dependency issue. Firstly dependencies do not work in -stable. I wish they did, but they do not. MODULE_DEPEND() is a dummy stub in -stable. An MFC is needed. And the load order is important. Before, you would get Sep 17 08:18:28 bfg /kernel: Preloaded elf module "bktr.ko" at 0xc03ea0ec. Sep 17 08:18:28 bfg /kernel: link_elf: symbol bktr_has_stored_addresses undefined and the bktr module would not load. I assumed the load order would actually be defined by the user's personal loader.conf, but regardless of what you put in there, the load order actually happens in the order it is defined by /boot/defaults/loader.conf. bktr needs functions in bktr_mem. So bktr_mem myst go before bktr in loader.conf. Roger -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://www.telepresence.strath.ac.uk 0141 548 2897 roger@cs.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39C712B4.19CD4FE1>