Date: Sat, 25 Nov 2023 14:45:29 +0000 From: bugzilla-noreply@freebsd.org To: rc@FreeBSD.org Subject: [Bug 274977] [rc] [patch] /etc/rc.initdiskless: /rescue/tar: not found Message-ID: <bug-274977-20181-ULirmxsRT3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-274977-20181@https.bugs.freebsd.org/bugzilla/> References: <bug-274977-20181@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D274977 Jose Luis Duran <jlduran@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlduran@gmail.com --- Comment #3 from Jose Luis Duran <jlduran@gmail.com> --- While I do not object to the change proposed in review D42765, I think the issue may be that you probably used the files from FreeBSD-13.2-RELEASE-amd64-bootonly.iso or FreeBSD-13.2-RELEASE-amd64-disc1= .iso to populate your /tftpboot/FreeBSD/install directory? (see https://docs.freebsd.org/en/books/handbook/advanced-networking/#network-dis= kless). These two images do not contain a /rescue indeed since https://cgit.freebsd.org/src/commit/?id=3D6e352319b6ff97a20b53d13a6df76b71d= d12afc9, given it is a read-only media, it should not "need" a /rescue. If you untar base from: https://download.freebsd.org/releases/amd64/amd64/13.2-RELEASE/base.txz into /tftpboot/FreeBSD/install, you'll notice that it indeed contains /resc= ue. All that said, if that solves the problem, we should perhaps clarify the handbook to instruct the users on how to populate the /install directory, as having rc.initdiskless use the tar binary from /rescue may have its advanta= ges as well. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-274977-20181-ULirmxsRT3>