Date: Wed, 14 Feb 2001 18:12:41 -0600 From: Mike Meyer <mwm@mired.org> To: "Andrey Simonenko" <simon@comsys.ntu-kpi.kiev.ua>, <bwatts@corp.netcom.ca> Cc: questions@freebsd.org Subject: Re: kernel.GENERIC Vs. kernel in / Message-ID: <14987.7929.818397.468677@guru.mired.org> In-Reply-To: <6146543@toto.iv>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrey Simonenko <simon@comsys.ntu-kpi.kiev.ua> types: > You can delete /kernel.GENERIC, but if you install new kernel and for the > same reson delete /kernel.old before new kernel checking and new kernel will > not work, you will have to find somewhere floppy disk with correct kernel to > bootstrap your system. It is better to have kernel.GENERIC and you should be > able to bootstrap your system with it, even if you install/deinstall some > hardware from your system,etc. Note that installing a kernel automatically moves /kernel to /kernel.old. So after you build one kernel and it fails, you'll have your old (good) kernel in /kernel.old, and a broken kernel in /kernel. If you then "fix" the kernel and make an install, you'll wind up with your broken kernel as /kernel.old, and your untested kernel as /kernel. If your fix didn't take, you're going to wish you'd left kernel.GENERIC around. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. 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?14987.7929.818397.468677>