[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190321143225.GC9434@mit.edu>
Date: Thu, 21 Mar 2019 10:32:26 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: Lukas Czerner <lczerner@...hat.com>
Cc: Ext4 Developers List <linux-ext4@...r.kernel.org>,
darrick.wong@...cle.com
Subject: Re: [PATCH 5/9] e2fscrub: add the -n option which shows what
commands e2scrub would execute
On Thu, Mar 21, 2019 at 11:57:51AM +0100, Lukas Czerner wrote:
> On Wed, Mar 20, 2019 at 10:02:14PM -0400, Theodore Ts'o wrote:
> > Signed-off-by: Theodore Ts'o <tytso@....edu>
> > ---
> > scrub/e2scrub.8.in | 5 +++++
> > scrub/e2scrub.in | 6 ++++--
> > 2 files changed, 9 insertions(+), 2 deletions(-)
> >
> > diff --git a/scrub/e2scrub.8.in b/scrub/e2scrub.8.in
> > index ff03523e3..7342876a3 100644
> > --- a/scrub/e2scrub.8.in
> > +++ b/scrub/e2scrub.8.in
> > @@ -38,6 +38,11 @@ If the filesystem is not repaired,
> > will be run before the next mount.
> > .SH OPTIONS
> > .TP
> > +\fB-n\fR
> > +Print what commands
> > +.B e2scrub
> > +would execute (but don't actually execute them).
>
> We should be a bit more clear that it's not all the commands that will
> be printed but not executed. Some of commands, like lsblk and lvs will
> actually be executed so it's not like you can run this without proper
> privledges.
>
> It sounds nit-picky, and obvious to us, but I am sure someone will
> complaing about this.
Good point, I'll fix this.
- Ted
Powered by blists - more mailing lists