9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] patch/create problem (error?)
Date: Sat, 13 Sep 2008 21:45:08 -0400	[thread overview]
Message-ID: <47ec4087d7676e77986647f5fedd047d@quanstro.net> (raw)
In-Reply-To: <30849.1221354688@lunacy.ugrad.cs.cmu.edu>

On Sat Sep 13 21:13:15 EDT 2008, davide+p9@cs.cmu.edu wrote:
> > fn cp {cpmtu -m 700 $*}
>
> How about dd?
>
> Dave Eckhardt
>

dd behaves differently from cp, and patch/create
uses cp.  in particular cp tries to copy the mode
bits along.

i thought it would be easier to be correct in adding
4 lines to cp than writing a shim than makes dd work
like cp.  especially since cpmtu had already been
written.

i could be wrong, but that's what i was thinking.

by the way, my method is completely bogus and
accidentally works most of the time.  that should
be obvious from the fact that i'm using an mtu of
700 rather than 1500 or even 1510.  tcp, being a
stream protcol, doesn't respect write boundaries.
so even if the 9p messages are small enough, tcp
helpfully packs them together.

(unfortunately changing the mtu on a running interface
hung the interface.  i don't know if this behavior
persists.)

9p2000 mostly hides the stream nature of tcp,
but once in a while it rears its head.

- erik



      reply	other threads:[~2008-09-14  1:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12  7:34 Antonin Vecera
2008-09-12  7:54 ` Steve Simon
2008-09-12  8:34   ` Antonin Vecera
2008-09-12 11:47     ` erik quanstrom
2008-09-12 17:28       ` Antonin Vecera
2008-09-12 18:16         ` erik quanstrom
2008-09-13 19:14           ` Antonin Vecera
2008-09-14  1:11       ` Dave Eckhardt
2008-09-14  1:45         ` erik quanstrom [this message]

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=47ec4087d7676e77986647f5fedd047d@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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).