Thanks Richard, James,
Chris
> On Oct 3, 2016, at 11:05 AM, Richard Miller <9f...@hamnavoe.com> wrote:
>
> term% lookman iounit
> man 2 fcall # fcall(2)
> man 2 iounit # iounit(2)
> man 3 proc # proc(3)
> man 5 0intro # 0intro(5)
> man 5 open # open(5)
> man 5 read # read(5)
>
>
I agree with Eric*com. Rice rice baby, popo. Don't Tread on my 9p server.
On Mon, Oct 3, 2016 at 8:08 AM, James A. Robinson wrote:
> On Mon, Oct 3, 2016 at 6:54 AM Chris McGee wrote:
>
>> Lately, I’m looking at the “iounit.” Initially, I had thought of
On Mon, Oct 3, 2016 at 6:54 AM Chris McGee wrote:
> Lately, I’m looking at the “iounit.” Initially, I had thought of it as a
> way to give the size of a file on Topen. After some testing I realized that
> the network subsystem in plan9 is expecting the iounit to be large
term% lookman iounit
man 2 fcall # fcall(2)
man 2 iounit # iounit(2)
man 3 proc # proc(3)
man 5 0intro # 0intro(5)
man 5 open # open(5)
man 5 read # read(5)
Hello All,
I am learning the 9p protocol and implementing a 9P server. After reading the
9p manual page, the types of messages and much of the overview is clear. There
are a number of items that are less clear.
For example, it took some time to figure out how to provide a directory
structure
Hello All,
I am learning the 9p protocol and implementing a 9P server. After reading the
9p manual page, the types of messages and much of the overview is clear. There
are a number of items that are less clear.
For example, it took some time to figure out how to provide a directory
structure