From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <775b8d190801040226r50719693p3ff7461f43367bcf@mail.gmail.com>
Date: Fri,  4 Jan 2008 21:26:29 +1100
From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] frogs and osx
In-Reply-To: <10feb52595053fbf209fb152851e9191@quintile.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <775b8d190801040152n1a239619x7dcdf31796fd181e@mail.gmail.com>
	<10feb52595053fbf209fb152851e9191@quintile.net>
Topicbox-Message-UUID: 27188ad2-ead3-11e9-9d60-3106f5b1d025

Sure,

I think it's a mistake for a server to throw you frogs.  But no reason
(within reason) for the library to up-chuck on one.  But take care
where you walk.  If every protocol "violation" had to be treated as
"shit happens" then the world falls apart.

brucee

On Jan 4, 2008 9:17 PM, Steve Simon <steve@quintile.net> wrote:
> I take onboard all the commeonst made, and I am happy to
> code my own island of mutant frogs, however I wonder if there
> is a middle ground.
>
> Firstly I don't understand why the frogs are such a big problem,
> on plan9 at least a file with a \r in it appears as a
> , and this
> is a visible and easily typeable character, its true things where
> more awkward on ADM3As, but that was then.
>
> My biggest objection to the current code is a read of a directory balks
> at the \r and fails. Would it be better to hack the kernel to allow a
> read of directories containing \r and walks through them, but not
> allow read/write/stat/wstat.
>
> This would mean that such files are off limits but you can still access
> other files in the directory and those below - this feels rather
> non-othogonal maybe its a reasonable compromise.
>
> I could indeed hack u9fs but what to change the
>  to, \r perhaps, but
> that feels pretty horrid too.
>
> Is there a palatable solution?
>
> -Steve
>