Homebrew & El Capitan. GitHub Gist: instantly share code, notes, and snippets. Homebrew complements macOS (or your Linux system). Install your RubyGems with gem and their dependencies with brew. “To install, drag this icon” no more. Homebrew Cask installs macOS apps, fonts and plugins and other non-open source software. $ brew install -cask firefox. Making a cask is as simple as creating a formula. Option 2: Uninstalling Homebrew with the Uninstall Script Manually. If you don’t like the idea of executing a script downloaded from the internet with curl (which is understandable for security conscious individuals), then you can also view, download, and review the uninstall script beforehand, and then execute it manually on the computer that you wish to remove Homebrew from. Homebrew & El Capitan. GitHub Gist: instantly share code, notes, and snippets.
NTFS support in OS X is disappointing. You plug in a USB flash drive from a co-worker who uses Windows to simply copy over a file, only to realize that you can't actually write to NTFS-formatted drives on Mac out of the box.
That's kind of lame, to be honest. It's 2016, Apple, wake up! People who work together in the same office, on different operating systems, should be able to exchange files via USB flash drive with ease, without having to worry about formatting their drives with a cross-platform filesystem, like exFAT.
Solutions
There are a few ways to enable NTFS write support on OS X.
- Using the built-in NTFS drivers - Writing to NTFS drives is a functionality that's been built into OS X for some time. However, it's disabled by default for NTFS volumes, and for good reason. It's extremely buggy and corrupts entire volumes in certain situations. I tried copying 4GB worth of data to an NTFS volume this way, and the transfer just failed half-way, rendering the disk inaccessible and my computer unbootable, until I manually disconnected the SATA cable from the hard drive. Luckily, hot-plugging the drive to Windows 7 and running
dskchkfixed the issue, but other people reported losing all of their data because of these faulty drivers. Therefore, I strongly advise against this method. - Purchasing Tuxera/Paragon NTFS for Mac - A viable option, albeit quite expensive (Tuxera - $26.50, Paragon - $19.95), at least for something that should already be included with the OS. I shouldn't have to pay good money to be able to write to an NTFS volume. There has to be another way.
- Downloading and installing OSXFUSE and NTFS-3G - The winning option. NTFS-3G is an NTFS read/write driver that is free and open-source, and there don't seem to be any corruption issues arising from using it.
Installing OSXFUSE
So, what is OSXFUSE anyway?
FUSE for OS X allows you to extend OS X's native file handling capabilities via third-party file systems. As a user, installing the OSXFUSE software package will let you use any third-party file system written atop OSXFUSE or MacFUSE, if you choose to install the MacFUSE compatibility layer.
So basically, it's a way for developers to extend OS X's native file handling APIs to other file systems.
It's required by NTFS-3G, so let's go ahead and install the latest OSXFUSE (3.x.x) from here:
https://github.com/osxfuse/osxfuse/releases
Homebrew Mac Os El Capitan
Download the latest osxfuse-3.x.x.dmg attachment, mount it, and install it, as with any other .dmg.
Note: Make sure to select the MacFUSE Compatibility Layer in the installation options. NTFS-3G depends on it.
Installing NTFS-3G
Once that's done, we can go ahead and install NTFS-3G. But not so fast, we need Homebrew for that.
Verify that you have Homebrew installed by running:
If you don't, install it using this one-liner:
In any case, go ahead and update the Homebrew formula:
Next, let's finally install NTFS-3G via Homebrew:
Replacing Mount_NTFS
To get NTFS-3G to work, we need to replace the built-in /sbin/mount_ntfs binary, which is linked to Apple's NTFS driver, with NTFS-3G's mount_ntfs.
This was a pretty easy thing to do before OS X 10.11 El Capitan, but due to System Integrity Protection, it is now slightly harder.
System Integrity Protection is a security technology in OS X El Capitan that's designed to help prevent potentially malicious software from modifying protected files and folders on your Mac.
It restricts the root account and limits the actions that the root user can perform on protected parts of OS X.
Therefore, we can't simply swap out the binary by using sudo and running ln. That is, not until we disable System Integrity Protection.
Disabling SIP
Reboot your Mac, and hold Cmd + R to enter Recovery mode. Within the Terminal, enter the following command to disable SIP and reboot back into OS X:
Replacing the Binary Link
Boot into OS X, and open a Terminal window. Within the Terminal, enter the following commands to swap out the link to the native mount_ntfs binary with a link to NTFS-3G's mount_ntfs binary:
Re-enabling SIP
Reboot into Recovery mode again, this time, to re-enable SIP. Within the Terminal, enter the following command to enable SIP and reboot back into OS X:
That's It!
NTFS-3G will automatically mount your NTFS volumes in read-and-write mode once you reboot back into OS X. Go ahead and copy some files over to an NTFS volume to make sure it works. Well done!
You upgraded to Mac OS X El Capitan and cannot use Homebrew anymore. As a developer myself who uses homebrew pretty regularly, I can totally understand the feeling.
The reason these permission issues are arising is a result of Apple's new changes to Mac OS X 10.11 El Capitan called SIP which stands for System Integrity Protector. More about SIP towards the end of this article.
Here is how you can fix the permission issues with Homebrew in Mac OS X El Capitan:
If you had created the /usr/local directory already, then run this command in terminal:
sudo chown $(whoami):admin /usr/local && sudo chown -R $(whoami):admin /usr/local
And you should be all set.
Update - I have created this new guide titled - How to install Homebrew in Mac OS X El Capitan?
However, If you are doing a fresh install or cannot create /usr/local directory anymore, then follow these steps:
Step 1: Reboot into Recovery mode (Hold Cmd+R on boot) & access the Terminal. (Yes, you will have to go into recovery mode as that is the only way to disable SIP as of now.)
Step 2: In the terminal, run the following command:
csrutil disable
Step 3: Reboot back into OS X El Capitan
Homebrew El Capitan Software
Step 4: Once Mac restarts, Open your Terminal and run the following command:
sudo mkdir /usr/local && sudo chflags norestricted /usr/local && sudo chown $(whoami):admin /usr/local && sudo chown -R $(whoami):admin /usr/local
Step 5: After you have done above, you will need to reboot back into Recovery Mode once more & open the Terminal and type the following command:
csrutil enable
Step 6: Now, reboot back into OS X
Step 7: You will now be able to write to the /usr/local directory and proceed with installing Homebrew as you would regularly.
Homebrew El Capitan Game
Please Note:
You need not worry about any of the steps of issues that I outlined above if you have not installed Homebrew in /usr/local or another system-protected directory.
More about SIP - System Integrity Protector:
With SIP, you can no longer write to system directories like /usr , /System and /bin even though you have root permissions or you you have logged in as the user root.
According to the Apple documentation, the /usr/local directory will have the root:wheel restricted permissions like before with every forthcoming OS X update.
El Capitan Theatre Hollywood Ca
The Homebrew team has acknowledged this issue and they will soon be adding a brew doctor check that will warn you about any of these issues in the near future.
Homebrew El Capitan System
Thanks for reading and please let me know in the comments section, if this helped you.