From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 1 20:45:12 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0EB5106566C; Tue, 1 Mar 2011 20:45:11 +0000 (UTC) (envelope-from jhelfman@experts-exchange.com) Received: from mail.experts-exchange.com (mail.experts-exchange.com [72.29.183.251]) by mx1.freebsd.org (Postfix) with ESMTP id BAED48FC0C; Tue, 1 Mar 2011 20:45:11 +0000 (UTC) Received: from mail.experts-exchange.com (localhost [127.0.0.1]) by mail.experts-exchange.com (Postfix) with ESMTP id 72C6F6F6058; Tue, 1 Mar 2011 12:45:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=e-e.com; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:message-id:subject:subject :from:from:date:date:received:received:received; s=ee; t= 1299012301; x=1300826701; bh=ZeI1N75w9XoXbhH0mI9/sA9RI5zXG9zDjeD r82E1KRM=; b=LSn7sMiAf/eyJIjv442isM7z1wKh13a7clw0xj17B1usdIoCN0X uOrSdhJI3BdpQHjx2qWWFCeOPwGwQICkomdOE3ajilSEbrj5Mcn5d54KxCD/DgiI Fx9Fm3NrpfVbJL2TakCOS9S8vHeGUwfba3BNXec/lm/zDA5OQwljyQtI= X-Virus-Scanned: amavisd-new at experts-exchange.com Received: from mail.experts-exchange.com ([127.0.0.1]) by mail.experts-exchange.com (mail.experts-exchange.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bINScBkccP14; Tue, 1 Mar 2011 12:45:01 -0800 (PST) Received: from experts-exchange.com (unknown [72.29.180.81]) by mail.experts-exchange.com (Postfix) with SMTP id 8F86D6F6059; Tue, 1 Mar 2011 12:44:45 -0800 (PST) Received: (nullmailer pid 52449 invoked by uid 1001); Tue, 01 Mar 2011 20:41:24 -0000 Date: Tue, 1 Mar 2011 12:41:24 -0800 From: Jason Helfman To: Carl Message-ID: <20110301204124.GD76063@eggman.experts-exchange.com> References: <4D6C78D3.5090803@telus.net> <198718A4-4A82-4FDB-A8F6-400F132A649E@gsoft.com.au> <201103010800.35666.jhb@freebsd.org> <4D6D50AC.701@telus.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <4D6D50AC.701@telus.net> X-Operating-System: FreeBSD 8.2-RELEASE X-Living-The-Dream: I love the SLO Life! User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-hackers@freebsd.org Subject: Re: listing all modules compiled into a kernel instance X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2011 20:45:12 -0000 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