System Integrity Protection was introduced in El Capitan to add another layer of security to OS X. The system prevents the root user from doing things that are potentially harmful. Apple did this because any app at any time may ask for the administrator password and execute commands with elevated permissions, which is a big security risk on single user systems.
There are downsides to yet another layer of security, and much like Gate Keeper, System Integrity Protection brings us one step closer to a completely locked off system like iOS. I guess that’s the long term plan.
Until then, and if you need it, you can disable System Integrity Protection. Here’s how to do it:
boot into the Recovery Partition (hold down CMD + R during boot)
this takes a little longer than usual
when the system is back, select Utilities – Terminal
now type “csrutil disable”
close Terminal and restart the system
You can check at any time if this feature is on or off by typing
Enable it again during a Recovery session by typing “csrutil enable” and El Capitan is secured again.
To see what else this command has to offer, type csrutil without parameters:
Modifythe SystemIntegrityProtectionconfiguration.Allconfiguration changes apply to the entire machine.
Sometimes it’s important that things change for no apparent reason. You know, the way they move things around in supermarkets just to drive you crazy.
If you’ve tried burning an ISO image to disk in El Capitan recently, you know what I’m talking about:
because the option to burn an ISO has been removed from Disk Utility.
Yeah, I get it: plastic disks are out, no one should be using them anymore, there are no more Macs with SuperDrives in production as of 2016, so it’s time to remove this option from the built-in utility that had it for the last ten years. Think different. It keeps you sharp.
Lucky for us plastic spinners, there are two (not so obvious) solutions: the command line and the good old Finder that can still burn disks for us. Here’s how to do it.
Apparently Finder always had the option to burn a disk image. I never knew that! All we have to do is:
Apple have a new System Font in El Capitan and all of their other products starting 2015: it’s called San Francisco. It’s very similar to their previous font Helvetica Neue, but apparently San Francisco is better for your eyes (not to mention the fact that Helvetica Neue isn’t owned by Apple, and obviously we can’t have that).
If you’ve tried searching for San Francisco on your Mac’s Font Book app, you’ll notice that it doesn’t seem to exist. Likewise, if you’re trying to use it in CSS it won’t work.
Thanks to Craig Hockenberry I now know that this is because Apple haven’t exposed the font the usual way; rather, it can be used in web content and via CSS with a new property they’ve introduced. Here’s how:
Replace body with your own CSS property, and on Apple devices running El Capitan, iOS 9, watchOS2 or tvOS, your web views will sport San Francisco. Other devices will show Helvetica Neue when installed, or use a generic sans-serif font.
Read Craig’s post for more information: http://furbo.org/2015/07/09/i-left-my-system-fonts-in-san-francisco/
Check out Apple’s Surfin’ Safari post on this topic: https://www.webkit.org/blog/3709/using-the-system-font-in-web-content/
Download this font for your own projects: https://developer.apple.com/fonts/ (license required)
Ever wondered if there’s a difference in overhead and memory usage when you’re using a VM instead of OS X directly? Here’s a comparison for website hosting.
The above graph shows the difference of hosting one of my websites for the last few days on OS X Server (in blue) that I got from Hostgator (using their HostGator Thanksgiving Deal 2016 coupon), and in a CentOS VM under Parallels Desktop 10 on the same hardware (in red).
The traffic logs show that the amount of requests and visitors has remained the same, so we can deduce that the load put on either OS X and the VM is the same. There is a little more overhead when using the VM, but not as much as I had feared: the requests have to be forwarded to another software layer after all, and that takes some CPU power.