From owner-freebsd-current@FreeBSD.ORG Thu Jul 15 11:57:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 744A916A4CE for ; Thu, 15 Jul 2004 11:57:40 +0000 (GMT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CCD743D1D for ; Thu, 15 Jul 2004 11:57:40 +0000 (GMT) (envelope-from marks@dell-laptop.6bone.nl) Received: by postman.ripe.net (Postfix, from userid 8) id 83F614E2DA; Thu, 15 Jul 2004 13:57:39 +0200 (CEST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 39D984E7F4; Thu, 15 Jul 2004 13:57:39 +0200 (CEST) Received: from dell-laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id i6FBvd4c025967; Thu, 15 Jul 2004 13:57:39 +0200 Received: (nullmailer pid 19971 invoked by uid 1001); Thu, 15 Jul 2004 11:57:38 -0000 Date: Thu, 15 Jul 2004 13:57:38 +0200 From: Mark Santcroos To: Wilko Bulte Message-ID: <20040715115738.GA17082@laptop.6bone.nl> References: <20040714203642.GA13855@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040714203642.GA13855@freebie.xs4all.nl> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Status: N 0.002419 / 0.0 / 0.0 / disabled X-RIPE-Signature: fe8911555068cb90e5de736468c25e51 cc: current@freebsd.org Subject: Re: hm, how to recover from a fscked-up device.hints? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jul 2004 11:57:40 -0000 On Wed, Jul 14, 2004 at 10:36:42PM +0200, Wilko Bulte wrote: > I just created myself an interesting challenge: > > - I basically replaced my /boot/device.hints with a nonsensical one (don't > ask), it is not a device.hints file at all. > > How does one recover from that? Booting kernel.old does not fix it for > obvious reasons.. If the CDROM suggestion fails, you can try to: 1. load the kernel directly from boot1 (probably won't help, but easy try) or 2. feed the device.hints through the loader command line. (You don't need all of it, need to enable vt, etc) G'luck Mark