src/sys/boot/common/module.c, branch release/5.2.1

Use __FBSDID().

2003-08-25T23:30:41Z

Also some minor style cleanups.

FreeBSD 5.0 has stopped shipping /modules 2.5 years ago. Catch

2003-03-03T22:53:35Z

up with this further by excluding /modules from the (default) kern.module_path.

Bandaid for a buffer overrun in the module searching code. When breaking

2002-04-11T10:00:44Z

up the module_path string, we would walk one past the end of the buffer. This hurting ia64 originally, but it was probably also happening on i386 occasionally as well. The effects were usually harmless, it would add bogus "binary" search directories to the places it actually looked for files.

Fix a number of misspellings of "dependency" and "dependencies" in

2001-11-16T21:08:40Z

comments and function names. PR: kern/8589 Submitted by: Rajesh Vaidheeswarran

Implement the long-awaited module->file cache database. A userland

2001-09-11T01:09:24Z

tool (kldxref(8)) keeps a cache of what modules and versions are inside what .ko files. I have tested this on both Alpha and i386. Submitted by: bp

Fix a minor style bug in the last commit.

2001-06-10T11:15:37Z

Submitted by: Adrian Steinmann MFC after: 2 days

In sys/boot/common/module.c, near line 105 a request for a raw

2001-05-27T23:26:11Z

file is processed by passing its name in argv[1]: return(mod_loadobj(typestr, argv[1])); however, it is not tested to see if argv[1] actually is defined. At best, mod_loadobj() near line 244 returns an error like "can't find 'garbage'" but if the "filename" entered is sufficiently long, some buffer gets overrun. Of course, "load -t filename" is actually a typo because we meant to type "load -t mfs_root filename"; nevertheless, a hung machine seems like too harsh a punishment for such a small typo... PR: i386/27693 Submitted by: Adrian Steinmann MFC after: 1 week

The default search path for kernel and modules was bogus. It makes no

2000-09-16T19:59:41Z

sense for /boot/kernel to come last.

Fix autoboot. Now autoboot always show the correct kernel name. It

2000-09-08T16:47:05Z

gets the name from the environment variable kernelname, which is set when a kernel is loaded. For this reason, autoboot will _first_ try to load a kernel, and only proceed with the wait prompt after that succeeds. If it fails, it will abort immediately. While I understand some may think this behavior undesirable, I think it is, overall, the best thing to do, even if we do not consider the aesthetic issue. Notice that anyone using the default loader.rc already has the kernel loaded before autoboot. On unload, unset kernelname. Separate the code that tries to load a kernel from the list of options to the function loadakernel(). It is used by both boot() and autoboot().

The kernel is now known as `kernel.ko' and it and its matching modules

2000-09-05T22:37:46Z

live in ``/boot/kernel/''.