In message <2369865.bDOn7JOVgO@ravel>, Olivier Certner writes:
> --nextPart5823302.8T7jmnknE8
> Content-Transfer-Encoding: 7Bit
> Content-Type: text/plain; charset="UTF-8"; protected-headers="v1"
> From: Olivier Certner <o...@freebsd.org>
> To: Cy Schubert <cy.schub...@cschubert.com>
> Subject: Re: Removing fdisk and bsdlabel (legacy partition tools)
> Date: Thu, 25 Jan 2024 10:43:18 +0100
> Message-ID: <2369865.bDOn7JOVgO@ravel>
> In-Reply-To: <20240125055019.ccf1...@slippy.cwsent.com>
> MIME-Version: 1.0
>
> Hi,
>
> > A visual view of columns of a bsdlabel, editing a label using vi, checking
> > and double checking numbers before committing them is handy.The visual
> > format and the ability to adjust the numbers in an editor before committing
>
> > them is handy. You can't do this with gpart, as it's transactional. And
> > bsdinstall doesn't give one the opportunity to check the numbers in detail
> > on a console before committing them.
>
> You seem to want to be able to stack a number of modifications before actuall
> y pushing them. Actually, gpart(8) already can do that! Please see the "OPE
> RATIONAL FLAGS" section in gpart(8).
>
> In between your tentative modifications, just use 'gpart show' to see where y
> ou stand.
gpart(8) should have a vi mode. That is different than having changes
pending and committing them. A person is still entering commands rather
than doing something like editing a spreadsheet, which is what editing a
file is kind-of like. Even something like,
gpart show ada0s2 > some_file
vi some_file
gpart batch ada0s2 < some_file
--
Cheers,
Cy Schubert <cy.schub...@cschubert.com>
FreeBSD UNIX: <c...@freebsd.org> Web: https://FreeBSD.org
NTP: <c...@nwtime.org> Web: https://nwtime.org
e^(i*pi)+1=0
