3ccd61629b
Usually r->nused < r->nalloc and the read is in bounds. But it could in theory be right on the line and reading past the end of the allocation. Make it safe but preserve as much of the old semantics as possible. This use of rterm appears to be only for optimization purposes so the result does not matter for correctness. |
||
---|---|---|
acid | ||
bin | ||
dict | ||
dist | ||
face | ||
font | ||
include | ||
lib | ||
lp | ||
mac | ||
man | ||
ndb | ||
news | ||
plumb | ||
postscript | ||
proto | ||
sky | ||
src | ||
tmac | ||
troff | ||
unix | ||
.gitignore | ||
.travis.yml | ||
CHANGES | ||
configure | ||
CONTRIBUTING.md | ||
CONTRIBUTORS | ||
INSTALL | ||
install.txt | ||
LICENSE | ||
Makefile | ||
rcmain | ||
README.md |
This is a port of many Plan 9 libraries and programs to Unix.
Installation
To install, run ./INSTALL. It builds mk and then uses mk to run the rest of the installation.
For more details, see install(1), at install.txt in this directory and at https://9fans.github.io/plan9port/man/man1/install.html.
Documentation
See https://9fans.github.io/plan9port/man/ for more documentation. (Documentation is also in this tree, but you need to run a successful install first. After that, "9 man 1 intro".)
Intro(1) contains a list of man pages that describe new features or differences from Plan 9.
Helping out
If you'd like to help out, great!
If you port this code to other architectures, please share your changes so others can benefit.
Git
You can use Git to keep your local copy up-to-date as we make changes and fix bugs. See the git(1) man page here ("9 man git") for details on using Git.
Status
Contact
-
Mailing list: https://groups.google.com/group/plan9port-dev
-
Issue tracker: https://github.com/9fans/plan9port/issues
-
Submitting changes: https://github.com/9fans/plan9port/pulls
-
Russ Cox rsc@swtch.com