From owner-freebsd-questions Tue May 14 8:31: 5 2002 Delivered-To: freebsd-questions@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id CD39937B404 for ; Tue, 14 May 2002 08:30:59 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 14 May 2002 16:30:59 +0100 (BST) To: "Byron L. Sonne" Cc: freebsd-questions@FreeBSD.ORG Subject: Re: trying to fix missing /boot/loader error, no luck In-Reply-To: Your message of "Tue, 14 May 2002 11:13:04 EDT." <3CE12980.2A6BDC58@rogers.com> Date: Tue, 14 May 2002 16:30:58 +0100 From: Ian Dowse Message-ID: <200205141630.aa83695@salmon.maths.tcd.ie> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3CE12980.2A6BDC58@rogers.com>, "Byron L. Sonne" writes: >Yes, since this is a home machine I used a simple partitioning scheme; >other than swap all I have is /boot @ 256MB and / @ 18GB. I've done the Ah, that explains the problem. /boot/loader needs to be on the root filesystem. The separate /boot is not doing what you think it is and it does not achieve anything other than breaking the use of /boot/loader. When you have a /boot on Linux it is a completely different matter, because Linux uses /boot as the root filesystem at first and then switches over to the real one (I think). The simplest recommended filesystem layout is to have a smallish root filesystem and then a /var and a large /usr. For now you can just unmount /boot or mount it somewhere else and copy the contents to /boot on the root filesystem. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message