From owner-freebsd-questions@FreeBSD.ORG Wed Jul 4 08:45:15 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04DE0106566B for ; Wed, 4 Jul 2012 08:45:15 +0000 (UTC) (envelope-from mueller23@insightbb.com) Received: from mail.insightbb.com (smtp.insight.synacor.com [208.47.185.22]) by mx1.freebsd.org (Postfix) with ESMTP id BBD448FC12 for ; Wed, 4 Jul 2012 08:45:14 +0000 (UTC) X_CMAE_Category: 0,0 Undefined,Undefined X-CNFS-Analysis: v=1.1 cv=z5JnbuUV59w9XxpMO3Yhc9aVbWy8YmjdXuO1Tcff/LU= c=1 sm=0 a=nB4jEUsvz2gA:10 a=jLN7EqiLvroA:10 a=L05jEIKXaom6C7r9tscA:9 a=jKRid43F7UoA:10 a=Q/oqmR4JO1zR3vNQamCQeQ==:117 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Authentication-Results: smtp02.insight.synacor.com smtp.mail=mueller23@insightbb.com; spf=softfail; sender-id=softfail Authentication-Results: smtp02.insight.synacor.com header.from=mueller23@insightbb.com; sender-id=softfail Received-SPF: softfail (smtp02.insight.synacor.com: transitional domain insightbb.com does not designate 74.134.26.53 as permitted sender) Received: from [74.134.26.53] ([74.134.26.53:34105] helo=localhost) by mail.insightbb.com (envelope-from ) (ecelerity 2.2.2.40 r(29895/29896)) with ESMTP id 7C/EB-06836-8F104FF4; Wed, 04 Jul 2012 04:42:32 -0400 Date: Wed, 04 Jul 2012 04:42:32 -0400 Message-ID: <7C.EB.06836.8F104FF4@smtp02.insight.synacor.com> From: "Thomas Mueller" To: freebsd-questions@freebsd.org Cc: Polytropon , Jakub Lach Subject: Re: WITHOUT_MODULES in /etc/make.conf doesn't work X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2012 08:45:15 -0000 from Polytropon : > Yes, /etc/src.conf uses WITHOUT_* on a per-module basis, so you need > to explicitely name the modules not to build. > But you're right, there's only WITHOUT_USB (for not building the > USB-related parts), so going with kernel configuration would be > a good point to start -- the more precise you can define your > test setting and its variables, the better you can diagnose the > problem. > In /etc/make.conf, you could use MODULES_OVERRIDE to define the > set of modules you want (because only _those_ will then be > build) and keeping their functionality out of the kernel. In > this case, you have control over your test setting using the > modules. > The same files offers NO_MODULES=yes to avoid building modules > at all (use custom kernel instead). > If you decide to use WITHOUT_MODULES, you can define the set of > modules you want to avoid building, everything else will be > built. > > Would > > WITHOUT_MODULES= ulpt > > work better in /etc/src.conf than in /etc/make.conf ? > No, /etc/src.conf as (according to its manpage) a defined set of > variables that will be considered when building (or _not_ building) > certain modules. > > Besides the toxic (?) ulpt.ko, there are a lot of modules that > > would never be used on my hardware, and other modules that could > > be built in the kernel as non-modules (such as support for msdosfs > > and ext2fs, which I don't want to be without). > That's a good setting for using a custom kernel and not even > building the modules for the non-used functionalities. :-) I suppose modules save RAM by being loaded only when needed, but see the virtue of NO_MODULES=yes or MODULES_OVERRIDE in combination with putting everything needed in kernel config. Building WITHOUT_USB would cause a severe loss of functionality, USB sticks, USB hard drives, even USB mice and keyboards wouldn't work. from Jakub Lach : > Try with: > WITHOUT_MODULES= usb/ulpt I'll have to try that on my build/update of FreeBSD 9.0_STABLE i386 on USB stick. Thanks for the hint! This would be from the USB stick but with source base directory /STABLE1/usr/src (on hard drive). I had already built FreeBSD 9.0_STABLE i386 on the USB stick from FreeBSD 9.0_STABLE amd64, and was successful booting that USB stick. Sort of a dirty trick that you have to use usb/ulpt as opposed to ulpt, and a deficiency in the documentation. Now is there any way to prevent ulpt.ko from loading when a USB printer is connected? Tom