From nobody Wed Jan 24 20:42:57 2024 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 4TKwrq0L3jz58hC5 for ; Wed, 24 Jan 2024 20:43:07 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from slim.berklix.org (slim.berklix.org [94.185.90.68]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "slim", Issuer "slim" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TKwrp16t9z4P9T; Wed, 24 Jan 2024 20:43:05 +0000 (UTC) (envelope-from jhs@berklix.com) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of jhs@berklix.com has no SPF policy when checking 94.185.90.68) smtp.mailfrom=jhs@berklix.com Received: from dell.no.berklix.net (p4fc4ca6d.dip0.t-ipconnect.de [79.196.202.109]) (authenticated bits=128) by slim.berklix.org (8.17.1/8.17.1) with ESMTPSA id 40OKgvEq068406 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL); Wed, 24 Jan 2024 21:42:57 +0100 (CET) (envelope-from jhs@berklix.com) Received: from dell.no.berklix.net (localhost [127.0.0.1]) by dell.no.berklix.net (8.16.1/8.16.1) with ESMTPS id 40OKgvj6087349 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 24 Jan 2024 21:42:57 +0100 (CET) (envelope-from jhs@localhost.no.berklix.net) Received: (from jhs@localhost) by dell.no.berklix.net (8.16.1/8.16.1/Submit) id 40OKgv8P087348; Wed, 24 Jan 2024 21:42:57 +0100 (CET) (envelope-from jhs) Message-Id: <202401242042.40OKgv8P087348@dell.no.berklix.net> To: Ed Maste cc: FreeBSD Current Subject: Re: Removing fdisk and bsdlabel (legacy partition tools) From: "Julian H. Stacey" Organization: http://berklix.com/jhs/ User-agent: EXMH on FreeBSD http://berklix.com/free/ X-From: http://www.berklix.org/~jhs/ In-reply-to: Your message "Wed, 24 Jan 2024 10:44:57 -0500." 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 Content-Type: text/plain; charset="us-ascii" Content-ID: <87346.1706128977.1@localhost> Date: Wed, 24 Jan 2024 21:42:57 +0100 X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.10 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:33824, ipnet:94.185.88.0/22, country:DE]; FREEFALL_USER(0.00)[jhs]; HAS_ORG_HEADER(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; DMARC_NA(0.00)[berklix.com]; R_SPF_NA(0.00)[no SPF record] X-Rspamd-Queue-Id: 4TKwrp16t9z4P9T Ed Maste wrote: > MBR (PC BIOS) partition tables were historically maintained with > fdisk(8), but gpart(8) has long been the preferred method for working > with partition tables of all types. fdisk has been declared as > obsolete in the man page since 2015. Similarly BSD disklabels were > historically maintained with bsdlabel. It does not yet have a > deprecation notice - I have proposed a man page addition in > https://reviews.freebsd.org/D43563. > > I would like to disconnect these from the build, and subsequently > remove them. This is prompted by a recent bsdlabel bug report which > uncovered a longstanding buffer overflow in that tool. Effort is much > better focused on contemporary, maintained tools rather than > investigating issues in deprecated ones. Removing these tools would > happen in FreeBSD 15 only (no change in 14 or 13). > > Code review to disconnect fdisk: https://reviews.freebsd.org/D43575 > > Note that this effort is limited to these maintenance tools only - > there is no change to kernel or gpart support for MBR or BSD > disklablel partitioning. That said, MBR partitioning and BSD > disklabels are best considered legacy formats and should be avoided > for new installations, if possible. > > If anyone is using fdisk and/or bsdlabel rather than gpart I would > appreciate knowing what is preventing you from using the contemporary > tools. Probably many do, clueless there's a proposal to remove them, as many wont be tracking lists (I havent been tracking lately, focused on moving home, other will have other distractions) Personaly: I run a mix of machines from servers with 14 back through to clients with 4.11 http://berklix.com/scanjet/ Some boxes work well, have no benefit from upgrade & no capability to support the bloat from 4 to 15 but still very useful in heterogenous internal nets. Security is moot behind some firewalls, small is beautiful, & sometimes essential, eg I plan to hitch another small old toshiba libretto in a waterproof box to use parallel port to drive stepper motors for a satellite dish. I master disk images & trees for such old boxes, mounted on more modern FreeBSD, but common fdisk is nice on host & target. I also use fdisk maintained MBR on eg USB sticks on key ring, combining rescue & install partitions of new BSD + backup of encrypted data, + A DOS slice for export import for non BSD world. MBR via fdisk is a familiar comfort in a world of variant OS's. BSD people who've wrestled with weird Linux boot stuff may sypathise with the idea if retaining familiar fdisk for non latest BSD people. But if people really espouse tangible benefit to kicking fdisk out of src/, I just hope same people first copy fdisk in to ports/ before out of src/ Cheers, -- Julian Stacey. Arm Ukraine. Contraception V Global heating & resource wars. Gmail & Googlemail Fail http://berklix.org/jhs/mail/#bad