From nobody Mon Feb 21 17:43:06 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 26A9519D1523 for ; Mon, 21 Feb 2022 17:43:25 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st43p00im-zteg10072001.me.com (st43p00im-zteg10072001.me.com [17.58.63.167]) (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 4K2V5S3V3Sz3Gcj for ; Mon, 21 Feb 2022 17:43:24 +0000 (UTC) (envelope-from tsoome@me.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=1a1hai; t=1645465398; bh=pkHvWTuOKyuimlHbAicXVBr+K7KIVI7ouERhoYEXWNA=; h=Content-Type:Mime-Version:Subject:From:Date:Message-Id:To; b=UDtl0N7L1JorN0D+s/A6uiBz9w9zUaAZXA22W10gJ3vhk3GN2MKBdaYb7mB6uDc8x zQy3VxuP2x1k1sMG1lW3FaI0vIWJxmnusS1cWf9g8B+M+lSlLiKd7ya7quX1ITCY+3 6q+8V8clGz6lE+PqdhqBiZj2rmt3kJcbJiRCBzA3ggSmUPL4qtiqLUOe2c1zIC+9he 8E4gYpiHZFp8OqT8K5JKzbFLQhSt5MfPihgtcaB2GuamhHqDqdPVtnfl/P4wmqU5hn k//BgL0D76ozaUgXHXGOqDa0lgoUAS0HFm8nVZaj5ku8V/cXpQYlXwO15TtXjQteyN CRQ/K9QW+8lHQ== Received: from smtpclient.apple (148-52-235-80.sta.estpak.ee [80.235.52.148]) by st43p00im-zteg10072001.me.com (Postfix) with ESMTPSA id 5210EB40AA0; Mon, 21 Feb 2022 17:43:11 +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: <16051.1645463921@kaos.jnpr.net> Date: Mon, 21 Feb 2022 19:43:06 +0200 Cc: Hans Petter Selasky , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <9ADBF2DA-0D00-40C0-A2CA-AFBCA7E5F3A4@me.com> References: <6984fd5d-ae58-11a4-0d21-a8695b0c77f7@selasky.org> <02586EFB-0BB5-46BF-9EE5-28623D20EFD3@me.com> <16051.1645463921@kaos.jnpr.net> To: "Simon J. Gerraty" X-Mailer: Apple Mail (2.3693.60.0.1.1) X-Proofpoint-Virus-Version: =?UTF-8?Q?vendor=3Dfsecure_engine=3D1.1.170-22c6f66c430a71ce266a39bfe25bc?= =?UTF-8?Q?2903e8d5c8f:6.0.138,18.0.572,17.0.605.474.0000000_definitions?= =?UTF-8?Q?=3D2020-02-14=5F11:2020-02-14=5F02,2020-02-14=5F11,2020-01-23?= =?UTF-8?Q?=5F02_signatures=3D0?= X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 suspectscore=0 clxscore=1011 spamscore=0 malwarescore=0 adultscore=0 phishscore=0 mlxlogscore=999 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2202210105 X-Rspamd-Queue-Id: 4K2V5S3V3Sz3Gcj X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=me.com header.s=1a1hai header.b=UDtl0N7L; dmarc=pass (policy=quarantine) header.from=me.com; spf=pass (mx1.freebsd.org: domain of tsoome@me.com designates 17.58.63.167 as permitted sender) smtp.mailfrom=tsoome@me.com X-Spamd-Result: default: False [-3.60 / 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.63.167:from]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[me.com:+]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RECEIVED_SPAMHAUS_PBL(0.00)[80.235.52.148:received]; 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.63.0/24, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; FREEFALL_USER(0.00)[tsoome]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DWL_DNSWL_NONE(0.00)[me.com:dkim]; RCVD_IN_DNSWL_LOW(-0.10)[17.58.63.167:from]; 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 19:18, Simon J. Gerraty wrote: >=20 > Toomas Soome wrote: >>> Why should pxeboot have ZFS support? >>=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). >=20 > Or just build separate variants. > As Bjoern said Lua is probably the straw breaking the cammel's back > but I think it reasonable to assume that a system that has the = resources > to support ZFS does not have an ancient BIOS ? >=20 > Thus a non-ZFS version could work for older systems > while those without limitation can use the kitchen-sink version. It is not even about =E2=80=9Cancient=E2=80=9D BIOS, the problem is, PXE = stack does also need resources and it is easier to consume low memory = (just as loader does).=20 rgds, toomas=