From 972f41efb778d22e3a8bd52080918a56d9127dc4 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 24 Feb 2022 13:05:25 -0400 Subject: [PATCH] comment --- ...ent_3_223df2a9cebd99a312537137863b1781._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/can__39__t_make_annex_happy_in_freeze__47__thaw/comment_3_223df2a9cebd99a312537137863b1781._comment diff --git a/doc/bugs/can__39__t_make_annex_happy_in_freeze__47__thaw/comment_3_223df2a9cebd99a312537137863b1781._comment b/doc/bugs/can__39__t_make_annex_happy_in_freeze__47__thaw/comment_3_223df2a9cebd99a312537137863b1781._comment new file mode 100644 index 0000000000..6c16581c19 --- /dev/null +++ b/doc/bugs/can__39__t_make_annex_happy_in_freeze__47__thaw/comment_3_223df2a9cebd99a312537137863b1781._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2022-02-24T16:34:51Z" + content=""" +Looks like, while init does run the freeze hook in its test, +as well as trying to remove the write bits (which it always does, freeze +hook or no freeze hook), it still checks if the file's write permissions +got removed. + +I think that, in order to support filesystems where chmod -w has no effect, +init should skip looking at perms when there is a freeze hook. It can +still check that freezing prevents writing to a file. +"""]] -- 2.30.2