From owner-freebsd-current@freebsd.org Fri Mar 19 22:21:37 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 6806F5AE748 for ; Fri, 19 Mar 2021 22:21:37 +0000 (UTC) (envelope-from yuripv@yuripv.dev) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4F2JJx1Cp6z4V2N for ; Fri, 19 Mar 2021 22:21:37 +0000 (UTC) (envelope-from yuripv@yuripv.dev) Received: by mailman.nyi.freebsd.org (Postfix) id 278E35AE6C3; Fri, 19 Mar 2021 22:21:37 +0000 (UTC) Delivered-To: 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 2751F5AE6C2 for ; Fri, 19 Mar 2021 22:21:37 +0000 (UTC) (envelope-from yuripv@yuripv.dev) Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F2JJw3dGtz4Tyc for ; Fri, 19 Mar 2021 22:21:36 +0000 (UTC) (envelope-from yuripv@yuripv.dev) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id 11438580A17 for ; Fri, 19 Mar 2021 18:21:36 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 19 Mar 2021 18:21:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.dev; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=X xV+FpIjXQd+wipv76IunAgVxZO2GuMnci/l9dHjCQI=; b=mXDuocmGgLN63NhjW E6NU6llTLs5TUGFpoJF6Jrh2cnINVMYbtr+JGibSdn0vmSGJA0+SiPYrnhKaauuk /Ra0QUI6ph+e17i/ikxlFf/nhPNUd132SMQ2GXVPujp4Ew6viQ4sQJ6tQ6SGvGkq 6P+1i6inMtl7mV/hQS7BhG4MVIbhaZDzgvBf55YAj/qDDp/mfp8FsZXwaCxnA2NW oRmRkgbDY4Oite6fR/RrCXhBpqg8d3wLssoDGK0oaC4heo0et2Ui+Dh7ZfZFGwSr zlcf66WAp/LAhOTmGj21lfesTmgiL8wcD8Bt/MegEHcm1akCyiM+3GdkAlN+HGpK E06hw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=XxV+FpIjXQd+wipv76IunAgVxZO2GuMnci/l9dHjC QI=; b=I+AuXQSlhriUF8OYJzdGtgRNjJ+cQlpWNSTfCQb8lSNG9XOAxuy7/B7c1 wOezi5SkLoMHamyflNPdOQzbY7wT7kfMYy/lNgt4ZXE1t0qxNtKptY/fG0d3acmG NMSjjzh+waCFsw3DuV6irkRzw5Q+yqfN39Y8t6L3/oou3koShZDxq/H3D5xzXw6n XFWO0aIYvrqUVdLzuZTYJrdoYA5oaU+/Xj1V+JMV//EzHSVlHudESLLPzkGL9Uoh oUdR6D4Tz3WYfxTxJcwV4k+PPBYwqJW75la/MJXgcw23ZNoHVkpD/ZU3igPTPQ/n dQOh+OlSBXRGHobOxxekY2gQrvT+A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudefledgvdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtke ertddtfeejnecuhfhrohhmpegjuhhrihcurfgrnhhkohhvuceohihurhhiphhvseihuhhr ihhpvhdruggvvheqnecuggftrfgrthhtvghrnhepveefvefgtefgueekfeejudeukeffje eugfeiteetueelvddttefhleehvdejteevnecuffhomhgrihhnpehfrhgvvggsshgurdho rhhgnecukfhppeeluddrvdegtddruddvgedrudefjeenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpeihuhhrihhpvheshihurhhiphhvrdguvghv X-ME-Proxy: Received: from [192.168.1.12] (unknown [91.240.124.137]) by mail.messagingengine.com (Postfix) with ESMTPA id C5B8924005A for ; Fri, 19 Mar 2021 18:21:34 -0400 (EDT) Subject: Re: [Bug 254395] bsdinstall: fail script install after BETA3 To: current@freebsd.org References: <2132088f8d7addba911e3f49fc674e1b@bsdforge.com> From: Yuri Pankov Message-ID: <024a371e-a57d-9b94-b85a-e8b59be76a22@yuripv.dev> Date: Sat, 20 Mar 2021 01:21:34 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <2132088f8d7addba911e3f49fc674e1b@bsdforge.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4F2JJw3dGtz4Tyc X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yuripv.dev header.s=fm1 header.b=mXDuocmG; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=I+AuXQSl; dmarc=none; spf=pass (mx1.freebsd.org: domain of yuripv@yuripv.dev designates 66.111.4.229 as permitted sender) smtp.mailfrom=yuripv@yuripv.dev X-Spamd-Result: default: False [-2.40 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.229:c]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[yuripv.dev:+,messagingengine.com:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[66.111.4.229:from]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.229:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[yuripv.dev:s=fm1,messagingengine.com:s=fm2]; FREEFALL_USER(0.00)[yuripv]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; DMARC_NA(0.00)[yuripv.dev]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[66.111.4.229:from:127.0.2.255]; NEURAL_SPAM_SHORT(0.20)[0.201]; MAILMAN_DEST(0.00)[current] 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: Fri, 19 Mar 2021 22:21:37 -0000 Chris wrote: > On 2021-03-19 13:06, bugzilla-noreply@freebsd.org wrote: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 >> >> Nathan Whitehorn changed: >> >>            What    |Removed                     |Added >> ---------------------------------------------------------------------------- >> >>            Severity|Affects Only Me             |Affects Some People >>                  CC|                            |imp@FreeBSD.org >>            Priority|---                         |Normal >> >> --- Comment #6 from Nathan Whitehorn --- >> Thanks for the suggestion about the documentation -- I've updated the >> man page. >> >> The core problem here is that our tar can't extract archives to FAT32 >> with >> default options, since it treats inability to set modification time as >> a fatal >> error and FAT32 doesn't let you do that on the root directory. As >> such, any >> file in the release tarballs can't be extracted to FAT32. For interactive >> installations, the bsdinstall distextract tool, a CURSES-y frontend to >> libarchive, solves this by ignoring ctime/mtime errors. >> >> Some extra commentary on solutions, so it can be in one place. >> Possibilities >> are: >> >> 1. We drop /boot/efi from mtree. That will result in it not existing in >> base.txz, solving this issue, but will result in it not being in >> mtree. It will >> also leave in place an identical bug that will break scripted >> installation on >> bare-metal POWER8 and POWER9 systems, although that is a tier-2 platform. >> >> 2. We add an option to tar to ignore failure in setting ctime/mtime, >> like the >> interactive installer uses. This has the difficulty that the patch is >> hacky and >> would have to go through upstream. >> >> 3. We go back to using distextract for scripted installations as well as >> interactive ones, reverting d7640440fb644fde697f62fdff0b55aa3a4d5ef7. >> This >> fixes this issue but will result in installation failures for scripted >> installs >> without a controlling tty. (It will also add nice progress bars to >> scripted >> installs). >> >> 4. We do --exclude /boot/efi when running tar, then mkdir -p it by hand >> afterward. This is incredibly hacky and otherwise essentially >> functionally >> equivalent to #1. Like #1, it will fix this issue and has no obvious >> functional >> downside, but leaves scripted installs bare-metal POWER8 and POWER9 >> broken. >> >> 5. We patch the file system driver to (pretend to) allow setting times >> on the >> mount point. I don't want to do this, since I don't want to solve this >> in the >> kernel at RC3 and I don't like it pretending to do things it can't do. > >  6. (my favorite) do NOT require that the efi/ partition be in strictly a >  fat32 format. I mean fat32 is not strictly required as the format for > the efi >  partition. It is simply _assumed_ to be the required format and as > such, the >  one used in so many cases. Wrong, see "13.3 File System Format" in UEFI specification. > Whould it actually be that much harder to use ffs/ufs? > > You asked. ;-) > >> >> -------- >> >> Of these, 1, 3, and 4 are quite easy to implement, but all have some >> downside. >> My temptation is to do 4 for 13.0, since it will definitely work but >> is just >> lame, then either do #2 or a variant on #3 where distextract notices >> there is >> no tty and doesn't try to set up a dialog as a longer-term fix in >> HEAD. Any >> thoughts?