From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <21717812-8eaa-40ed-b993-9c91287e8445@email.android.com> References: <21717812-8eaa-40ed-b993-9c91287e8445@email.android.com> Date: Mon, 10 Aug 2015 16:35:57 +0200 Message-ID: From: Giacomo Tesio To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=14dae9cc9c7e5513b4051cf5e7ac Subject: Re: [9fans] read9pmsg usage Topicbox-Message-UUID: 65a23db0-ead9-11e9-9d60-3106f5b1d025 --14dae9cc9c7e5513b4051cf5e7ac Content-Type: text/plain; charset=UTF-8 2015-08-10 16:22 GMT+02:00 erik quanstrom : > on plan 9 systems 0 writes are not discarded. > Interesting! Is this "by design"? And what is the intended usage of 0 writes? BTW, so fcall(2) is misleading, a 0 read can not be used to identify an EOF, right? Giacomo --14dae9cc9c7e5513b4051cf5e7ac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
2015-08-10 16:22 GMT+02:00 erik quanstrom <quanstro@q= uanstro.net>:

on plan 9 systems 0= writes are not discarded.

Interesting! Is this "= by design"?
And what is the intended usage of 0 writes?

BTW, so fcall(2) is misleading, a 0 read can not be used to identif= y an EOF, right?


Giacomo
--14dae9cc9c7e5513b4051cf5e7ac--