9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: arisawa@ar.aichi-u.ac.jp
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] Re: echo -n
Date: Tue, 21 Nov 2006 10:23:22 +0900	[thread overview]
Message-ID: <0F431F87-7799-4D4C-8302-D2CA6286AAC3@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <13426df10611201627g1d8e0962wf512a11aca15bfc7@mail.gmail.com>

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?



  parent reply	other threads:[~2006-11-21  1:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20 19:06 [9fans] v9fs mounting in linux Paul Lalonde
2006-11-20 19:15 ` erik quanstrom
2006-11-20 22:35   ` Paul Lalonde
2006-11-21  0:27     ` ron minnich
2006-11-21  1:16       ` Paul Lalonde
2006-11-21  2:36         ` ron minnich
2006-11-21  2:42           ` Paul Lalonde
2006-11-21  2:49             ` ron minnich
2006-11-21  3:00               ` erik quanstrom
2006-11-21  3:17                 ` [9fans] read of eof Michael Baldwin
2006-11-21  6:38                   ` Bruce Ellis
2006-11-21  1:23       ` arisawa [this message]
2006-11-21  2:32         ` [9fans] Re: echo -n ron minnich
2006-11-21 17:36           ` Andrew Lynch
2006-11-21 17:35             ` andrey mirtchovski
2006-11-21 18:13               ` Axel Belinfante
2006-11-21 18:23                 ` andrey mirtchovski
2006-11-21 18:31                   ` Axel Belinfante
2006-11-21 18:53                     ` Skip Tavakkolian
2006-11-22  1:32           ` dmr
2006-11-24  4:17             ` Lyndon Nerenberg
2006-11-24 16:24               ` Bruce Ellis
2006-11-21  9:01 Fco. J. Ballesteros
2006-11-21 15:23 ` Dave Lukes
2006-11-21 15:37 ` ron minnich
2006-11-21 15:54   ` erik quanstrom
2006-11-21 16:35   ` Brantley Coile
2006-11-21 16:49   ` Bakul Shah
2006-11-24  4:06 ` Lyndon Nerenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0F431F87-7799-4D4C-8302-D2CA6286AAC3@ar.aichi-u.ac.jp \
    --to=arisawa@ar.aichi-u.ac.jp \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).