From nobody Mon Feb 21 15:19:58 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id BE3B919D0DC9 for ; Mon, 21 Feb 2022 15:20:16 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-ztdg10021901.me.com (pv50p00im-ztdg10021901.me.com [17.58.6.55]) (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 4K2QwJ0Q84z4Vfr for ; Mon, 21 Feb 2022 15:20:16 +0000 (UTC) (envelope-from tsoome@me.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=1a1hai; t=1645456809; bh=uY+pi/R/dR/4hkDwoz4gw+N8nvgz6iU39f/c8KIBhbM=; h=Content-Type:Mime-Version:Subject:From:Date:Message-Id:To; b=uHhvgEzzwUw/vh3/FNsIrus0uWDrEI7BtjbFCctRadZJWPuN87mlxNbemOx1yC5pF oUnQt6nwa+BgOgheFQeNxg/vEgWmu5DG5Xsze5wgdKCx0GxpIbDegJyxJu8u3IMQlA 4VROzVrTKlghCtNpVd0cUu1PlE6UZ8QgReqRbczoZda7ng+x9+FjpXhhNm4Fy53M0d gfBKQNDms07yfSNqLI9xe+es1u3W/Vc65Fi7i7VUA7fserMJP4DVDLtjrKTCjtmXca +AqL5uTZLulwb2Af9tVg1Ryxj20cq7bqGwHq+ojfExP8zbcY34AtW78K7FqoXqXqO3 +WlxTmUpzd8cw== Received: from smtpclient.apple (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-ztdg10021901.me.com (Postfix) with ESMTPSA id C0D9181B49; Mon, 21 Feb 2022 15:20:07 +0000 (UTC) Content-Type: text/plain; charset=utf-8 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\)) Subject: Re: pxeboot binary is too big on FreeBSD (>640KBytes) From: Toomas Soome In-Reply-To: <6984fd5d-ae58-11a4-0d21-a8695b0c77f7@selasky.org> Date: Mon, 21 Feb 2022 17:19:58 +0200 Cc: FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <02586EFB-0BB5-46BF-9EE5-28623D20EFD3@me.com> References: <6984fd5d-ae58-11a4-0d21-a8695b0c77f7@selasky.org> To: Hans Petter Selasky X-Mailer: Apple Mail (2.3693.60.0.1.1) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.425,18.0.816 definitions=2022-02-21_07:2022-02-21,2022-02-21 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2009150000 definitions=main-2202210090 X-Rspamd-Queue-Id: 4K2QwJ0Q84z4Vfr X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=me.com header.s=1a1hai header.b=uHhvgEzz; dmarc=pass (policy=quarantine) header.from=me.com; spf=pass (mx1.freebsd.org: domain of tsoome@me.com designates 17.58.6.55 as permitted sender) smtp.mailfrom=tsoome@me.com X-Spamd-Result: default: False [-3.57 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; RWL_MAILSPIKE_EXCELLENT(0.00)[17.58.6.55:from]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[me.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; NEURAL_HAM_SHORT(-1.00)[-0.999]; RCVD_IN_DNSWL_LOW(-0.10)[17.58.6.55:from]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[me.com]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.97)[-0.973]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; FREEFALL_USER(0.00)[tsoome]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[me.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; RECEIVED_SPAMHAUS_PBL(0.00)[80.235.52.148:received]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N > On 21. Feb 2022, at 09:43, Hans Petter Selasky = wrote: >=20 > FYI: >=20 > After a lot of digging trying everything, I found that the pxeboot and = loader.efi was too big simply due to ZFS support. >=20 > So I did this after buildworld: >=20 > cd /usr/src/stand > make WITHOUT_LOADER_ZFS=3DYES clean > make WITHOUT_LOADER_ZFS=3DYES all > make WITHOUT_LOADER_ZFS=3DYES install >=20 > And now it works, with my old GigaByte mainboard! >=20 > Why should pxeboot have ZFS support? >=20 > = https://forums.freebsd.org/threads/problem-with-isc-dhcpd-and-diskless-boo= ting.82199/ >=20 > =E2=80=94HPS >=20 Well, the feature X can be helpful for recovery purposes. The root cause = is not the feature X itself, but the size limit. And the unfortunate = fact, the size limit is not fixed, but depends on the system. Therefore = there are two options - either to fix the size limit or drop option X = from default build =E2=80=94 at least till the size limit is fixed (or = support for BIOS will be dropped). rgds, toomas=