Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Subject: RE: mkfs.jffs2 for Windows
Date: Tue, 15 Feb 2005 22:13:15 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Message-ID: <3D848382FB72E249812901444C6BDB1D022F50AE@exchange.timesys.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
content-class: urn:content-classes:message
From: "Robb, Sam" <sam DOT robb AT timesys DOT com>
To: <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j1G3FBcL015284

> > I have been searching the mailing lists and the web for a 
> version of 
> > mkfs.jffs2 that will run on Windows.  I do not believe one 
> is available
> 
>   Correct.  Cygwin relies entirely on the underlying 'doze OS 
> for file-system
> support, device drivers, and so on.  Since there is no 'doze 
> support for jffs2,
> there is no way to format and mount such a filesystem under cygwin.

For the record: mkfs.jffs2 takes as input a directory and an
option device table file, and turns that directly into a file
containing a jffs2 filesystem.  So, OS support really isn't
required.

Getting mkfs.jffs2 to build & run under Cygwin is not all that
difficult.  I've done it before, and gotten permission from my
employer to package it for Cygwin - what I lack at the moment
is time :-/  Until then, if anyone is interested in helping
push this through as a proper Cygwin package, I'd be happy to
talk to them about it.

-Samrobb

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/