From nobody Thu Jan 25 15:50:31 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 4TLQJx5Brgz57Vpg
	for <freebsd-current@mlmmj.nyi.freebsd.org>; Thu, 25 Jan 2024 15:50:41 +0000 (UTC)
	(envelope-from freebsd@igalic.co)
Received: from mail-4323.proton.ch (mail-4323.proton.ch [185.70.43.23])
	(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 (4096 bits) client-digest SHA256)
	(Client CN "protonmail.com", Issuer "R3" (verified OK))
	by mx1.freebsd.org (Postfix) with ESMTPS id 4TLQJx3C2Wz4xp8
	for <freebsd-current@freebsd.org>; Thu, 25 Jan 2024 15:50:41 +0000 (UTC)
	(envelope-from freebsd@igalic.co)
Authentication-Results: mx1.freebsd.org;
	none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=igalic.co;
	s=protonmail3; t=1706197837; x=1706457037;
	bh=5HM4e7UMixhg0nRvty63Ak5rUqnvWqhruvCctmKX5LI=;
	h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References:
	 Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
	 Message-ID:BIMI-Selector;
	b=U3CSoendpUkCyEN7xi0bc9aBXwvV5n92Ll3muglNQA7otOsYhQ7dp0w/ZDroPygP4
	 FreThOD7HRZgUY4d3b0Z3wRcORefz0iWxA9ixwKf83vwznsEBw0kX800+3Ca7eOoMr
	 l1zbLukOW8qE/5jLYruK/Ng3MH4p76zysq2kGrLqkaCrpZk5+5DtTYLh6r4CVGcreJ
	 e7HEJ79PooMmdaWOCUGCCtGmB+MIyL2EL3gTg16QtmdksR6ze1EnKWqey7tMDeo/Cm
	 u4P+z4VTSwVK1fq4OsgVex+F/dfeNXu7HmKBd+toHQejg3gHFD6HWsvPdbG2D6cnE6
	 1EUHyS0pRa5+A==
Date: Thu, 25 Jan 2024 15:50:31 +0000
To: "emaste@freebsd.org" <emaste@freebsd.org>, "imp@bsdimp.com" <imp@bsdimp.com>
From: =?utf-8?Q?Mina_Gali=C4=87?= <freebsd@igalic.co>
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: Re: Removing fdisk and bsdlabel (legacy partition tools)
Message-ID: <E0wRsk-5NPyMz16fk2lz8i2tYZ38T-gSOa_iAFsN8frOlYG8HxFJW-ZXHhGydmtQJGwNo8vXIaJXz2ZkEoee_9gslehz85geiD45zqRlbpk=@igalic.co>
In-Reply-To: <CAPyFy2AmNmc54G66XHCnaZkgsDcbJT+pCi0ys=YVrPUTkX8BYQ@mail.gmail.com>
References: <CAPyFy2CK0Vq8U6J-H4XU3pNA33-uKAxUoNOAbM9SdSFa0Bcqkg@mail.gmail.com> <CANCZdfoYEJvp3R+e=+=Brm=WmRTPxeOooS004dnNLupjQnodEw@mail.gmail.com> <CAPyFy2AmNmc54G66XHCnaZkgsDcbJT+pCi0ys=YVrPUTkX8BYQ@mail.gmail.com>
Feedback-ID: 66573723:user:proton
List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-current
List-Help: <mailto:freebsd-current+help@freebsd.org>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Subscribe: <mailto:freebsd-current+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-current+unsubscribe@freebsd.org>
Sender: owner-freebsd-current@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Rspamd-Queue-Id: 4TLQJx3C2Wz4xp8
X-Spamd-Bar: ----
X-Rspamd-Pre-Result: action=no action;
	module=replies;
	Message is reply to one we originated
X-Spamd-Result: default: False [-4.00 / 15.00];
	REPLY(-4.00)[];
	ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH]


>  > Those are the only users in the tree, but not for long :)
> =20
>  I have some reviews open to remove some old fdisk / diskabel /
>  bsdlabel invocations from the tree.
> =20
>  With those applied, for fdisk I see the following references
>  (excluding sbin/fdisk/* and comments, old examples, etc.):
> =20
>  contrib/netbsd-tests/sbin/gpt/t_gpt.sh
>  tests/sys/cddl/zfs/bin/zpool_smi.ksh
> =20
>  For bsdlabel / disklabel:
> =20
>  sbin/growfs/tests/legacy_test.pl
>  tools/regression/msdosfs/msdosfstest-2.sh
>  tools/regression/tmpfs/t_vnd
>  tools/tools/nanobsd/legacy.sh
>  contrib/netbsd-tests/kernel/t_umount.sh
>  contrib/netbsd-tests/kernel/t_umountstress.sh
>  contrib/netbsd-tests/sbin/gpt/t_gpt.sh
>  sbin/newfs/runtest00.sh
>  sbin/newfs/runtest01.sh

i was looking at cd(4) today, and to my surprise, it was full of disklabel =
references.
I haven't looked at the code itself yet, to see how far the documentation h=
as drifted apart from reality, but to most users, our documentation is real=
ity.