Date: Tue, 1 Mar 2011 12:41:24 -0800 From: Jason Helfman <jhelfman@e-e.com> To: Carl <k0802647@telus.net> Cc: freebsd-hackers@freebsd.org Subject: Re: listing all modules compiled into a kernel instance Message-ID: <20110301204124.GD76063@eggman.experts-exchange.com> In-Reply-To: <4D6D50AC.701@telus.net> References: <4D6C78D3.5090803@telus.net> <198718A4-4A82-4FDB-A8F6-400F132A649E@gsoft.com.au> <201103010800.35666.jhb@freebsd.org> <4D6D50AC.701@telus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 01, 2011 at 12:01:48PM -0800, Carl thus spake: >On 2011-03-01 3:20 AM, Maxim Khitrov wrote: >> kldstat provides information about components that were loaded >> dynamically. If your kernel was built with INCLUDE_CONFIG_FILE option >> (enabled by default in GENERIC), then you can see the static >> components using: >> >> config -x /boot/kernel/kernel > >As has been shown though, "kldstat -v" actually does show static >components, at least those declared with DRIVER_MODULE(), and "config >-x" does not improve on the situation at all because components like >ucom were not cited in the configuration file. IMHO, there needs to be a >reliable way to query an existing kernel that yields a _complete_ list >of which components are actually included. > >On 2011-03-01 5:00 AM, John Baldwin wrote: >>> Maybe ucom doesn't appear because it doesn't have a DRIVER_MODULE() >>> declaration (because it isn't a driver). >> >> Yes, that would explain it. > >I can explicitly include ucom in a kernel by adding "device ucom" in the >configuration file, in which case it would call DRIVER_MODULE(), right? >That would then make it appear in the "kldstat -v" list? So why is it a >driver when it's done explicitly, but not a driver when done implicitly? >That makes no sense to me since the functionality doesn't change. IMHO, >this is a bug that needs to be fixed, not just for ucom but any >implicitly included driver. > >Who should submit a bug report? There was a documentation bug that was put in regarding the ucom device, and it was to update the device name in the documentation. http://www.freebsd.org/cgi/query-pr.cgi?pr=155074 I don't know if a PR is still required, but this may be worth a look first. > >Carl / K0802647 -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110301204124.GD76063>