From owner-freebsd-questions@FreeBSD.ORG  Sun Nov 23 00:20:46 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5C64AC9F
 for <freebsd-questions@freebsd.org>; Sun, 23 Nov 2014 00:20:46 +0000 (UTC)
Received: from mail.cyberleo.net (paka.cyberleo.net [216.226.128.180])
 by mx1.freebsd.org (Postfix) with ESMTP id 3A83B8CC
 for <freebsd-questions@freebsd.org>; Sun, 23 Nov 2014 00:20:45 +0000 (UTC)
Received: from [172.16.44.4] (vitani.den.cyberleo.net [216.80.73.130])
 by mail.cyberleo.net (Postfix) with ESMTPSA id 5B644195FB;
 Sat, 22 Nov 2014 19:20:37 -0500 (EST)
Message-ID: <54712854.1000007@cyberleo.net>
Date: Sat, 22 Nov 2014 18:20:36 -0600
From: CyberLeo Kitsana <cyberleo@cyberleo.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.8.0
MIME-Version: 1.0
To: lnrt <lnrt80@openmailbox.org>, freebsd-questions@freebsd.org
Subject: Re: Full disk encryption on FreeBSD 10.1-RELEASE?
References: <72aee80c9f26982088d6b2e018744c91@openmailbox.org>
In-Reply-To: <72aee80c9f26982088d6b2e018744c91@openmailbox.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Nov 2014 00:20:46 -0000

On 11/22/2014 05:44 PM, lnrt wrote:
<snip>
> This result in the following error when booting the system:
> 
> config: not a directory.
> loader: not a directory.
> gptboot: No /boot/loader on 0:ad(0p2)
> kernel: not a directory.
> gptboot: No /boot/kernel/kernel on 0:ad(0p2)
> 
> FreeBSD/x86 boot
> Default: 0:ad(0p2)/boot/kernel/kernel
> boot:
> 
> Does anyone have a suggestion on why the second method won't work?

All the boot files end up in /boot, which is on a separate filesystem.
>From the point of view of the boot process, the files are no longer
/boot/loader and such, but instead just /loader. I have found no easy
way to change this in the code itself, so I work around it with a symlink.

With the boot filesystem mounted on /boot:
----8<----
mv /boot/boot /boot/boot.blk
ln -s . /boot/boot
----8<----

Now gptboot(8) will look for /boot/loader, dereference the symlink, and
load /loader instead, and everything will work. Same with loader(8)
looking for its files and kernel.

Just remember you did this during upgrades, because installworld will
fail in weird ways with that symlink there.

-- 
Fuzzy love,
-CyberLeo
Technical Administrator
CyberLeo.Net Webhosting
http://www.CyberLeo.Net
<CyberLeo@CyberLeo.Net>

Furry Peace! - http://www.fur.com/peace/