public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gthomas@redhat.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: eCos Disuss <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] ROMFS in anoncvs
Date: Fri, 13 Jul 2001 04:32:00 -0000	[thread overview]
Message-ID: <XFMail.20010713053145.gthomas@redhat.com> (raw)
In-Reply-To: <20010713091400.B637@biferten.ma.tech.ascom.ch>

On 13-Jul-2001 Andrew Lunn wrote:
> On Thu, Jul 12, 2001 at 04:05:23PM -0600, Gary Thomas wrote:
>> A little harsh;  perhaps open() calls for nested paths fail.
>> 
>> It does look like you are correct about the mode stuff.
> 
> The filesystems root directory, is not a directory, and so it fails
> imeadiatly with my test program.
> 

Odd - these definitions have been current in the tree for a year.

Perhaps my iPAQ demo works because it doesn't use pathname separators
(i.e. all the files are in the topmost directory and I just use the name)

>> The two things
>> I see to be done are:
>>   * Change 'mk_romfs' to perform some mapping from the host file system modes
>>     to those used by eCos.  
> 
> I sent a patch to Jifl last night.

We also got a patch from Richard Panton, the original contributor.

> 
>>   * Improve the test program so that it can be run automatically, thus
>>     allowing it to be tested more thoroughly by our test farm.
> 
> I've got some test code embedded in a synthetic application. I will
> try to hack it into a standalone test.

Thanks.

      parent reply	other threads:[~2001-07-13  4:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-12 11:38 Andrew Lunn
2001-07-12 15:05 ` Gary Thomas
2001-07-13  0:14   ` Andrew Lunn
2001-07-13  2:55     ` Richard Panton
2001-07-13 13:38       ` Jonathan Larmour
2001-07-13  4:32     ` Gary Thomas [this message]

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=XFMail.20010713053145.gthomas@redhat.com \
    --to=gthomas@redhat.com \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-discuss@sourceware.cygnus.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).