From owner-freebsd-arch Wed Jul 19 20:51:42 2000 Delivered-To: freebsd-arch@freebsd.org Received: from racine.cybercable.fr (racine.cybercable.fr [212.198.0.201]) by hub.freebsd.org (Postfix) with SMTP id 436B437B6A3 for ; Wed, 19 Jul 2000 20:51:37 -0700 (PDT) (envelope-from root@gits.dyndns.org) Received: (qmail 1766040 invoked from network); 20 Jul 2000 03:51:35 -0000 Received: from r224m65.cybercable.tm.fr (HELO gits.dyndns.org) ([195.132.224.65]) (envelope-sender ) by racine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 20 Jul 2000 03:51:35 -0000 Received: (from root@localhost) by gits.dyndns.org (8.9.3/8.9.3) id FAA71019; Thu, 20 Jul 2000 05:51:35 +0200 (CEST) (envelope-from root) From: Cyrille Lefevre Posted-Date: Thu, 20 Jul 2000 05:51:35 +0200 (CEST) Message-Id: <200007200351.FAA71019@gits.dyndns.org> Subject: Re: Multiple kernels / module search path In-Reply-To: <39763CB9.89DFA18C@cup.hp.com> "from Marcel Moolenaar at Jul 19, 2000 04:41:45 pm" To: Marcel Moolenaar Date: Thu, 20 Jul 2000 05:51:35 +0200 (CEST) Cc: arch@FreeBSD.ORG Reply-To: clefevre@citeweb.net Organization: ACME X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marcel Moolenaar wrote: > Cyrille Lefevre wrote: > > > > there is one thing I don't understand in this thread. > > you are saying than modules are different from kernel to kernel. > > Kernels and their modules can be completely different. Take for example > an upgrade from 4-stable to 5-current. I'm not right w/ you. when you do an upgrade, you build the world, then the kernel (using buildkernel). so, all is in sync, no ? > > 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. > > It's to avoid conflicts between a kernel and its modules. Not between 2 > different kernels and their modules. ok, that's what I understood until now :) so, for instance, the buildkernel target could be modified to build modules only for the first kernel, not for the others. do you see what I mean ? if I said KERNEL="WHATEVER GENERIC" in /etc/make.conf, modules are build twince and it's a lost of time :( > > what is the problem about to have /:/boot:/modules/WHATEVER:/modules > > as the modules search path ? > > Interference. > > I guess we'll discuss all these issues when the new infrastructure is > being deployed, if it needs any more discussing, of course. There's no > point in discussing this any further here, because we're not going to > worry about multiple kernels now. humm! I always keep a GENERIC kernel in sync, just in case... that's why I build more than one kernel. FYI, yesterday, in -stable, I post a Super-Makefile to cvsup/(update)/\ build/install everything from one point. I use it for month w/o any problems. it's a little bit complicated, but I have no choice. see you. 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