From owner-freebsd-questions@FreeBSD.ORG Mon May 9 21:11:48 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA2B816A4EA for ; Mon, 9 May 2005 21:11:48 +0000 (GMT) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id A20CA43D2D for ; Mon, 9 May 2005 21:11:48 +0000 (GMT) (envelope-from cliftonr@lava.net) Received: by malasada.lava.net (Postfix, from userid 102) id 1615F153882; Mon, 9 May 2005 11:11:48 -1000 (HST) Date: Mon, 9 May 2005 11:11:47 -1000 From: Clifton Royston To: Brent Message-ID: <20050509211147.GF2626@tikitechnologies.com> References: <20050509134413.M37350@bmyster.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050509134413.M37350@bmyster.com> User-Agent: Mutt/1.4.2i cc: questions@freebsd.org Subject: Re: revert to old kernel help ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2005 21:11:49 -0000 On Mon, May 09, 2005 at 09:50:52AM -0400, Brent wrote: > Hello, im running Freebsd 4.10 , When i first setup this box i re-compiled > the kernel for firewalling and such...which worked great ...i then tried to > tighten the box down even further...by compileing ICMP_BANDLIM which caused > problems for my webserver. Anywho ...is there a way i can tell my Freebsd box > when it power cycles to boot the old kernel automatically ? At this point im > having to tell it manually to load kernel.old > > any help is greatly appreciated Your last previous kernel and module set should normally be saved as the file /kernel.old and the directory /modules.old/ on your root file system. If you haven't gone through multiple build cycles, you can do this, or the equivalent steps: # cd / # ln kernel kernel.bad && mv kernel.old kernel # mv modules modules.bad && mv modules.old modules Then reboot: # shutdown -r now 'Reboot into restored kernel' If you went through multiple build cycles with the new parameters, then you're torqued; you'll need to go through a fresh build cycle with a corrected kernel config. This is why it's a good idea to back up a known good copy of your kernel and modules before you start tinkering. Doesn't hurt to always keep a GENERIC kernel around too. -- Clifton -- Clifton Royston -- cliftonr@tikitechnologies.com Tiki Technologies Lead Programmer/Software Architect "I'm gonna tell my son to grow up pretty as the grass is green And whip-smart as the English Channel's wide..." -- 'Whip-Smart', Liz Phair