From owner-freebsd-stable Fri Jul 7 21:58:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from manatee.mammalia.org (manatee.mammalia.org [216.231.50.6]) by hub.freebsd.org (Postfix) with ESMTP id DCA6A37B9DB for ; Fri, 7 Jul 2000 21:58:53 -0700 (PDT) (envelope-from rjoseph@mammalia.org) Received: by manatee.mammalia.org (Postfix, from userid 1000) id 059A111CE08; Fri, 7 Jul 2000 21:58:53 -0700 (PDT) Date: Fri, 7 Jul 2000 21:58:52 -0700 From: R Joseph Wright To: Alfred Perlstein Cc: freebsd-stable@FreeBSD.org Subject: Re: 4.0-STABLE question (aka, now I did it) Message-ID: <20000707215852.A11695@manatee.mammalia.org> References: <20000707212514.W630@zaphon.llamas.net> <20000707213246.V25571@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000707213246.V25571@fw.wintelcom.net>; from bright@wintelcom.net on Fri, Jul 07, 2000 at 09:32:46PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 07, 2000 at 09:32:46PM -0700, Alfred Perlstein wrote: > * Greg Rumple [000707 21:27] wrote: > > Well after seeing all the discussion on using make buildkernel > > KERNEL=BLAH I decided I would try it too. :-) Just to see what it > > does. Lo and behold, it builds my kernel. I than even did a make > > installkernel KERNEL=BLAH (which actually installs my kernel as /BLAH > > instead of /kernel). I even managed to boot it, and my system comes up > > to the point of loading the linux kernel module for linux binary > > compatibility and than it reboots. This went on for like 4 hours before > > I walked back in to see what was going on. So it appears that there is > > something quite different here than just doing a standard kernel > > install, it also rebuilds and installs all the kernel modules. > > > > So is the linux.ko kernel module really broken? > > Are you sure you're actually booting your new kernel? It would seem > that unless you modified the files in /boot to load your new kernel > that you're old one would run and try to load the newer linux module > and then blow up. Why would you have to modify the files in /boot? Last time I did it, doing installkernel KERNEL=BLAH would only put BLAH in the / directory. You still have to do # chflags noschg kernel BLAH # mv kernel kernel.old # mv BLAH kernel # chflags schg kernel* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message