Re: Possible to undo subvol delete?

[Austin S Hemmelgarn <ahferroin7@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2286 bytes --]

On 2014-12-04 09:06, Shriramana Sharma wrote:
> On Thu, Dec 4, 2014 at 12:23 AM, David Sterba <dsterba@suse.cz> wrote:
>> On Tue, Dec 02, 2014 at 08:45:10PM +0530, Shriramana Sharma wrote:
>>> On Tue, Dec 2, 2014 at 6:26 PM, David Sterba <dsterba@suse.cz> wrote:
>>>>
>>>> Works for me without the root password on a Tumbleweed installation
>>>> (without apparmor/selinux).
>>>
>>> Are you then referring to a btrfs partition mounted with user_subvol_rm_allowed?
>>
>> The context was 'does creating a subvolume require root password'.
>
> Well I don't know about you, but I'm just running an openSUSE 13.2
> system updated to Tumbleweed here, and even if I just hit "btrfs"
> enter (no sudo, no btrfs commands) on my regular (non-root) prompt, I
> am getting:
>
> $ btrfs
> Absolute path to 'btrfs' is '/usr/sbin/btrfs', so running it may
> require superuser privileges (eg. root).
> $
>
> ... so what to say of btrfs subvol, whether followed by crea or del!
>
> On Kubuntu Trusty, doing the above at least gives me the help list of
> btrfs subcommands and only when I try to execute some actual *action*
> which requires privileges (like accessing some root-read-only file or
> such) do I get an error message for not using sudo. For some (wierd)
> reason SuSE (possibly thinking it's being helpful) is requiring me to
> use sudo and enter password for even just *running* the btrfs
> executable. If there were a way to disable this and/or get the Kubuntu
> behaviour it'd be great (but of course this is not a SuSE forum!).
>
> What seems weird to me here is that it says it *may* require root
> privileges but simply drops me back to the prompt -- it doesn't seem
> to check whether the executable *actually* requires root permission.
> Granted, if it's under /sbin or /ust/sbin, it probably does, but the
> wording is quite strange, and the behaviour stranger.
>
AFAIK, the behavior is something in whatever patched version of whatever 
shell SuSE uses by default (IIRC, it's bash, but I'm not 100% certain 
about that).  I would go looking in /etc/profile and the other system 
wide startup files for that shell to see if you could override the 
behavior there.  It may also be something SELinux or file permissions 
related though.


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]