This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE : empty filenames in JFFS2
- From: "Vincent Catros" <Vincent dot Catros at elios-informatique dot fr>
- To: 'Øyvind Harboe' <oyvind dot harboe at zylin dot com>,"'Thomas Koeller'" <thomas dot koeller at baslerweb dot com>
- Cc: <ecos-discuss at sources dot redhat dot com>
- Date: Mon, 8 Mar 2004 17:45:20 +0100
- Subject: [ECOS] RE : [ECOS] empty filenames in JFFS2
Hello,
> -----Message d'origine-----
> De?: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-
> owner@ecos.sourceware.org] De la part de Øyvind Harboe
> Envoyé?: lundi 8 mars 2004 17:35
> À?: Thomas Koeller
> Cc?: ecos-discuss@sources.redhat.com
> Objet?: Re: [ECOS] empty filenames in JFFS2
>
> man, 08.03.2004 kl. 11.57 skrev Thomas Koeller:
> > This happens because JFFS2 happily creates files with empty names if
> > asked to do so, I've noticed this before.
>
> Some questions come to mind:
>
> - Is this the intended behaviour?
> - If empty filenames are illegal, whos job is it to produce an error
> message? I.e. should the fix go into JFFS2 or eCos higher layers?
I think empty file name shouldn't be allowed because it would become
impossible to distinguish for instance "/" (root directory) and "/"
(empty filename under root directory).
As this is a general behaviour it should be fixed into "fileio" package.
Regards.
Vincent
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss