Date: 20 Jul 2000 01:26:55 +0200 From: Cyrille Lefevre <lefevre@citeweb.net> To: Marcel Moolenaar <marcel@cup.hp.com> Cc: Mike Smith <msmith@FreeBSD.ORG>, arch@FreeBSD.ORG Subject: Re: Multiple kernels / module search path Message-ID: <zondya4g.fsf@pc166.gits.fr> In-Reply-To: Marcel Moolenaar's message of "Tue, 18 Jul 2000 14:24:33 -0700" References: <200007182113.OAA18973@mass.osd.bsdi.com> <3974CB11.388FE532@cup.hp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Marcel Moolenaar <marcel@cup.hp.com> writes:
> Mike Smith wrote:
> >
> > > The problem is with versioning. If I add 3rd party module foo.ko to
> > > modules, while it actually is a module for kernel 'kernel.bar' *and*
> > > kernel and kernel.bar are sufficiently incompatible, then kernel won't
> > > boot (for example) if the module is loaded at boot time.
> > >
> > > Or, if kernel.bar is booted and I want to load foo.ko, I might pick up
> > > the version from /modules if I don't happen to have a foo.ko in
> > > /modules.bar, which may be sufficiently incompatible and cause a kernel
> > > panic.
> >
> > This has already been discussed to death, and consensus has been as
> > follows:
> [snip]
>
> Ok, I'll make {build|install}kernel behave the same as the traditional
> way only and not add the ability to install multiple kernels. We can
> always revisit these targets when the improved infrastructure is in
> place.
there is one thing I don't understand in this thread.
you are saying than modules are different from kernel to kernel.
I suppose this is true if you build modules as part of world (the
old way) and not as part of the kernel. where, if the src tree
as been updated between the workd and the kernel. I'm right ?
if you build the world and the kernel in the same time, even if
you have multiple kernels (read your own and GENERIC), it should
not be a problem to have one and only one module directory.
do you understand what I mean ? and what I understand is that
the building of modules as part of the kernel and not of the world
is to avoid conflicts if the src tree has been updated.
IMHO, to left the root directory clean, it would be better to
create /modules/WHATEVER subdirectories than /modules.WHATEVER.
the idea to have kernel.ko in /modules/WHATEVER is interresting.
what is the problem about to have /:/boot:/modules/WHATEVER:/modules
as the modules search path ? another problem is to say to the boot
loader which kernel to load. what about loader_conf_files=" \
/boot/boot.conf /boot/loader.conf /boot/loader.conf.local" where
boot.conf just contain kernel="/modules/WHATEVER/kernel" which is
updated a kernel installation ?
Cyrille.
--
home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?zondya4g.fsf>