This make sense now...

The the check disk tool for vfat and msdos are in the sys file while in
the ram disk there are just fsck.ext2@      fsck.ext3*      fsck.reiserfs*
 fsck.xfs*

It does not find the binary for that filesystem so it skip,
if the dyne.sys is on a cuorrupted FAT and the fat checkdisk program is on
the dyne.sys that is still not mounted...
but if the fs is corrupted it should not get mounted no?
Do I miss something?
This is a issue that should be taken care, I don't see so much the point
of having fsck.xfs in the ramdisk if I cannot boot on macs and not the fat
one.


> You might try running fsck on the appropriate partitions. Most of my
> system is still in FAT32 partitions, and I get that kind of message if
> one of them gets corrupted (doesn't have to be a big corruption--any
> li'l ole thing will trigger it). Since I haven't mastered the fine art
> of running fsck, I reboot to Windows and run ScanDisk or Norton Disk
> Doctor on the offending partition. Partition works fine after that.
>
> HTH.
> _______________________________________________
> dynebolic mailing list
> dynebolic@???
> http://lists.dyne.org/mailman/listinfo/dynebolic
>