diff options
| author | Luke T. Shumaker <lukeshu@lukeshu.com> | 2025-02-26 15:22:00 -0700 |
|---|---|---|
| committer | Luke T. Shumaker <lukeshu@lukeshu.com> | 2025-02-26 16:10:28 -0700 |
| commit | 1d097f65ade8ae6ef40966b8409952a9eb99ec25 (patch) | |
| tree | 1cbb472e636089cfda428a987e9d4893db077ecf /README.md | |
| parent | ab15e12dd7b26831f4efe5f09d7ecc71d5c68cc7 (diff) | |
README.md: Touch up
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 6 |
1 files changed, 2 insertions, 4 deletions
@@ -69,9 +69,7 @@ There are several ways of putting this firmware file onto the harness: The harness uses DHCP to acquire an IPv4 address, then serves the 9P protocol over TCP: - - TCP port: 564 (9P does not have a standard TCP port number, but - this is the default port number used by most 9P-over-TCP clients, - including the Linux kernel's v9fs driver). + - TCP port: 564 - Supported protocol versions: - `9P2000` (base protocol): Yes - `9P2000.u` (Unix extension): Yes, with Linux kernel @@ -96,7 +94,7 @@ library for your programming language of choice. Some notes on choosing a client: - On x86-32, the Linux kernel v9fs driver is known to drop entries - from directory listings; I advise using 9pfuse instead of you want + from directory listings; I advise using 9pfuse instead if you want to mount it on 32-bit systems. - I generally like mounting it as a real filesystem, but this means that you only get errno errors, and the more-helpful error strings |