@@ -12,11 +12,14 @@ If you're a power user, you can run the Urbit virtual machine directly using the
12{% tab label="MacOS" %}
12{% tab label="MacOS" %}
17−curl -JLO https://urbit.org/install/mac/latest
15+curl -L https://urbit.org/install/mac/latest | tar xzk --strip=1 && ./urbit
18−tar zxvf ./darwin.tgz --strip=1
16+```
18+Note our Mac build is only compatible with Apple Silicon (M1/M2) via Rosetta.
19+If you have such a machine you must run the following command:
22+/usr/sbin/softwareupdate --install-rosetta --agree-to-license
@@ -24,18 +27,14 @@ tar zxvf ./darwin.tgz --strip=1
24{% tab label="Linux" %}
27{% tab label="Linux" %}
29−wget --content-disposition https://urbit.org/install/linux64/latest
30+curl -L https://urbit.org/install/linux64/latest | tar xzk --strip=1 && ./urbit
30−tar zxvf ./linux64.tgz --strip=1
34Linux users may need to run this command in another terminal window to access your Urbit on port 80:
33Linux users may need to run this command in another terminal window to access your Urbit on port 80:
37sudo apt-get install libcap2-bin
36sudo apt-get install libcap2-bin
38−sudo setcap 'cap_net_bind_service=+ep' ~/urbit/urbit
37+sudo setcap 'cap_net_bind_service=+ep' ./urbit
@@ -43,14 +42,15 @@ sudo setcap 'cap_net_bind_service=+ep' ~/urbit/urbit
43{% tab label="Windows" %}
42{% tab label="Windows" %}
45```winbatch
44```winbatch
46−mkdir %USERPROFILE%\urbit
47−cd %USERPROFILE%\urbit
48−curl -JLO https://urbit.org/install/windows/latest
45+curl -L https://urbit.org/install/windows/latest | tar -xzkf - --strip-components=1 && urbit
49−tar zxvf .\windows.tgz --strip=1
50−%USERPROFILE%\urbit\urbit
53−> Windows 10 build 17063 and later includes the familiar `curl` and `tar` command-line tools.
48+Windows 10 build 17063 and later includes the familiar `curl` and `tar`
49+command-line tools. If you're running an older version of Windows, you may need
51+[https://github.com/urbit/urbit/releases/latest](https://github.com/urbit/urbit/releases/latest)
52+in the browser, download the `windows.zip` file, extract it and execute the
53+contained `urbit.exe` file in the command prompt.
@@ -92,10 +92,10 @@ A comet name looks like `~dasres-ragnep-lislyt-ribpyl--mosnyx-bisdem-nidful-marz
95−To boot a comet, go into the command line and run the following command from the `urbit` directory you created during [Urbit installation](#os).
95+To boot a comet, go into the command line and run the following command:
98−~/urbit/urbit -c mycomet
98+./urbit -c mycomet
101It may take a while to load the comet (probably only take a few minutes, but it could take longer). This comes along with it being free. When it's done you'll some messages ending like this:
101It may take a while to load the comet (probably only take a few minutes, but it could take longer). This comes along with it being free. When it's done you'll some messages ending like this:
@@ -111,10 +111,10 @@ When your comet is finished booting, you will see `~sampel_marzod:dojo>` (Dojo:
112To exit Urbit, use `Ctrl-D` or enter `|exit` into Dojo.
112To exit Urbit, use `Ctrl-D` or enter `|exit` into Dojo.
114−To start your comet up again, run the following from your `urbit` directory (note the lack of `-c` argument):
114+To start your comet up again, run the following command:
117−~/urbit/urbit mycomet
117+./mycomet/.run
120### Using the web interface
120### Using the web interface
@@ -134,10 +134,10 @@ At the moment, the most common way to use Urbit is by launching apps like Groups
135Urbit comes with a recent release of the Urbit OS, but automatic updates of the `%base` desk (which contains the kernel of the OS) are not enabled by default for Comets. Many comets are used only once and thrown away, so it would be wasteful to update every single comet as soon as it boots. If you plan to use your comet for more than a quick test, you'll probably want to ensure you're running the latest version of the OS.
135Urbit comes with a recent release of the Urbit OS, but automatic updates of the `%base` desk (which contains the kernel of the OS) are not enabled by default for Comets. Many comets are used only once and thrown away, so it would be wasteful to update every single comet as soon as it boots. If you plan to use your comet for more than a quick test, you'll probably want to ensure you're running the latest version of the OS.
137−You can enable updates for your comet by typing `|install (sein:title our now our) %kids, =local %base` into Dojo and pressing Enter.
137+You can enable updates for your comet by typing `|ota (sein:title our now our)` into Dojo and pressing Enter.
140−> |install (sein:title our now our) %kids, =local %base
140+> |ota (sein:title our now our)
142kiln: activated install into %base from [~samzod %kids]
142kiln: activated install into %base from [~samzod %kids]
143kiln: downloading update for %base from [~samzod %kids]
143kiln: downloading update for %base from [~samzod %kids]