Date: Thu, 13 Jul 2000 17:22:35 +0200 (CEST) From: ripley@nostromo.in-berlin.de To: FreeBSD-gnats-submit@freebsd.org Subject: kern/19891: make buildkernel/installkernel installs only partly Message-ID: <200007131522.RAA31575@office.in-berlin.de>
next in thread | raw e-mail | index | archive | help
>Number: 19891 >Category: kern >Synopsis: make installkernel creates /GENERIC >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jul 13 08:30:00 PDT 2000 >Closed-Date: >Last-Modified: >Originator: H. Eckert >Release: FreeBSD 4.x-STABLE i386 >Organization: IN-Berlin e.V. >Environment: 4.0-RELEASE upgrading to -stable >Description: Upgraded 4.0-RELEASE system with the following commands: make update (runs cvsup) make buildworld make buildkernel make installkernel (this installs the kernel es /GENERIC !) shutdown (single user mode) make installworld mergemaster reboot On reboot the system paniced because the modules in /modules have been updated but the loaded kernel /kernel is still 4.0-R and thus incompatible with the new modules. (To be exact the kernel crashed after loading the linux compatibility). >How-To-Repeat: Upgrade 4.0-R system to 4.x stable, have no customized kernel but some kernel module activated on boot. >Fix: Use a customized kernel and before reboot do cd /sys/i386/conf config YOURKERNELNAME cd ../../compile/YOURKERNELNAME make depend all install This way you're sure to have a fresh kernel in sync with the installed modules. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007131522.RAA31575>