https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274977
Jose Luis Duran <jldu...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jldu...@gmail.com
--- Comment #3 from Jose Luis Duran <jldu...@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-diskless).
These two images do not contain a /rescue indeed since
https://cgit.freebsd.org/src/commit/?id=6e352319b6ff97a20b53d13a6df76b71dd12afc9,
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 /rescue.
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 advantages
as well.
--
You are receiving this mail because:
You are the assignee for the bug.
