6 ms·

It seems like when installing Nix, it needs to create a 'nix' directory in your root directory. While I haven’t tried installing Nix yet myself, I’m guessing th

by arm 10y ago

It seems like when installing Nix, it needs to create a 'nix' directory in your root directory. While I haven’t tried installing Nix yet myself, I’m guessing this probably won’t work on OS X v10.11 El Capitan due to System Integrity Protection¹. You’ll have to temporarily turn it off² first before attempting to install Nix (and then optionally turn it back on after). ―――――― ¹ — https://derflounder.wordpress.com/2015/10/01/system-integrity-protection-adding-another-layer-to-apples-security-model/ https://derflounder.wordpress.com/2015/10/01/system-integrit... ² — http://www.madrau.com/support/support/srx_1011.html http://www.madrau.com/support/support/srx_1011.html

cstrahan 10y ago
Ooh, that's an excellent point -- thanks for bringing it up. I've had Nix installed since early 2014, so I haven't run into any trouble with SIP yet. Looks like we might need to update our docs, and maybe have the installer give a helpful tip.
- Razengan 10y ago
  No need, `sudo mkdir /nix` works even with SIP enabled.
- Watabou 10y ago
  Unless /nix modifies files/folders, then no, you don't need to modify your install instructions. SIP only prevents users from modifying system level files. It does not prevent you from adding to, or deleting your own files within the `/` directory.
Razengan 10y ago
I have SIP enabled and I was able to install nix just by `sudo mkdir \nix` before installation. No problems.
Watabou 10y ago
Nope, System Integrity Protection only affects you if you delete/modify system level files. It does not prevent you from creating a `/nix` directory with regular root privileges, nor does it prevent you deleting it with root privileges. It's only when you try to delete something like /Library, that it then complains. This is one reason why I strongly believe SIP is blown out of proportion. I've used El Capitan since the betas and created root directories, deleted them, added to existing root directories without having to disable SIP. Again, it's only when you try to modify the built in directories inside / does it then complain, and frankly, I am more than happy with that, even with sudo privileges.

by arm 10y ago

cstrahan 10y ago

Ooh, that's an excellent point -- thanks for bringing it up. I've had Nix installed since early 2014, so I haven't run into any trouble with SIP yet. Looks like we might need to update our docs, and maybe have the installer give a helpful tip.

Razengan 10y ago
No need, `sudo mkdir /nix` works even with SIP enabled.
Watabou 10y ago
Unless /nix modifies files/folders, then no, you don't need to modify your install instructions. SIP only prevents users from modifying system level files. It does not prevent you from adding to, or deleting your own files within the `/` directory.

Razengan 10y ago

I have SIP enabled and I was able to install nix just by `sudo mkdir \nix` before installation. No problems.

Watabou 10y ago

Nope, System Integrity Protection only affects you if you delete/modify system level files. It does not prevent you from creating a `/nix` directory with regular root privileges, nor does it prevent you deleting it with root privileges. It's only when you try to delete something like /Library, that it then complains. This is one reason why I strongly believe SIP is blown out of proportion. I've used El Capitan since the betas and created root directories, deleted them, added to existing root directories without having to disable SIP. Again, it's only when you try to modify the built in directories inside / does it then complain, and frankly, I am more than happy with that, even with sudo privileges.