From owner-freebsd-arm@freebsd.org Sun Jul 17 18:32:25 2016 Return-Path: Delivered-To: freebsd-arm@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 AC0FBB9C97B for ; Sun, 17 Jul 2016 18:32:25 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (kientzle.com [142.254.26.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 517B81D13 for ; Sun, 17 Jul 2016 18:32:25 +0000 (UTC) (envelope-from tim@kientzle.com) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id u6HIMfft071214; Sun, 17 Jul 2016 18:22:41 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.106] (192.168.1.101 [192.168.1.101]) by kientzle.com with SMTP id xknwsp4z48nsiuxtegq5es3u2e; Sun, 17 Jul 2016 18:22:41 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Bizarre clone attempt failures on Raspberry Pi2... From: Tim Kientzle In-Reply-To: Date: Sun, 17 Jul 2016 11:22:41 -0700 Cc: freebsd-arm Content-Transfer-Encoding: 7bit Message-Id: <841D0760-66D7-43A7-AB6A-AEFEA177DAD6@kientzle.com> References: <548783e1-9047-68f7-5f50-449db684d602@denninger.net> <5475ea53-ae22-2634-6f2a-5737d1b0e308@denninger.net> <398ae56c-8893-f188-c210-cf7f19ccf433@denninger.net> <1468518953.72182.219.camel@freebsd.org> <7a91fc79-1c85-fac8-aa3f-db90592f3f44@denninger.net> <60b6e156-981e-9fbd-b68c-0daae1961286@denninger.net> <04391154-A38E-46CD-B570-B2BECFD19022@gromit.dlib.vt.edu> To: Karl Denninger X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jul 2016 18:32:25 -0000 > > > The quick fix is to put "failok" (or noauto) in the default /etc/fstab > entry for the dos filesystem, since it is not necessary for that > filesystem to be mounted at all on a running machine. If there is a > policy reason to leave it accessible (and there's a fairly-clean > argument that there is) then "failok" might be preferable to "noauto", > but either way forcing a filesystem that is not necessary to be > accessible or the system fails to come up and does not give any > indication of same on what many users will have accessible to them is > facially wrong. History: I believe this is something I introduced in Crochet that has been picked up by the RE build scripts. Mounting the MSDOS partition as /boot/msdos was intended to ensure that the critical boot elements were all visible so they could be easily edited and/or updated. For example, the FDT files (and other boot-time configuration files) reside there. Without this, those components are invisible and hence more difficult to update on device and also more difficult to explain and document. Tim