Ubuntu
module-init-tools package

No mechanism for per-kernel configuration files during early boot

Bug #114803 reported by David Fox on 2007-05-15

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	module-init-tools	New	Undecided	Unassigned
	module-init-tools (Ubuntu)	Triaged	Wishlist	Unassigned

Bug Description

Binary package hint: module-init-tools

The modprobe configuration mechanism needs a way to provide configuration files that are only read for a particular kernel flavor, for example 2.6.20-15-lowlatency. It is possible to create a link in /etc/modprobe.d to a directory containing these configuration files, but it is not possible early in the boot when the file systems are still mounted read only. I propose a trivial solution: modifying modprobe so it tries the configuration directory /etc/modprobe.d-2.6.20-15-lowlatency before it tries /etc/modprobe.d.

Tags:

Revision history for this message

David Fox (david-fox) wrote on 2007-05-31:

I'm now using a udev rule to run a script that creates a link /dev/modprobe.d -> /etc/modprobe.d/arch/`uname -r`. By adding a link /etc/modprobe.d/running-kernel.d -> /dev/modprobe.d, this solves the problem pretty well. The advantage of putting the link in /dev is that /dev is the first writable directory created on the system, so the link is available very early during boot.

Scott James Remnant (Canonical) (canonical-scott) on 2009-03-09

Changed in module-init-tools:
importance:	Undecided → Wishlist
status:	New → Confirmed

Scott James Remnant (Canonical) (canonical-scott) on 2009-11-09

Changed in module-init-tools (Ubuntu):
status:	Confirmed → Triaged

Revision history for this message

Peter Hurley (phurley) wrote on 2010-03-22:

Among other uses, this will be handy to blacklist the old 1349 stack when using kernel versions > 2.6.33, but blacklist the new 1349 stack with < 2.6.33.

Revision history for this message

Peter Hurley (phurley) wrote on 2011-06-18: