From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: echo -n
Date: Tue, 21 Nov 2006 08:49:10 -0800 [thread overview]
Message-ID: <20061121164910.9E4075B1B@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Tue, 21 Nov 2006 08:37:19 MST." <13426df10611210737l6796930eibbd12721570520ab@mail.gmail.com>
> > : 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.
Reminds me of OSes where you couldn't have a 0 length file.
Their designers couldn't imagine why anyone would perform
such a despicable act.
> but, seriously, it's the general issue that you need to tell something
> (program, io device, network, whatever) that you don't have anything
> to say, which is not the same as saying nothing.
I am waiting for someone to write a book with the title
"zero one two...0xffffffff: Facts and Explorations of Computer Science".
next prev parent reply other threads:[~2006-11-21 16:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2006-11-24 4:06 ` Lyndon Nerenberg
-- strict thread matches above, loose matches on Subject: below --
2006-11-20 19:15 [9fans] v9fs mounting in linux erik quanstrom
2006-11-20 22:35 ` Paul Lalonde
2006-11-21 0:27 ` ron minnich
2006-11-21 1:23 ` [9fans] Re: echo -n arisawa
2006-11-21 2:32 ` 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
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=20061121164910.9E4075B1B@mail.bitblocks.com \
--to=bakul+plan9@bitblocks.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).