From owner-freebsd-current@freebsd.org Sun May 5 01:21:59 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F13E8159E23C for ; Sun, 5 May 2019 01:21:58 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8889580909; Sun, 5 May 2019 01:21:57 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id x451LFsV034786 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 4 May 2019 18:21:16 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id x451LFZ9034784; Sat, 4 May 2019 18:21:15 -0700 (PDT) (envelope-from fbsd) Date: Sat, 4 May 2019 18:21:14 -0700 From: bob prohaska To: "Rodney W. Grimes" Cc: Warner Losh , Glen Barber , Enji Cooper , Alan Somers , David Boyd , FreeBSD CURRENT Subject: Firstboot behavior, was Re: New vm-image size is much smaller than previos Message-ID: <20190505012114.GA34528@www.zefox.net> References: <20190504033340.GB26932@www.zefox.net> <201905041303.x44D30CW097600@gndrsh.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201905041303.x44D30CW097600@gndrsh.dnsmgr.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 8889580909 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [4.63 / 15.00]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.90)[0.900,0]; IP_SCORE(0.11)[ip: (0.43), ipnet: 50.1.16.0/20(0.21), asn: 7065(-0.03), country: US(-0.06)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.78)[0.776,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: www.zefox.net]; NEURAL_SPAM_LONG(0.96)[0.957,0]; RCPT_COUNT_SEVEN(0.00)[7]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Sun, 05 May 2019 01:21:59 -0000 [changed subject to follow drift of conversation] On Sat, May 04, 2019 at 06:03:00AM -0700, Rodney W. Grimes wrote: > > Do we even have install note(s) pages for these things, or a wiki page Not that I know of. > that documents it, or ? Working around /firstboot does not require > a serial console, if you know about it ahead of time, you can even ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8-) The statement is true. The gymnastics required to > mount the sd image up on another system, and remove firstboot if you > want, or create a swap partition at the end of the device, make the > boot partition use up the rest and then iirc growfs on firstboot does > what you want. (Untested at this time, but that should just work.) are far from trivial, even for experienced foot-shooters such as myself. A Pi running Raspbian can download and write the FreeBSD image, but it can't mount ufs to manipulate files. I'm not sure about Mac OS and Windows. That's a likely starting scenario for potential users of FreeBSD on the Pi. AFAIK it's still necessary to boot single-user, set up the microSD (which is a considerable challenge using gpart unless one is in good practice) and then let the system go to multi-user. Last time I checked, u-boot (or maybe it's loader) couldn't read the USB keyboard to execute boot -s so the system essentially runs away from the user's control. I admit not having checked in the last few months, but even if it's fixed asking a new user to start by using gpart is unlikely to encourage further exploration. Thanks for your attention! bob prohaska