[PATCH v3 01/18] fsadm: Add new commands create, list, add and remove

[Alasdair G Kergon <agk@redhat.com>]

On Wed, Oct 05, 2011 at 11:46:45AM +0200, Lukas Czerner wrote:
> On Wed, 5 Oct 2011, Zdenek Kabelac wrote:
> > Dne 5.10.2011 10:02, Lukas Czerner napsal(a):
> > > On Tue, 4 Oct 2011, Zdenek Kabelac wrote:
> > > > Dne 4.10.2011 14:13, Lukas Czerner napsal(a):
> > > > > On Tue, 4 Oct 2011, Zdenek Kabelac wrote:
 
You both lost me several messages ago!

For *changes* to functionality, what I'm looking for is:

  Description of how it works today in *all* relevant code paths/option
combinations/invocation methods;

  Description/explanation of how it will work *after* the change has been made
in all the same cases as now plus any new ones

Explanation of/justification for the difference.

Currently in lvm:

  --yes is meant to mean 'answer yes to all questions'
These are generally informative questions telling the user what the tool will do
and seeking confirmation.  On its own, they should not be dangerous or risk
corruption.  Example: removing an LV that is active but not currently being used.
The idea of such questions is to point out to the user the actual consequences
of the command to help to make sure they understand what will happen.

  --force is meant to mean 'permit operations that might not always be wise but
sometimes do need to be done - assume the user knows what they are doing'.
Normally a warning of what will happen is issued and confirmation is required,
but --yes can be used to avoid that confirmation.

For dangerous things that wouldn't normally make sense but occasionally can be
justified, like destroying PVs while they are in (inactive) VGs, --force can be
required to be repeated twice.


Now, let's try to understand:
  How these options are currently used in fsadm-related tools;
  What's good/bad here and perhaps ought to change.

Alasdair