From mboxrd@z Thu Jan  1 00:00:00 1970
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <13426df10611201627g1d8e0962wf512a11aca15bfc7@mail.gmail.com>
References: <1c5b7c3fd84e9c2449747b93b99abf66@coraid.com>
	<7B16F5E3-CF10-4603-9D4E-557BA4A493EF@telus.net>
	<13426df10611201627g1d8e0962wf512a11aca15bfc7@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <0F431F87-7799-4D4C-8302-D2CA6286AAC3@ar.aichi-u.ac.jp>
Content-Transfer-Encoding: 7bit
From: arisawa@ar.aichi-u.ac.jp
Date: Tue, 21 Nov 2006 10:23:22 +0900
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] Re: echo -n
Topicbox-Message-UUID: e3e9d906-ead1-11e9-9d60-3106f5b1d025

Thanks all for following to my question.

Just my impression ...
If 0 byte writing is a message other than EOF, then we should have
some mechanism that enables to distinguish between 0 byte read and
true EOF.
However introducing a new mechanism to system call is a great surgery.

Coming back to my original question:
	0 byte write using echo -n
What is intended by this operation?
Let  "ECHO" be another "echo" that does not write 0 byte to stdout.
How to distinguish these two commands?
Using the command in rc script to pipe will make the difference.
Are there any other cases that make difference?

If the difference is only in pipe, then we should consider:
is it a legitimate method to let the other end close the pipe?