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 <[EMAIL PROTECTED]> 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 >
