From owner-freebsd-current@freebsd.org  Wed Sep 16 02:18:07 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 765059C2B07
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Wed, 16 Sep 2015 02:18:07 +0000 (UTC)
 (envelope-from rysto32@gmail.com)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com
 [IPv6:2607:f8b0:4001:c05::22c])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 43F6A1ED7;
 Wed, 16 Sep 2015 02:18:07 +0000 (UTC)
 (envelope-from rysto32@gmail.com)
Received: by igcrk20 with SMTP id rk20so26181562igc.1;
 Tue, 15 Sep 2015 19:18:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=eg3nprHPLwPdz0GunDkvSZtB8a+D4ICIhLbE8gSg6w0=;
 b=XNYhEC/jBWiyOioaDXZRjC+znFRLk36PghSmbWqFAab/IyQFBSaEWaoGI1bkZdOiu4
 9uQ7XwI74yQAUYlDtPwLd+3RBc1mZXoAMsRnH2pH1xCMWkjiIfDIUY/rngXeAnfiJZ8a
 boRYUfQ7FtEQWB3GWWxgH64QqifNXZd0toHRWpeHjwHlvdwO/AO0JrecdeFrzVeH7iyw
 dT5dVWrGhcZlTRbXVBoGud+wDU3LgvF5R3Hh7nYsVt2GZNbCp70SZdR73DRpx7JltC1B
 /6ASYhk7LZ96G6uz/6GYakl9WjYkIoI0B0Iz9oEYEiWGukqNL9OB73MMLpegOfvFTeW/
 BNwA==
MIME-Version: 1.0
X-Received: by 10.50.30.106 with SMTP id r10mr11749686igh.69.1442369886723;
 Tue, 15 Sep 2015 19:18:06 -0700 (PDT)
Received: by 10.107.178.67 with HTTP; Tue, 15 Sep 2015 19:18:06 -0700 (PDT)
In-Reply-To: <55F8CBB2.1080109@freebsd.org>
References: <CAO0mX5YwFpUhcWfni8QeyOzesFmLpCQnkPT5zFOYU5PokYdiFw@mail.gmail.com>
 <55F8CBB2.1080109@freebsd.org>
Date: Tue, 15 Sep 2015 22:18:06 -0400
Message-ID: <CAFMmRNymd6jeZLepa1W_2m-5uYC5AO+9qyVyzZNnoYJpvibDSg@mail.gmail.com>
Subject: Re: nanoBSD boot problem (on USB stick or as a HD)
From: Ryan Stone <rysto32@gmail.com>
To: Julian Elischer <julian@freebsd.org>
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.20
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Sep 2015 02:18:07 -0000

On Tue, Sep 15, 2015 at 9:53 PM, Julian Elischer <julian@freebsd.org> wrote:

> one possibility is to use  gpart label to describe the device.
> possibly it woudl hav ehte same result in both cases, but I don't know for
> sure that
> it works for root device.. you'd have to test.
>
>
I would recommend a UFS label instead.  gpart labels are kind of fragile
and easy to mess up.  My previous employer has been shipping systems where
the root fs is specified in fstab via a UFS label for years and it never
gave us a problems.