https://bugzilla.novell.com/show_bug.cgi?id=300694#c11
--- Comment #11 from Thomas Fehr 2007-08-21 09:46:22 MST ---
If an entry is in fstab, it needs to be reliably mountable at system startup.
Since this is not the case for ntfs-3g, I see not how we can use ntfs-3g
for entries in fstab.
Of course I also would abort if any FAT, ext3 whatever partition is not
mountable,
but so far such cases did not happen. So the problem with ntfs-3g is that it is
currently NOT handled differently to all other filesystems. The real problem is
not within YaST2, ignoring the mount failure for ntfs-3g would be easily doable
(but I doubt ignoring return codes is really the way to go) if decision makers
tell me to do so.
But what is with the normal system boot. Depending on what the user did during
his last windows session (and if ntfs is considered consistent or inconsistent
by ntfs-3g) he will either have read-write access to the filesystem or no
access at all. I do not think this is what users would expect. I understand
that there
are cases where ntfs-3g has valid reasons to refuse mounting read-write, but I
would think in these cases it should simply mount read-only instead and report
the reason for doing this on terminal and in via system log. Similar to the
case
where I do a "mount -tiso9660 /dev/cdrom /mnt" (forgetting the -r switch) and
mount tells me that it mounts readonly, instead of failing the mount command
completely.
--
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.