https://bugzilla.novell.com/show_bug.cgi?id=300694#c10
--- Comment #10 from Szabolcs Szakacsits 2007-08-21 09:12:55 MST ---
Thomas: would you please explain what you mean "ntfs-3g is not compatible with
fstab semantics"? I'd really love to help but I seriously don't even understand
what this issue has to do with ntfs-3g itself.
Wouldn't you also abort if any FAT, ext3, etc partition would fail to
mount/fsck? If not then why is NTFS handled differently? (I'm just interested,
I've never met such drastic handling of non-critical mount failures.)
If a volume is badly corrupted, or doesn't have the file system signature at
all (wrong/changed device), or missing an important strip disk from a RAID, or
a network server or removable media is not available when configured for boot
time mount, etc then no driver can mount those non-existent file systems.
Wouldn't it be more productive and user-friendly to continue and
investigate/fix these issues when the OS is fully up instead of a total system
failure?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.