From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [66.249.92.175] (helo=ug-out-1314.google.com) by linuxtogo.org with esmtp (Exim 4.67) (envelope-from ) id 1ID5sX-0006XZ-F5 for openembedded-devel@lists.openembedded.org; Mon, 23 Jul 2007 23:55:45 +0200 Received: by ug-out-1314.google.com with SMTP id i24so40027ugd for ; Mon, 23 Jul 2007 14:54:40 -0700 (PDT) Received: by 10.66.225.1 with SMTP id x1mr140193ugg.1185227680481; Mon, 23 Jul 2007 14:54:40 -0700 (PDT) Received: from ?192.168.20.110? ( [77.122.179.115]) by mx.google.com with ESMTPS id z40sm13176755ikz.2007.07.23.14.54.39 (version=SSLv3 cipher=OTHER); Mon, 23 Jul 2007 14:54:39 -0700 (PDT) Date: Tue, 24 Jul 2007 00:54:33 +0300 From: Paul Sokolovsky X-Mailer: The Bat! (v3.64.01 Christmas Edition) UNREG / CD5BF9353B3B7091 X-Priority: 3 (Normal) Message-ID: <86855446.20070724005433@gmail.com> To: openembedded-devel@lists.openembedded.org In-Reply-To: <77326513.20070720105101@gmail.com> References: <77326513.20070720105101@gmail.com> MIME-Version: 1.0 Subject: Re: [RFC] Revamp module handling in OE X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2007 21:55:48 -0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello OpenEmbedded, Friday, July 20, 2007, 10:51:01 AM, you wrote: > Hello openembedded-devel, > We have few issues with kernel module handling in OE which I'd like > to bring to attention and discuss ways to resolve. > 1. Module config option handling was not upgraded since 2.4. > This is known issue, it surfaced several times already, and we > discussed ways to solve it with Graeme Gregory on IRC recently. The > issue is that OE currently writes module config options where 2.4 > modutils expect them (/etc/modutils/*.conf), not where 2.6 > module-init-tools do (/etc/modprobe.d/*.conf). The patch is at > http://bugs.openembedded.org/show_bug.cgi?id=2669 I got confirmation from Graeme that it works ok, so I'd like to commit this tomorrow night. > 2. Location of module autoload config. > Module autoload is rather different feature. It actually never was > part of modutils/module-init-tools, but is done via adhoc scripts per > some distro's convention. Relatively randomly OE uses the same > /etc/modutils dir to store that info (just in files w/o extension). > Per-module data is then collated into /etc/modules file, and *that* > file is Debian convention. But AFAICT, that file is supposed to > contain local user's selection of autoload modules, whereas OE > automatically overwrites it. Of course, this information rather be > checked by people with more Debian background. Either way, at least > following issues can be identified: > 1. Location of per-module autoload data: /etc/modutils/ is rather > confusing place for this, especially if we switch to 2.6 way. > 2. /etc/modules is supposedly a user file. > One of the possible solutions: if a file is named /etc/modules, then > it's natural to name dir /etc/modules.d/ . If data from it would need > to be collated, that would go to some /etc/modules.foo, leaving > /etc/modules intact. FInally, both contents of files and dri would be > taken into account. I hope that people are fully back from GUADEC now and can give this some thought ;-). > Thoughts? -- Best regards, Paul mailto:pmiscml@gmail.com