Section 1.5. Join the Network

[jurij-jukic]

https://book.kinode.org/login.html#starting-the-kinode
https://book.kinode.org/login.html#running-the-binary
The two of these give the code ./kinode home and ./kinode --help. And that's what I did. And I got zsh: permission denied because I was running it on the folder and not the binary. It says before the code snippets to run on the binary, but imo still not idiot proof. And there are also nested kinode folder which makes it confusing as well.
My suggestion is to have 2 separate subsections depending on where we are running the binary from. So one subsection would say ./kinode/kinode/target/debug/kinode home and the other ./Downloads/kinode home so it's painfully obvious where it needs to be run from.

---

Nick:
Yeah this is a fundamentally hard problem for giving directions. If we had a specific chain it would be better, e.g.
wget foo
unzip foo
cd foo/
./bar

but since there are multiple chains, I agree we'd have to specify different specific commands which I am hesitant to do because it gets messy. I wonder if there is some find or smth we can do to locate binary, assign to env var, then run, or something along those lines 🤔