From: Nicolas Bercher <nbercher@yahoo.fr>
To: 9fans@9fans.net
Subject: Re: [9fans] FAT32 question
Date: Wed, 27 Mar 2013 17:02:47 +0100 [thread overview]
Message-ID: <51531827.8040800@yahoo.fr> (raw)
In-Reply-To: <CAE9W7-hwRhUz2c6ev4v6MELi0gtY_t5gRwMu1rLYCatCWF15_w@mail.gmail.com>
On 27/03/2013 15:18, Comeau At9Fans wrote:
> On Wed, Mar 27, 2013 at 8:33 AM, erik quanstrom<quanstro@quanstro.net> wrote:
>> On Wed Mar 27 08:26:04 EDT 2013, comeauat9fans@gmail.com wrote:
>>> ... I tried mv'ing the problem files and then back
>>> but same results.
>>
>> modulo other bugs, dossrv does something kind of interesting.
>> if you explictly walk to x.c, you will have a match. but it doesn't
>> do this when stating a directory. so if the file lists as "x.c" you
>> should be able to compile it.
>>
>> ladd# cd /n/9fat
>> ladd# lc
>> 9LOAD 9PCCPU.GZ 9pccpu PLAN9.INI
>> ladd# cat plan9.ini>/dev/null
>> lladd# cat PLAN9.ini>/dev/null
>> ladd# cat PLAN9.INI>/dev/null
>
> That seems correct from what I saw. The problem is in globing though,
> *.c will yield differently than x.c/X.c/x.C/X.C. Anyway, I seem to be
> past this part of things as I just tried mv'ing on Plan 9 itself
> rather than the host system and that seems to be letting x.c be seen
> as itself, or whatever it is that's going on or not is good enough for
> me now.
Maybe a solution would be do to this in two passes. Since x.c and X.C
describe the same file, it is not possible to rename it directly:
cpu% touch X.C
cpu% mv X.C x.c
mv: X.C and ./x.c are the same
Just try something like this:
cpu% mv X.C _x.c
cpu% mv _x.c x.c
cpu% ls *.c
x.c
cpu%
It worked for me on the 9fat partition (the only difference being
my Plan9 runs on an Atom, not a RPi).
Nicolas
next prev parent reply other threads:[~2013-03-27 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 12:24 Comeau At9Fans
2013-03-27 12:33 ` erik quanstrom
2013-03-27 14:18 ` Comeau At9Fans
2013-03-27 16:02 ` Nicolas Bercher [this message]
2013-03-27 16:16 ` Comeau At9Fans
2013-03-27 12:36 ` tlaronde
2013-03-27 12:39 ` dexen deVries
2013-03-27 13:07 ` Stuart Morrow
2013-03-27 15:44 ` Bakul Shah
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=51531827.8040800@yahoo.fr \
--to=nbercher@yahoo.fr \
--cc=9fans@9fans.net \
/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).