Gabriel Sechan wrote:
From: "John H. Robinson, IV" <[EMAIL PROTECTED]>
Let's see what a filesystem has, in a very basic way:
It has files, and ways of referencing those files.
Let's see what a music cd has, in a very basic way:
It has a stream of data, and a way of indexing that data.
They might look the same, but a music cd has no *reliable* way of
extracting the information. A data CD, however, has checksum and
tracking information on it. These are *very* different beasts. If a
music CD had a filesystem, we would not need cdparanoia to get reliable
rips.
FAT doesn't have checksum or other such data. Is it not a filesystem?
I don't see the difference. A FS specifies where pieces of data (called
files) are found on a device (weher a physical or logical device). A
TOC on a musice cd specifies where pieces of data (called tracks) are on
a cd. Sounds like a filesystem to me.
<heh> I agree with Gabe, at least with his counter example of your
definition of filesystem. I do think that the filesystem concept admits
an extremely broad range of possibilities. To make some such system into
a Linux-mountable (and usable) filesystem requires merely (!) some
little wrapper providing handlers for the required virtual filesystem
hooks <or something like that, in more precise language>.
So Gabe, maybe you could just throw together a little bit of code?
..jim
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
