public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jay Lepreau <lepreau@cs.utah.edu>
To: "Maurizio Martignano" <mm@sitek.it>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] File System?
Date: Sun, 30 Jan 2000 18:31:00 -0000	[thread overview]
Message-ID: <200001310231.TAA10928@mancos.cs.utah.edu> (raw)

>    is there a file system available for eCos?

The OSKit ( http://www.cs.utah.edu/flux/oskit/ ) would probably be a
good place from which to grab a filesys.  Since the main point of the
OSKit is to produce components that are easily usable in *other*
operating systems, it should be relatively easy to get one of its many
file systems to work with eCos.  You'd have to write the glue code to
map the normalized OSKit execution environment to the eCos one; there
are examples and lots of docs, and we'd help out if needed.

File systems in the OSKit's current bag of components include all the
Linux-supported filesystems (ext2, msdos, vfat, and iso9660 have been
tested), the standard BSD "ffs" filesystem, and a simple memory
filesys.  Since the OSKit wraps essentially unchanged code from the
original OS's (except for the memory fs), its file systems are more
reliable and speedy than if we'd been foolish enough to reimplement
them.

Jay Lepreau
Flux Research Group
Dept of Computer Science
University of Utah

             reply	other threads:[~2000-01-30 18:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-30 18:31 Jay Lepreau [this message]
2000-01-31  0:14 ` Jesper Skov
  -- strict thread matches above, loose matches on Subject: below --
2000-01-31  2:48 Jay Lepreau
2000-01-27  5:25 Maurizio Martignano
2000-01-27 10:57 ` Paul Beskeen
2000-01-11  9:13 Maurizio Martignano

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=200001310231.TAA10928@mancos.cs.utah.edu \
    --to=lepreau@cs.utah.edu \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=mm@sitek.it \
    /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).