From: David Sterba <dsterba@suse.cz>
To: Petr Bena <benapetr@gmail.com>
Cc: Hugo Mills <hugo@carfax.org.uk>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: New tool to recursive compress / decompress of files
Date: Wed, 25 Mar 2015 02:49:06 +0100 [thread overview]
Message-ID: <20150325014906.GD20767@twin.jikos.cz> (raw)
In-Reply-To: <CA+4EQ5chrXyaoLs09TdK09npfCxvLKDTZor5Bqc9wqqX3xpKkA@mail.gmail.com>
On Sat, Mar 21, 2015 at 07:16:47PM +0100, Petr Bena wrote:
> I am just wondering, does that defragment trick work for non-root users?
Defragmentation works where read and write would work for the user. Root
can also defrag files that do not have the wite rwx bit set, but it's a
special case anyway.
> Also, even if it did work, I could as well make my tools use this
> defragment trick instead, because I will probably never remember that
> hacky syntax of defrag command :P doing something like compress -r
> <folder> or decompress -r <folder> is just much more easy to remember
> than multiple commands.
The tools should provide a rich set of options to do basic operations
and could provide options to do complex things, but writing wrappers is
sometimes inevitable.
In your case, we can enhance the defrag command to set the +c bit on
directories/files on the way, plus set the compression method via
properties according to the user selected method. All of this fits into
the idea of core tool support.
next prev parent reply other threads:[~2015-03-25 1:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 17:56 New tool to recursive compress / decompress of files Petr Bena
2015-03-21 18:08 ` Hugo Mills
2015-03-21 18:12 ` Petr Bena
2015-03-21 18:16 ` Petr Bena
2015-03-25 1:49 ` David Sterba [this message]
2015-03-25 1:42 ` David Sterba
2015-03-21 18:22 ` Roman Mamedov
2015-03-21 18:25 ` Petr Bena
2015-03-21 18:26 ` Petr Bena
2015-03-21 19:27 ` Marc MERLIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150325014906.GD20767@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=benapetr@gmail.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.