Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 20 Aug 2012 14:17:26 +0400
From: gremlin@...mlin.ru
To: owl-dev@...ts.openwall.com
Subject: Re: kernel.spec generated RPMs

On 19-Aug-2012 16:23:51 +0400, Vasiliy Kulikov wrote:

 > > kernel-modules-xxx (for xxx support),
 > > kernel-modules-yyy (for yyy support),
 > What are these xxx/yyy about? Does rpm identifies inter-modules
 > dependencies to write down RPM dependencies?

These "xxx" and "yyy" may be module groups - like deprecated "ide"
(found under CONFIG_IDE aka "ATA/ATAPI/MFM/RLL support" in the kernel
configuration, should be disabled or modularized in RH6-compatible
kernels, as they cause _lots_ of trouble with AHCI controllers), or
"snddev" (as Owl is a server platform, it's unlikely to work with
sound devices), or any other like ones you've mentioned below.

But even that may be non-trivial. Did you know that some modern boards
_do_ require the CONFIG_SND_HDA_INPUT_BEEP to just produce noise via
onboard PC speaker? For me, that was a really unpleasant surprise...

 > I think we can have one big rpm and move out rarely used modules -
 > multimedia, bluetooth, wireless, drm/gpu, isdn, atm, etc. I expect
 > the main rpm to have a half of the current size.

While frequently used modules (primarily modules for mass storage and
network devices support) should be compiled into the kernel (remember,
we're not limited by its' size anymore), the rarely used modules should
be really moved out - but if someone want one module, they should not
need install _all_ existing modules. That's why I suggest introducing
these "module groups" packages.


-- 
Alexey V. Vissarionov aka Gremlin from Kremlin
<gremlin ПРИ gremlin ТЧК ru>
GPG key ID: 0xEF3B1FA8, keyserver: hkp://subkeys.pgp.net
GPG key fingerprint: 8832 FE9F A791 F796 8AC9 6E4E 909D AC45 EF3B 1FA8

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.