Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain;
        charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Subject: Re: ext4: Remove deprecated noacl/nouser_xattr options
From:   Patrik Schindler <poc@pocnet.net>
In-Reply-To: <20230117104525.kmbypv4vca6lbd5a@quack3>
Date:   Tue, 17 Jan 2023 11:55:18 +0100
Cc:     linux-ext4@vger.kernel.org, Ted Tso <tytso@mit.edu>
Content-Transfer-Encoding: quoted-printable
Message-Id: <06B5ADDC-D887-4C63-80BE-20950B7AAB75@pocnet.net>
References: <A5F622F8-99CF-4C7D-8811-7D82DB1C8846@pocnet.net>
 <20230116104254.xpphncpzu3zf53va@quack3>
 <3C7004E8-E732-40C1-B0DD-2A2290E43AC5@pocnet.net>
 <20230117104525.kmbypv4vca6lbd5a@quack3>
To:     Jan Kara <jack@suse.cz>
Precedence: bulk

Hello Jan,

Am 17.01.2023 um 11:45 schrieb Jan Kara <jack@suse.cz>:

> I understand the wish for more overview over file permissions but this =
seems like a bit awkward way to reach it?

This might be a matter of taste.

> It rather seems like a lack of control in the smbget(1) tool (or =
whatever you are using for the copying)?

Im using my Mac with macOS. I mount a samba share and use the Finder to =
copy files by drag & drop.

> Adding an option there to not copy permissions from the server would =
look like a very logical thing to do (similarly as cp(1) has these =
options)...  Would that work?

In this case: No, wouldn't work.

But your response made me wade through smb.conf(5) again, specifically =
searching for "acl" and found:

nt acl support =3D no

to be the adequate solution after trying. With that, copying files =
doesn't add ACLs anymore.

Sorry for bugging you and all the list members. Thank you for helping me =
think. :-)

:wq! PoC