From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] frogs and osx
Date: Fri, 4 Jan 2008 10:17:48 +0000 [thread overview]
Message-ID: <10feb52595053fbf209fb152851e9191@quintile.net> (raw)
In-Reply-To: <775b8d190801040152n1a239619x7dcdf31796fd181e@mail.gmail.com>
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
next prev parent reply other threads:[~2008-01-04 10:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 19:46 Steve Simon
2008-01-04 2:29 ` Russ Cox
2008-01-04 6:35 ` Bruce Ellis
2008-01-04 7:24 ` Lyndon Nerenberg
2008-01-04 7:31 ` Bruce Ellis
2008-01-04 7:37 ` Lyndon Nerenberg
2008-01-04 7:45 ` Bruce Ellis
2008-01-04 7:45 ` Lyndon Nerenberg
2008-01-04 9:52 ` Bruce Ellis
2008-01-04 10:17 ` Steve Simon [this message]
2008-01-04 10:26 ` Bruce Ellis
2008-01-04 11:22 ` Pietro Gagliardi
2008-02-06 13:51 ` underspecified
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=10feb52595053fbf209fb152851e9191@quintile.net \
--to=steve@quintile.net \
--cc=9fans@cse.psu.edu \
/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).