Open AresAndy opened 4 years ago
This is how Archlinux copes with hardcoded paths: https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/plan9port#n42
And you should execute plan9port programs with the PLAN9 environment variable correctly set to the absolute path to the plan9port tree and with "$PLAN9/bin" in the PATH environment variable. As done here: https://git.archlinux.org/svntogit/community.git/tree/trunk/plan9.sh?h=packages/plan9port
This is how Archlinux copes with hardcoded paths: https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/plan9port#n42
I am on Arch, but to not further complicate things with root permissions I'm using the repo directly. Anyway, shouldn't the INSTALL
script do that already on its own?
Also, I have the two global variables set properly both on bash
and fish
, but all my attempts at using 9p <command>
yield Connection refused
. I can launch the plumber and acme just fine, I just can't query/alter the 9p system (configs, fonts, etc..)
Hello,
I'm probably going to state the obvious here, but
plan9port
really needs guides for newcomers. I mean, I'm not completely ignorant on the *nix topic, yet I'm still trying to understand why my install still points to/usr/local/plan9
even though I followed the instructions step by step.grep
ing the project real quick shows that themoveplan9
script does not work, shebang paths and all still point to/usr/local/plan9
. Google+ is down and the Groups is either unreachable or not existing, and that's why I'm writing here.. All the documentation one can find is:man
pagesI would really like to use
acme
for all my work, and I can't use it at all without plumbing per se.Thanks