9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: echo -n
Date: Mon, 20 Nov 2006 19:32:49 -0700	[thread overview]
Message-ID: <13426df10611201832m7ce46730pf61df2e78d544e14@mail.gmail.com> (raw)
In-Reply-To: <0F431F87-7799-4D4C-8302-D2CA6286AAC3@ar.aichi-u.ac.jp>

This whole discussion has been coming up for years. I can't remember
the first time I saw it but it was definitely over a quarter century
ago. I think at some point we figured the issue was roughly akin to
the difference between the empty string and the null string -- where
EOF is the null string, and 0 bytes of data is the empty string --
which you can't actually distinguish via read. I'm NOT saying this is
exactly it, but I think it provides an analogy and a  way to think
about it.

I think Plan 9 got it completely right. Being able to push a 0-byte
write through the kernel is mighty handy. I got quite annoyed with
Unix at various points over the years as I watched "optimizations"
gobble up my attempts to get a 0 byte write through the kernel.

Score one more for Plan 9 -- it lets you do what you want to do.

I hope people enjoyed this discussion more than the up-arrow thread.

thanks

ron


  reply	other threads:[~2006-11-21  2:32 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       ` [9fans] Re: echo -n arisawa
2006-11-21  2:32         ` ron minnich [this message]
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=13426df10611201832m7ce46730pf61df2e78d544e14@mail.gmail.com \
    --to=rminnich@gmail.com \
    --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).