From owner-freebsd-newbies@FreeBSD.ORG Tue Apr 15 01:59:46 2003 Return-Path: Delivered-To: freebsd-newbies@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F08EC37B401 for ; Tue, 15 Apr 2003 01:59:46 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DC2643FAF for ; Tue, 15 Apr 2003 01:59:46 -0700 (PDT) (envelope-from DougB@freebsd.org) Received: from master.gorean.org (12-234-22-23.client.attbi.com[12.234.22.23]) by sccrmhc03.attbi.com (sccrmhc03) with SMTP id <2003041508594100300fc6bde>; Tue, 15 Apr 2003 08:59:41 +0000 Date: Tue, 15 Apr 2003 01:59:40 -0700 (PDT) From: Doug Barton To: Sperry Russ In-Reply-To: <200304141421020644.001DA712@smtp.earthlink.net> Message-ID: <20030415015619.W2937@znfgre.tberna.bet> References: <200304141421020644.001DA712@smtp.earthlink.net> Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-newbies@freebsd.org Subject: Re: Failed To Boot X-BeenThere: freebsd-newbies@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Gathering place for new users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Apr 2003 08:59:47 -0000 Howdy, Unlike some other forums, the -newbies list here is not for questions, it's for discussing new user experiences. You should have asked this in freebsd-questions@freebsd.org, but since the answer is so easy ... On Mon, 14 Apr 2003, Sperry Russ wrote: > I am using a boot manager named BootIt and have win2000, linux and other > systems installed. > > When I installed FreeBSD I set it not to modify my boot manager. Upon > my first boot it booted to the point of a prompt with the words: mount > root> and informed me that i needed to supply a file system and device. Our boot loader requires a little more access to your disk than your multi-boot thingy is giving it. You might be able to find a workaround by posting the details to -questions, but it sounds like you should give our boot manager a try. It's not pretty, but it works quite well. :) Doug -- This .signature sanitized for your protection