From mboxrd@z Thu Jan  1 00:00:00 1970
From: andrey mirtchovski <andrey@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme question + diffs for kfs, fs and plumbing
In-Reply-To: <20020709112856.L20312@cackle.proxima.alt.za>
Message-ID: <20020709051948.A66021-100000@fbsd.acl.lanl.gov>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Date: Tue,  9 Jul 2002 05:23:53 -0600
Topicbox-Message-UUID: c6f807a2-eaca-11e9-9e20-41e7f4b1d025

umm,

were you reading this from a unix machine? i think nemo meant that he's
replacing ' ' with a non-ascii rune in p9 (maybe your font
mistranslated it to '?' in the terminal?)...

here's what the original looked like:

I'm renaming ' ' with =E2^=D0=A3 in u9fs
There's no problem doing that since there's no =E2^=D0=A3
in outside file names.

andrey (who thinks nemo's solution looks quite ok)

On Tue, 9 Jul 2002, Lucio De Re wrote:

> On Tue, Jul 09, 2002 at 10:42:04AM +0200, Fco.J.Ballesteros wrote:
> >
> > I'm renaming ' ' with ? in u9fs
> > There's no problem doing that since there's no ?
> > in outside file names.
>
> There could be:
>
> -rw-r--r--   1 lucio  staff         0 Jul  9 11:22 t?uch
>
> produced by "touch t\?uch" on my NetBSD host.  This is from
> "man 2 intro" on NetBSD 1.5.2:
>
>      File Name
>              Names consisting of up to 255 (MAXNAMELEN) characters may be=
 used
>              to name an ordinary file, special file, or directory.
>
>              These characters may be selected from the set of all ASCII c=
har-
>              acter excluding 0 (NUL) and the ASCII code for `/' (slash). =
 (The
>              parity bit, bit 7, must be 0.)
>
>              Note that it is generally unwise to use `*', `?', `[' or `]'=
 as
>              part of file names because of the special meaning attached t=
o
>              these characters by the shell.
>
> It needn't be up to date, but it's a safe indicator.
>
> ++L
>