13 messages in org.freebsd.freebsd-archRe: Multiple kernels / module search ...| From | Sent On | Attachments |
|---|---|---|
| Marcel Moolenaar | Jul 17, 2000 10:09 pm | |
| Brooks Davis | Jul 17, 2000 11:03 pm | |
| Sheldon Hearn | Jul 18, 2000 6:11 am | |
| Marcel Moolenaar | Jul 18, 2000 9:20 am | |
| Marcel Moolenaar | Jul 18, 2000 9:32 am | |
| Mike Smith | Jul 18, 2000 2:13 pm | |
| Marcel Moolenaar | Jul 18, 2000 2:24 pm | |
| Warner Losh | Jul 18, 2000 8:26 pm | |
| Warner Losh | Jul 18, 2000 8:28 pm | |
| Brooks Davis | Jul 18, 2000 8:55 pm | |
| Cyrille Lefevre | Jul 19, 2000 4:26 pm | |
| Marcel Moolenaar | Jul 19, 2000 4:41 pm | |
| Cyrille Lefevre | Jul 19, 2000 8:51 pm |
| Subject: | Re: Multiple kernels / module search path | |
|---|---|---|
| From: | Marcel Moolenaar (mar...@cup.hp.com) | |
| Date: | Jul 18, 2000 9:32:05 am | |
| List: | org.freebsd.freebsd-arch | |
Sheldon Hearn wrote:
On Mon, 17 Jul 2000 22:09:44 MST, Marcel Moolenaar wrote:
Question 3: Should we change the order in which modules are searched to /modules{.NAME}:/boot:/, where {.NAME} denotes the optional name suffix.
I really don't think that this is the way to go. A module should be a module should be a module. That's certainly where we're headed, right?
Building the modules as part of the kernel seems like a step away from it, because if modules are modules are modules, we could build them as part of world as we used to do and avoid building and rebuilding modules with every kernel we're building. But building modules as part of the world resulted in kernel and modules to be out of sync. We all know what that means :-)
We currently don't have the interfaces to make that happen (modules being modules that is). This implies that different installed kernels can not always share the same /modules directory. This is especially true during an upgrade, when the new kernel will be version V.x and the old kernel will be version (V-1).y. If we don't have a seperate /modules directory for the old kernel, we still have the "out-of-sync" problem.
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message