Date: Fri, 16 Jul 2004 18:34:10 +0200 From: Wilko Bulte <wb@freebie.xs4all.nl> To: ticso@cicely.de Cc: current@freebsd.org Subject: Re: hm, how to recover from a fscked-up device.hints? Message-ID: <20040716163410.GB24452@freebie.xs4all.nl> In-Reply-To: <20040716163226.GB21212@cicely12.cicely.de> References: <20040714203642.GA13855@freebie.xs4all.nl> <20040715114425.GG29928@submonkey.net> <20040715130055.GC17340@freebie.xs4all.nl> <20040716163226.GB21212@cicely12.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 16, 2004 at 06:32:27PM +0200, Bernd Walter wrote: > On Thu, Jul 15, 2004 at 03:00:55PM +0200, Wilko Bulte wrote: > > On Thu, Jul 15, 2004 at 12:44:25PM +0100, Ceri Davies wrote: > > > 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.. > > > > > > Boot from CDROM? > > > > Yeah.. I thought of that one, but I was wondering about something > > more clever. Probably does not exist :) > > Cut & Paste it on serial console - or as other said type the minimum > required for single user mode by hand. I went for the CDboot method, which obviously works OK. -- Wilko Bulte wilko@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040716163410.GB24452>