Re: FAT32: Invalid FSINFO signature on mount?

Max Cohan (mcohan@adnc.net)
Thu, 18 Mar 1999 16:47:40 -0800

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Alan Cox: "Re: bug(?) in block_til_ready serial.c - open() blocking, 2.0 & 2.2"
Previous message: Max Cohan: "Re: FAT32: Invalid FSINFO signature on mount?"

One thing I forgot to note...
In regards to the 0x1E0 offset, I'm not sure that it shouldn't be
0x1E4. There is a 4 byte signature, then a 480 byte space, then
the useful fsinfo information. I still wonder where the magic number came
from, I wonder if there is some way this additional offset should be
'calculated' rather than have it be a static number.

Max

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Alan Cox: "Re: bug(?) in block_til_ready serial.c - open() blocking, 2.0 & 2.2"
Previous message: Max Cohan: "Re: FAT32: Invalid FSINFO signature on mount?"