4 ms·

Apple is moving towards forbidding write access to system directories, for example: sudo mv /bin/echo /bin/e mv: rename echo to e: Operation not permit

Apple is moving towards forbidding write access to system directories, for example: sudo mv /bin/echo /bin/e mv: rename echo to e: Operation not permitted I'm not sure if this is getting close to falling foul of the GPL v3 -- if I can't replace these files, is that a problem?

pohl 10y ago
Rather than replacing it, why not write it under /usr/local and edit your PATH?
- CJefferson 10y ago
  Oh, I certainly could (and do for bash), but I believe the GPL v3 requires that you can replace any copies of programs with your own, which possibly Apple might worry they fall foul of, which might be why they don't want GPL v3 software (I'm guessing).
colejohnson66 10y ago
Is there anything stopping you from booting into Linux to rename it, is there? Like how I can't delete files owned by SYSTEM on Windows, but can on Linux?
- koenigdavidmj 10y ago
  You can even unset this within macOS; it just requires a reboot: 1. Hold Cmd-R as you reboot. That puts you in recovery mode. 2. Bring up a terminal. 3. Run 'csrutil disable' 4. Reboot back into regular mode
- cmurf 10y ago
  Yes. Linux has no support for Core Storage, which is now used in default macOS layouts. So any hfsplus volume on Core Storage is rendered effectively not readable on an OS other than macOS, even if it's not encrypted.
spullara 10y ago
That is System Integrity Protection implemented in the latest operating system: https://support.apple.com/en-us/HT204899 https://support.apple.com/en-us/HT204899 It is possible to disable it and even if you couldn't I don't think it has any impact on licensing.
- dragonwriter 10y ago
  If you couldn't, it would conflict with the "anti-tivoization" rules applicable to "User Products" in the GPLv3, which requires that any GPLv3 code incorporated into a "User Product" is replaceable with modified versions, and that the manufacturer of the product provide all information necessary to the user to make that replacement.
  - spullara 10y ago
    Hmm. Isn't it replaceable by changing the PATH and installing them in non-System Integrity areas of the operating system like /usr/local/bin?

pohl 10y ago

Rather than replacing it, why not write it under /usr/local and edit your PATH?

CJefferson 10y ago
Oh, I certainly could (and do for bash), but I believe the GPL v3 requires that you can replace any copies of programs with your own, which possibly Apple might worry they fall foul of, which might be why they don't want GPL v3 software (I'm guessing).

colejohnson66 10y ago

Is there anything stopping you from booting into Linux to rename it, is there? Like how I can't delete files owned by SYSTEM on Windows, but can on Linux?

koenigdavidmj 10y ago
You can even unset this within macOS; it just requires a reboot: 1. Hold Cmd-R as you reboot. That puts you in recovery mode. 2. Bring up a terminal. 3. Run 'csrutil disable' 4. Reboot back into regular mode
cmurf 10y ago
Yes. Linux has no support for Core Storage, which is now used in default macOS layouts. So any hfsplus volume on Core Storage is rendered effectively not readable on an OS other than macOS, even if it's not encrypted.

spullara 10y ago

That is System Integrity Protection implemented in the latest operating system: https://support.apple.com/en-us/HT204899 https://support.apple.com/en-us/HT204899 It is possible to disable it and even if you couldn't I don't think it has any impact on licensing.

dragonwriter 10y ago
If you couldn't, it would conflict with the "anti-tivoization" rules applicable to "User Products" in the GPLv3, which requires that any GPLv3 code incorporated into a "User Product" is replaceable with modified versions, and that the manufacturer of the product provide all information necessary to the user to make that replacement.
- spullara 10y ago
  Hmm. Isn't it replaceable by changing the PATH and installing them in non-System Integrity areas of the operating system like /usr/local/bin?