Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md #142

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update README.md #142

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -197,7 +197,7 @@ It's easy to get up and running. Simply clone the repo using ``git``.
Make sure you have **all** [dependencies](https://github.com/Coopydood/ultimate-macOS-KVM/blob/main/README.md#requirements) installed before getting started.

```sh
$ git clone https://github.com/Coopydood/ultimate-macOS-KVM
git clone https://github.com/Coopydood/ultimate-macOS-KVM
```

> [!TIP]
Expand All @@ -209,7 +209,7 @@ Okay, so you've cloned my repo, and `cd`'d into the directory. Great!
Now, before running the script - and to avoid the subsequent and inevitable gotcha - you should enable the ``libvirtd`` daemon first if it hasn't been already. Here's an example for Arch-based systems:

```sh
$ sudo systemctl enable libvirtd
sudo systemctl enable libvirtd
```
> [!WARNING]
> This command requires superuser privileges.
Expand All @@ -219,7 +219,7 @@ $ sudo systemctl enable libvirtd
and/or check the status of the daemon with

```sh
$ systemctl status libvirtd
systemctl status libvirtd
```

***
Expand All @@ -231,7 +231,7 @@ Okay, now you're ready to use **ultimate-macOS-KVM**. Use the ``main.py`` file.
This is your main menu / central hub for the project and everything can be accessed from here.

```sh
$ ./main.py
./main.py
```
> [!CAUTION]
> Most sub-scripts included in the project should *not* be run on their own. Always use ``main.py`` unless the script was user-generated or stated otherwise.
Expand Down