Date: Sun, 13 Jun 2004 22:40:22 GMT From: "Val P" <secureplay@sbcglobal.net> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/67721: FreeBSD-current + Samba 3.0.4 + FAT32. File corruption Message-ID: <200406132240.i5DMeMHV081603@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/67721; it has been noted by GNATS. From: "Val P" <secureplay@sbcglobal.net> To: <freebsd-gnats-submit@FreeBSD.org>, <patrick_dkt@yahoo.com.hk> Cc: Subject: Re: ports/67721: FreeBSD-current + Samba 3.0.4 + FAT32. File corruption Date: Sun, 13 Jun 2004 17:32:10 -0500 "Fix Use UFS2(possibly UFS) as the backend of share instead of Fat32" The "Fix" in this bug report is not acceptable. Sometimes UFS is not an option. FAT32 is a cross-platform file system. UFS is not. Furthermore such a bug should not be in a -stable branch, unless the end user is warned somehow when trying to use it. Do you picture microsoft shipping out Windows XP with a file corruption bug in FAT32 and telling people (after they experience the problem and data loss, not ahead of time) that their fix is to use NTFS?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406132240.i5DMeMHV081603>