Bug 21405

Summary:

Default module patch mismatch between kernel and loader(8)

Product:

Base System

Reporter:

Makoto Matsushita <matusita>

Component:

kern

Assignee:

dd <dd>

Status:

Closed FIXED

Severity:

Affects Only Me

Priority:

Normal

Version:

5.0-CURRENT

Hardware:

Any

OS:

Any

Attachments:

Description	Flags
file.diff	none

Description Makoto Matsushita 2000-09-20 03:40:01 UTC

	Default module path of loader(8) is changed a few days before,
	however, module path of kernel (shown as 'kern.module_path' MIB)
	is not changed yet.

	This should cause a problem, if a user upgrades their old
	-current box to the latest, and forget to remove /modules
	directory.

	Typical example is 'mfs' module. If a kernel does not have MFS
	feature, kernel try to load a mfs.ko module (this is easily
	happen if your /etc/fstab has 'mfs' entry). However, if
	/modules/mfs.ko exists, it is used instead of /boot/kernel/mfs.ko.

Fix: Change default module_path, to sync with src/sys/boot/loader.conf.
How-To-Repeat: 
	(Left old /modules/*.ko, then)
	kldload your_favorite_module_name

Comment 1 Makoto Matsushita 2000-09-27 05:23:38 UTC

Here is a status of this PR.

* Just submitted, no one checked.

* There are yet another way of thinking. If you want to install a *new*
  version of kernel module which is also available by FreeBSD itself,
  /boot/modules should be listed *before* of /boot/kernel. So, maybe
  current kernel implementation is not wrong, and loader.conf needs
  modification.

Anyway, is there anybody to analyse this PR ?

-- -
Makoto `MAR' MATSUSHITA

Comment 2 dd freebsd_committer

2001-07-22 16:48:09 UTC

Responsible Changed
From-To: freebsd-bugs->dd

I'll take a look at this.

Comment 3 dd freebsd_committer

2001-08-20 02:12:44 UTC

State Changed
From-To: open->closed

Patch applied, thanks!