From owner-freebsd-current@freebsd.org Wed Sep 16 02:26:00 2015 Return-Path: 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 1CA459CD143 for ; Wed, 16 Sep 2015 02:26:00 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (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 CF9F31614; Wed, 16 Sep 2015 02:25:59 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by qgx61 with SMTP id 61so160674413qgx.3; Tue, 15 Sep 2015 19:25:59 -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=pcYw2I56qc+GG0CJQOCGm5cbXaVKGzHE/ce5mRfNmd8=; b=KXZ6ArHo/wLhSjyKSrD8EmwhwkLNethCfXiC/q2EqbeNCk42tVFOutYu8XFTJvf+zW jUCnaEo3LTZRm3Ba2jgeIYLaLRU8FM45/OQ2Z7qYyFT1VpeYp8fyMcRv4SirMwT2/WVy 8cKQ0tcsMpSizBnSqRErSoO3/CWPQPlXiOX6nKWVAqkjCgiQoE1Imn7z/KGBsYG4VqmM Sh/KtSiaGzBrff3ukrURlUdkjhUWJJmZEUzheXy7q11fQ4pwM6pMEs9lNQ1dwC7jNsAU 489LR50XKVCCV/0+WqMQDoRrwiVT7Mj4OyCVpEDQ/SO6NU0XRmkqRDV/GINbld2p7oqA RiFA== MIME-Version: 1.0 X-Received: by 10.140.216.211 with SMTP id m202mr39667251qhb.80.1442370358958; Tue, 15 Sep 2015 19:25:58 -0700 (PDT) Received: by 10.140.94.33 with HTTP; Tue, 15 Sep 2015 19:25:58 -0700 (PDT) In-Reply-To: References: <55F8CBB2.1080109@freebsd.org> Date: Tue, 15 Sep 2015 19:25:58 -0700 Message-ID: Subject: Re: nanoBSD boot problem (on USB stick or as a HD) From: NGie Cooper To: Ryan Stone Cc: Julian Elischer , FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 02:26:00 -0000 On Tue, Sep 15, 2015 at 7:18 PM, Ryan Stone wrote: > On Tue, Sep 15, 2015 at 9:53 PM, Julian Elischer 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. +100 And FWIW as Stefano discovered later, NANO_LABEL does just that (use UFS labels). The only unfortunate thing is that nanobsd uses a NUL string by default: grep NANO_LABEL tools/tools/nanobsd/defaults.sh tools/tools/nanobsd/defaults.sh:NANO_LABEL="" tools/tools/nanobsd/defaults.sh: echo newfs ${NANO_NEWFS} ${NANO_LABEL:+-L${NANO_LABEL}${lbl}} ${dev} tools/tools/nanobsd/defaults.sh: newfs ${NANO_NEWFS} ${NANO_LABEL:+-L${NANO_LABEL}${lbl}} ${dev} tools/tools/nanobsd/defaults.sh: if [ ! -z ${NANO_LABEL} ]; then tools/tools/nanobsd/defaults.sh: tunefs -L ${NANO_LABEL}"s2a" /dev/${MD}s2a tools/tools/nanobsd/defaults.sh: # Override user's NANO_DRIVE if they specified a NANO_LABEL tools/tools/nanobsd/defaults.sh: [ ! -z "${NANO_LABEL}" ] && NANO_DRIVE="ufs/${NANO_LABEL}" The default NANO_DRIVE is useless though -- the old ata(4) stack is dead: 95 # The drive name of the media at runtime 96 NANO_DRIVE=ad0 Cheers, -NGie