This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: FAT FS questions
- From: "Paul D. DeRocco" <pderocco at ix dot netcom dot com>
- To: "eCos Discuss" <ecos-discuss at ecos dot sourceware dot org>
- Date: Mon, 4 Oct 2004 01:26:27 -0700
- Subject: RE: [ECOS] FAT FS questions
> From: Andrew Lunn
>
> RAMFS has no concept of attributes at all.
>
> ROMFS is naturaly a read only filesystem and no attributes at all
>
> JFFS2 has attributes as you would expect for a *nix style FS, but the
> eCos layer above it i think totally ignores them.
>
> There is no chmod() function, so even where there are attribute
> support in the filesystem there is no way to change them.
>
> When you start look at attributes it gets complicated very
> quickly. There is no concept of a user in eCos, or groups. Deeply
> embedded systems have no needs for users. But without users who is a
> super user who is allowed to change permission of files, ignore what
> is read only? Also which write bit is important, the owner, group,
> other? So the basic model is that everything runs as root and can do
> what ever it wants. KISS.
MS-DOS had a read-only attribute, with no concept of users. Even though the
read-only attribute could be turned off, it was still useful, for preventing
modification or deletion by "normal" code which didn't go to the trouble of
turning it off.
--
Ciao, Paul D. DeRocco
Paul mailto:pderocco@ix.netcom.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss