9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Michael Teichgräber" <mt@wmipf.in-berlin.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] implementing 9p read
Date: Fri,  6 Jul 2007 01:44:19 +0200	[thread overview]
Message-ID: <468D8253.9030400@wmipf.in-berlin.de> (raw)
In-Reply-To: <8d88287934ff066cf767d5d1e024cf94@quintile.net>

> line at a time - the library assembles the lines into the requested
> buffer's worth

Nice - this way you may easily generate quite large files using a buffer
covering just one line. This probably also means that Read returns in
most cases less bytes than requested, just as much as needed for the
current line up to \n. The server likely has to keep some information
like the next read-offset expected, and the next line number, so that it
can check whether the next read-request actually asks for the next line
 -- if it doesn't ignore seek/offsets at all, which also seems practicable.

> writing files can be flagged smilarly:
> 
> line at a time - newlines and leading and trailing whitespace
> stripped

I suppose this is adequate for control files waiting for commands. One
can leave the fd open, and send one line after the other as needed.

One thing I like about the idea using 9p even in smaller systems is,
that you can define one file to be something like a "serial terminal".
If one has a lot of such embedded devices connected to a network, one
can easily have a "command line" for each of them without the need to
connect each to a real serial port.

Michael


  reply	other threads:[~2007-07-05 23:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05 18:51 Michael Teichgräber
2007-07-05 18:59 ` Sape Mullender
2007-07-05 19:14   ` Steve Simon
2007-07-05 23:44     ` Michael Teichgräber [this message]
2007-07-06  0:01       ` erik quanstrom
2007-07-07 10:57         ` [9fans] kvm matt
2007-07-07 12:19           ` Paweł Lasek
2007-07-07 14:35             ` matt
2007-07-07 19:20               ` Paweł Lasek
2007-07-08 15:22                 ` Paweł Lasek
2007-07-06 14:43       ` [9fans] implementing 9p read Steve Simon
2007-07-06 14:54         ` ron minnich
2007-07-06 21:58           ` Steve Simon
2007-07-06 22:03             ` Charles Forsyth
2007-07-06 14:57         ` C H Forsyth
2007-07-05 19:58   ` ron minnich
2007-07-05 23:32   ` Michael Teichgräber

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=468D8253.9030400@wmipf.in-berlin.de \
    --to=mt@wmipf.in-berlin.de \
    --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).