linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Pala <gotar@polanet.pl>
To: "Tomasz Kłoczko" <kloczko.tomasz@gmail.com>
Cc: Linux fs Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: your mail
Date: Sun, 18 Feb 2018 10:34:55 +0100	[thread overview]
Message-ID: <20180218093454.GA13420@polanet.pl> (raw)
In-Reply-To: <20180218092802.GA25085@polanet.pl>

On Sun, Feb 18, 2018 at 10:28:02 +0100, Tomasz Pala wrote:

> I've already noticed this problem on February 10th:
> [btrfs-progs] coreutils-like -i parameter, splitting permissions for various tasks
> 
> In short: not possible. Regular user can only create subvolumes.

Not possible "oficially". Axel Burri has replied with more helpful approach:
https://github.com/digint/btrfs-progs-btrbk

Unfortunately this issue was not picked up by any developer, so for now
we can only wait for splitting libbtrfsutil so this task could be easier.

-- 
Tomasz Pala <gotar@pld-linux.org>

  reply	other threads:[~2018-02-18  9:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-18  8:14 Tomasz Kłoczko
2018-02-18  9:28 ` your mail Tomasz Pala
2018-02-18  9:34   ` Tomasz Pala [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-01  2:02 Fennec Fox
2016-09-01  7:44 ` your mail M G Berberich
2016-09-01 11:17   ` Austin S. Hemmelgarn
2016-09-01 16:44     ` Kyle Gates
2016-09-01 17:06       ` Austin S. Hemmelgarn
2016-09-02  1:51       ` Jeff Mahoney
2016-09-01 21:15     ` M G Berberich
     [not found] <1330599216.71336.YahooMailNeo@web30703.mail.mud.yahoo.com>
2012-03-01 12:41 ` (unknown) bella tk
2012-03-01 12:58   ` your mail David Sterba
2012-03-01 14:26     ` Chris Mason
2011-09-20 15:24 (unknown) Ken D'Ambrosio
2011-09-20 15:35 ` your mail Hugo Mills
2011-09-20 15:40   ` Hugo Mills

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=20180218093454.GA13420@polanet.pl \
    --to=gotar@polanet.pl \
    --cc=kloczko.tomasz@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).