Why are .nomount and .nosync files not checked for by default?
#143
Answered
by
abraunegg
RokeJulianLockhart
asked this question in
Q&A
-
|
As #141 (comment) describes:
Why isn't this enabled by default? |
Beta Was this translation helpful? Give feedback.
Answered by
abraunegg
Nov 21, 2023
Replies: 1 comment
-
Because it is a client side filtering rule that can be enabled by users - such as yourself. This is why it is not enabled by default are there are highly specific code operations (especially around |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
RokeJulianLockhart
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Because it is a client side filtering rule that can be enabled by users - such as yourself. This is why it is not enabled by default are there are highly specific code operations (especially around
.nomount) ... you have to understand why you are implementing that option + perform some very specific operating system modifications to use that option .... not everyone will be doing that ... thus not enabled by default.