Bug 9581 - Separate blacklists for different kernels
Summary: Separate blacklists for different kernels
Status: CLOSED WONTFIX
Alias: None
Product: Sisyphus
Classification: Development
Component: hotplug (show other bugs)
Version: unstable
Hardware: all Linux
: P2 enhancement
Assignee: Anton Farygin
QA Contact: qa-sisyphus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-17 00:33 MSD by Artem Delendik
Modified: 2007-08-13 13:51 MSD (History)
2 users (show)

See Also:


Attachments
separate blacklists (in addition to main blacklist) for hotplug-2004_09_23-alt17 (5.64 KB, patch)
2006-05-17 00:36 MSD, Artem Delendik
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Artem Delendik 2006-05-17 00:34:00 MSD
In some cases there are different sets of compiled-in kernel modules.
This patch allows to keep and use additional "blacklist" files for unique
kernels to keep the hotplug of trying to load nonexistent modules.
Differentiation based on `uname -a` information. "blacklist" files are stored in
`uname -a`-name-based directories in /etc/hotplug/blacklist.d . These
directories are automatically created by hotplug in case of their's absence at
first kernel boot.

I suppose this (or this kind of idea) will be useful for someone's use. :-)
Comment 1 Artem Delendik 2006-05-17 00:36:09 MSD
Created attachment 1491 [details]
separate blacklists (in addition to main blacklist) for hotplug-2004_09_23-alt17
Comment 2 Michael Shigorin 2007-08-13 13:50:50 MSD
I think this won't be fixed as hotplug is obsolete; back then, one could do that
with our custom modutils and if-clauses which were supported.  AFAIK these
aren't supported with module-init-tools; if the need arises again, please
consider looking at udev.