From owner-freebsd-questions@FreeBSD.ORG Thu Jul 10 10:10:59 2003 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 10FC737B401 for ; Thu, 10 Jul 2003 10:10:59 -0700 (PDT) Received: from out005.verizon.net (out005pub.verizon.net [206.46.170.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 284D643FA3 for ; Thu, 10 Jul 2003 10:10:58 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com ([141.149.47.46]) by out005.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030710171057.OMYR20032.out005.verizon.net@mac.com> for ; Thu, 10 Jul 2003 12:10:57 -0500 Message-ID: <3F0D9E1F.8030404@mac.com> Date: Thu, 10 Jul 2003 13:10:55 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: questions@freebsd.org References: <39020-2200374103946796@M2W035.mail2web.com> <3F0D112F.9010804@mac.com> <20030710170111.GE3656@webserver.get-linux.org> In-Reply-To: <20030710170111.GE3656@webserver.get-linux.org> X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out005.verizon.net from [141.149.47.46] at Thu, 10 Jul 2003 12:10:57 -0500 Subject: Re: Changed a filesystem's name -- now system hangs on reboot (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: Thu, 10 Jul 2003 17:10:59 -0000 Joshua Oreman wrote: > On Thu, Jul 10, 2003 at 03:09:35AM -0400 or thereabouts, Chuck Swiger wrote: [ ... ] >> This is when you boot single-user mode off of the install CD, or the FIXIT >> CD (#2) if you have that around. Then mount your hard drive's root >> partition on /mnt (or make something in /tmp), and fix the problem. > > Completely unnecessary. While I am a fan of "use the existing tools to fix the problem without physical intervention if at all possible"-- remote management does that to you-- I think what the OP was asking was "what should I do if I've screwed up the config on the hard drive enough that it won't boot properly, and I want to start from a known-working environment to fix things". Booting single-user off a CD may be completely unnecessary in this particular case; nevertheless, it's a valid solution to the problem. -- -Chuck