On 2021-06-08 04:41, Zygo Blaxell wrote:
> On Sun, Jun 06, 2021 at 10:47:05PM -0700, Paul Eggert wrote:
>> On 6/5/21 10:42 PM, Zygo Blaxell wrote:
>>> If cp -a implements the inode attribute propagation (or
inheritance), then
>>> only users of cp -a are impacted. They are more likely to be awa
On 2021-06-08 04:41, Zygo Blaxell wrote:
On Sun, Jun 06, 2021 at 10:47:05PM -0700, Paul Eggert wrote:
On 6/5/21 10:42 PM, Zygo Blaxell wrote:
If cp -a implements the inode attribute propagation (or inheritance), then
only users of cp -a are impacted. They are more likely to be aware that
the
On Sun, Jun 06, 2021 at 10:47:05PM -0700, Paul Eggert wrote:
> On 6/5/21 10:42 PM, Zygo Blaxell wrote:
> > If cp -a implements the inode attribute propagation (or inheritance), then
> > only users of cp -a are impacted. They are more likely to be aware that
> > they may be creating new files with
On 6/5/21 10:42 PM, Zygo Blaxell wrote:
If cp -a implements the inode attribute propagation (or inheritance), then
only users of cp -a are impacted. They are more likely to be aware that
they may be creating new files with reduced-integrity storage attributes.
True, although I think this aspec
I believe that /etc/fstab should not be subject to COW. We can have partitions
dynamically mounted by users
(noauto,user on the fstab line).
/boot/efi must be protected as well. Sometimes this directory is redirected.
I have experienced cow issues with system reboots. Then running btrfs to
On Sat, Jun 05, 2021 at 01:56:49PM +0800, Tom Yan wrote:
> As far as I'm concerned, inheriting an attribute from the source inode
> isn't a "surprising" behavior. Rather it seems pretty "natural" to me.
> And I don't think whether the attribute is "dangerous" changes that,
> because if you consider
On 2021-06-05 07:56, Tom Yan wrote:
As far as I'm concerned, inheriting an attribute from the source inode
isn't a "surprising" behavior. Rather it seems pretty "natural" to me.
And I don't think whether the attribute is "dangerous" changes that,
because if you consider it "dangerous", shouldn
As far as I'm concerned, inheriting an attribute from the source inode
isn't a "surprising" behavior. Rather it seems pretty "natural" to me.
And I don't think whether the attribute is "dangerous" changes that,
because if you consider it "dangerous", shouldn't you "watch out"
anyway when you try to
On Fri, Jun 04, 2021 at 10:37:35PM +0800, Tom Yan wrote:
> Also cc'ing bug-coreutils@gnu.org.
>
> On Fri, 4 Jun 2021 at 22:33, Tom Yan wrote:
> >
> > Hi all,
> >
> > I've just bumped into a problem that I am not sure what the expected
> > behavior should be, but there seems to be something flawed
Also cc'ing bug-coreutils@gnu.org.
On Fri, 4 Jun 2021 at 22:33, Tom Yan wrote:
>
> Hi all,
>
> I've just bumped into a problem that I am not sure what the expected
> behavior should be, but there seems to be something flawed.
>
> Say I have a file that was created with the No_COW attributed
> (in
10 matches
Mail list logo
