Date: Fri, 7 Jul 2000 23:22:12 -0700 From: Alfred Perlstein <bright@wintelcom.net> To: Greg Rumple <grumple@zaphon.llamas.net> Cc: R Joseph Wright <rjoseph@mammalia.org>, freebsd-stable@FreeBSD.org Subject: Re: 4.0-STABLE question (aka, now I did it) Message-ID: <20000707232212.X25571@fw.wintelcom.net> In-Reply-To: <20000707231652.B630@zaphon.llamas.net>; from grumple@zaphon.llamas.net on Fri, Jul 07, 2000 at 11:16:52PM -0700 References: <20000707212514.W630@zaphon.llamas.net> <20000707213246.V25571@fw.wintelcom.net> <20000707215852.A11695@manatee.mammalia.org> <20000707231652.B630@zaphon.llamas.net>
next in thread | previous in thread | raw e-mail | index | archive | help
* Greg Rumple <grumple@zaphon.llamas.net> [000707 23:16] wrote: > * R Joseph Wright (rjoseph@mammalia.org) [000708 04:59]: > > On Fri, Jul 07, 2000 at 09:32:46PM -0700, Alfred Perlstein wrote: > > > * Greg Rumple <grumple@zaphon.llamas.net> [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* > > Actually this is kind of what I did, and this did not work. I had to > truly boot BLAH for the kernel modules to work. WEIRD.. Not 'weird', this is to be expected, the bootloader is looking for a file called /kernel, you have to tell it to look for some other name. Just be glad you don't have to recompile your bootloader each time you upgrade your kernel... :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000707232212.X25571>