From owner-freebsd-current@freebsd.org Tue May 4 20:35:18 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 83BC5622582 for ; Tue, 4 May 2021 20:35:18 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FZWn23S3rz4TZC for ; Tue, 4 May 2021 20:35:18 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from comporellon.tachypleus.net (unknown [IPv6:2601:405:4a00:acd:4491:83d2:e2d6:4cc8]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: nwhitehorn/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 518206C62 for ; Tue, 4 May 2021 20:35:18 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Subject: Re: should bsdinstall work? To: freebsd-current@freebsd.org References: From: Nathan Whitehorn Message-ID: Date: Tue, 4 May 2021 16:35:17 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 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: Tue, 04 May 2021 20:35:18 -0000 Yes, it should work just fine; however, we don't provision the microsd images for the installer, especially for -CURRENT. The actual OS is fetched in plaintext to allow caching and the MANIFEST files are what provides authentication -- they provide the checksums of the files that get fetched so that they can be verified against corruption and tampering. For snapshots, the current version changes all the time and that doesn't work; it also means that network-install media have to be set up with those checksums in advance. Where are you trying to install to? Usually the assumption is that the microsd images *are* the installed system rather than a tool you use to install a system. -Nathan On 5/4/21 3:22 PM, tech-lists wrote: > Hi, > > I've been trying to set up a boot-from-usb3 raspberry pi 4. I thought > i'd be able to do this by booting into latest current snapshot image for > arm64 rpi (written to microsd), and then running bsdinstall as root. > > I can select the auto-zfs option then select the usb3 disk as > installation destination. The bsdinstall selects the sets and downloads > them, but then get the error: > > "error while fetching file://usr/freebsd-dist/MANIFEST : No such file or > directory" > > also tried via release/13 image, same error. Looks like it's downloading > the files but then the installer can't see them, something like that. > > the downloaded files are there: > > root@generic:~ # ls -lah /mnt/usr/freebsd-dist/ > total 187454 > drwxr-xr-x  2 root  wheel     4B Apr  9 06:51 . > drwxr-xr-x  6 root  wheel     6B Apr  9 06:50 .. > -rw-r--r--  1 root  wheel   158M Apr  9 06:51 base.txz > -rw-r--r--  1 root  wheel    25M Apr  9 06:51 kernel.txz > root@generic:~ # > worth submitting a PR? or is bsdinstall legacy and I need to use some > other method. I've not tried releng/12.2 yet. > > thanks,