Install - Revision history

Lundman: /* Initial installation from source */

2020-08-20T07:41:04Z

‎Initial installation from source

2020-06-04T12:56:44Z

‎Installing the official release: add link to Bash_completion page

2020-06-03T16:27:30Z

update brew install command to the current one on brew.sh

2020-05-03T00:10:35Z

2020-05-03T00:09:41Z

2019-09-06T02:06:39Z

‎Initial installation from source

2019-01-08T18:28:45Z

‎Initial installation from source: Deleted second instance of an unnecessarily doubled word

2018-12-06T15:10:20Z

‎Initial installation from source

2017-02-10T15:10:03Z

‎Installing from source

2017-02-10T15:08:27Z

‎Installing from source

@@ Line 25: / Line 25: @@
 == Installing from source ==
 ===Initial installation from source===
 Before doing anything else, please set your boot-args.

← Older revision		Revision as of 12:56, 4 June 2020
Line 18:		Line 18:

	Follow the prompts.		Follow the prompts.
		+
		+	Bash completion is also available: see [[Bash_completion]] page

	If you ever want to uninstall, follow the instructions for [[Uninstall#Uninstalling_a_release_version\|uninstalling a release version]].		If you ever want to uninstall, follow the instructions for [[Uninstall#Uninstalling_a_release_version\|uninstalling a release version]].

@@ Line 84: / Line 84: @@
 <syntaxhighlight lang="bash">
-ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
+/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
 </syntaxhighlight>

@@ Line 40: / Line 40: @@
 If you are a developer, you may want <code>debug=0x144</code> in your boot-args as well, as explained here: [[Development]]
 Tips for getting into recovery mode, useful if developing on a VM, type the following commands in a shell in the guest VM:
@@ Line 46: / Line 47: @@
 sudo reboot recovery
 </syntaxhighlight>
 For macOS Sierra (10.12) and OS X El Capitan (10.11), you also need to boot into the Recovery OS (either the Recovery partition or bootable OS X install media for 10.11) and run

← Older revision		Revision as of 00:09, 3 May 2020
Line 41:		Line 41:
	If you are a developer, you may want <code>debug=0x144</code> in your boot-args as well, as explained here: [[Development]]		If you are a developer, you may want <code>debug=0x144</code> in your boot-args as well, as explained here: [[Development]]

		+	Tips for getting into recovery mode, useful if developing on a VM, type the following commands in a shell in the guest VM:
		+	<syntaxhighlight lang="bash">
		+	sudo nvram "recovery-boot-mode=unused"
		+	sudo reboot recovery
		+	</syntaxhighlight>

	For macOS Sierra (10.12) and OS X El Capitan (10.11), you also need to boot into the Recovery OS (either the Recovery partition or bootable OS X install media for 10.11) and run		For macOS Sierra (10.12) and OS X El Capitan (10.11), you also need to boot into the Recovery OS (either the Recovery partition or bootable OS X install media for 10.11) and run

@@ Line 52: / Line 52: @@
 The latter will allow you to load your custom-built, unsigned kernel extensions, while keeping the rest of System Integrity Protection (SIP) in place.
 (Depending on your needs, other options you may want are <code>--without fs</code>, <code>--without debug</code>, <code>--without dtrace</code>, or <code>--without nvram</code>. If you specify all of them, that is equivalent to <code>csrutil disable</code>. The <code>--without</code> option takes a comma-delimited list or can be specified multiple times: <code>--without kext,debug,dtrace</code> is equivalent to <code>--without kext --without debug --without dtrace</code>).
 If you have any other implementation of ZFS installed, you must uninstall it and reboot before proceeding further. Similarly, if you have installed the O3X installer version, please follow the [https://openzfsonosx.org/wiki/Uninstall uninstallation directions] before proceeding.

← Older revision		Revision as of 18:28, 8 January 2019
Line 37:		Line 37:


−	This will take effect the next time you reboot. The argument <code>-v</code> will make your boot screen verbose instead of just showing the Apple logo, the argument <code>keepsyms=1</code> will make your panic reports more useful for us, and the argument <code>kext-dev-mode=1</code> (OS X Yosemite ONLY) will allow you to load your custom-built, unsigned kexts kernel extensions. Note that as of OS X El Capitan, kext-dev-mode is obsolete ~~and~~ and does nothing. If you are on macOS Sierra (10.12) or OS X El Capitan, you should remove kext-dev-mode from your boot-args to avoid confusion.	+	This will take effect the next time you reboot. The argument <code>-v</code> will make your boot screen verbose instead of just showing the Apple logo, the argument <code>keepsyms=1</code> will make your panic reports more useful for us, and the argument <code>kext-dev-mode=1</code> (OS X Yosemite ONLY) will allow you to load your custom-built, unsigned kexts kernel extensions. Note that as of OS X El Capitan, kext-dev-mode is obsolete and does nothing. If you are on macOS Sierra (10.12) or OS X El Capitan, you should remove kext-dev-mode from your boot-args to avoid confusion.

	If you are a developer, you may want <code>debug=0x144</code> in your boot-args as well, as explained here: [[Development]]		If you are a developer, you may want <code>debug=0x144</code> in your boot-args as well, as explained here: [[Development]]

@@ Line 26: / Line 26: @@
 Before doing anything else, please set your boot-args.
-On macOS Sierra (10.12), OS X El Capitan (10.11), OS X Mavericks (10.9), and OS X Mountain Lion (10.8) :
+On macOS Mojave (10.14), High Sierra (10.13), Sierra (10.12), OS X El Capitan (10.11), OS X Mavericks (10.9), and OS X Mountain Lion (10.8) :
 <syntaxhighlight lang="bash">
 sudo nvram boot-args="-v keepsyms=1"

@@ Line 61: / Line 61: @@
 * [http://brew.sh/ Homebrew] (or [http://www.macports.org/ MacPorts])
-Note: Xcode 6.3 or later is now required to build due to Broadwell CPU support requirements. Additionally, as of XCode 8, if you are on 10.11, you need to install the CLT (Command Line Tools):
+Note: Xcode 6.3 or later is now required to build due to Broadwell CPU support requirements. Additionally, as of XCode 8, if you are on 10.11 specifically (unnecessary on 10.12), you need to install the CLT (Command Line Tools):
 <syntaxhighlight lang="bash">