I grep through kernel source... the FATty error messages appear *only* in fs/fat/
So this leaves 2 possibilities (and again I be guesssing):
The block device handler after calling ioctl on cdrom driver to detect fs type and getting 'no recognized filesystem' falls back to FAT.
OR
Since the error messages are a minute apart the FAT errors are coming from different device.
On 2/10/06, JM Ibanez <
[EMAIL PROTECTED]> wrote:
On 2/10/06, rexonf < [EMAIL PROTECTED]> wrote:
> Just a guess: iso9660 probably uses a file allocation table of some sort and
> the guy who wrote the cdrom driver decided to refer to it in his error
> messages as...... 'FAT'. What a surprise!
ISO9660 does *not* use a file allocation table, since (first and
foremost) ISO9660 volumes are supposed to be on read-only media. There
are, however, volume descriptors and path tables. IIRC, AFAICT.
--
JM Ibanez --
Book: If you take sexual advantage of her, you're going to burn in a
very special level of Hell, a level they reserve for child
molesters and people who talk at the theater.
(Firefly, "Our Mrs. Reynolds")
-----
http://www.livejournal.com/~jmibanez/
http://www.mycgiserver.com/~butiki/
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
