Date: Fri, 16 Aug 2002 17:15:01 -0700 From: Mike Hogsett <hogsett@csl.sri.com> To: Darren Pilgrim <dmp@pantherdragon.org> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: When the world doesn't match the kernel, what won't work? Message-ID: <200208170015.g7H0F1NL000871@axp.csl.sri.com> In-Reply-To: Message from Darren Pilgrim <dmp@pantherdragon.org> of "Fri, 16 Aug 2002 17:10:42 PDT." <3D5D9482.6EB81946@pantherdragon.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Things like /usr/bin/top which read kernel variables is a good example of something that is going to break. Rather than a new kernel and old world why not do cd /usr/src make buildworld && \ make buildkernel KERNCONF=mykernelconf && \ make installworld && \ make installkernel KERNCONF=mykernelconf && \ reboot ... run mergemaster after the reboot Assuming all the makes suceeded the machine will reboot with a matching kernel and world. - Mike > After the pre-installworld reboot, and I have a system with a new kernel > and old userland, what won't be functional until I install the > new world? What breaks when the kernel version isn't that which the > userland was built for? I ask because I'm working on a way of doing > remote installworlds, and want to make use of scripts, but obviously > I can't use something that won't be functional. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200208170015.g7H0F1NL000871>