From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <47ec4087d7676e77986647f5fedd047d@quanstro.net> From: erik quanstrom Date: Sat, 13 Sep 2008 21:45:08 -0400 To: 9fans@9fans.net In-Reply-To: <30849.1221354688@lunacy.ugrad.cs.cmu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] patch/create problem (error?) Topicbox-Message-UUID: 10e63efc-ead4-11e9-9d60-3106f5b1d025 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