From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3e1162e60607141035y6ef55f97wee0aff25c0ec65b2@mail.gmail.com> Date: Fri, 14 Jul 2006 10:35:00 -0700 From: "David Leimbach" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: Re: Re: [9fans] molesting the acme filesystem In-Reply-To: <20060714104547.B1785@orthanc.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4f99d25e2af2ef50218a5846cfff0f7f@quanstro.net> <20060714104547.B1785@orthanc.ca> Topicbox-Message-UUID: 7f083848-ead1-11e9-9d60-3106f5b1d025 On 7/14/06, Lyndon Nerenberg wrote: > On Fri, 14 Jul 2006, quanstro@quanstro.net wrote: > > > i'm not sure why acme and other plan9 filesystems typically disallow a trailing newline > > on input and don't provide one on output. > > Yup. This one is my top entry for the confusomatic contest. > /dev/acme/event seems to provide one on output and requires one for the input to be valid. However, as was seen, I couldn't provide one to "addr". The interface seems a bit inconsistent based on my current knowledge but I enjoyed running through xfid.c and seeing how that was all parsed out all the same. I think maybe the man page should be more specific about some of this stuff, I may fix it and get a patch in for it over the weekend. Looks like the site's back up. Glad to see that :-) Dave