No announcement yet.

NTFS-3G Safe Read/Write NTFS Driver Hits RC Stage

  • Filter
  • Time
  • Show
Clear All
new posts

  • NTFS-3G Safe Read/Write NTFS Driver Hits RC Stage

    NTFS-3G Safe Read/Write NTFS Driver is now past Beta stages and the first release candidate is now out.

    We got to a point when the most critiques the driver receives is its BETA
    status. It's fairly widely used, indeed, even in productions for months
    with satisfaction. Still almost everybody is waiting for corruptions, file
    loss, disasters, and the apocalypse. Perhaps because it's still labelled as
    BETA even if it refers to the planned new features and functionalities
    instead of its reliability?

    However it seems the bad things don't really want to come. In fact, just on
    the contrary. The major part of the development time is spent to identify
    bugs and problems in stable softwares and hardwares which were originally
    believed to be caused by ntfs-3g. This is getting seriously __boring__.
    So why is it still BETA?

    Alright, convinced! From now on let's call it Release Candinate. Hopefully
    this will open the gates for real bug reports, and if not then we'll have
    a stable release real soon now.

    WARNING! Please don't expect RC2, RC3, ... and especially not RC94831. If
    no serious fault submission or concern arrives then this driver will be
    simply renamed to stable.

    This release warns if the deficient FUSE 2.6.2 kernel module is installed
    which by accident may lack the required fuseblk support for safe and
    enriched operations. FUSE 2.6.3 fixed this and includes the corrected FUSE
    kernel module.

    A very serious bug was also found in Windows chkdsk which could result the
    removal of valid files. The chance to meet the required conditions is very
    small but it does exist. If you plan to run chkdsk then make a backup of
    your files first then just restore the deleted files.

    The default_permissions FUSE option is transparently used from now if any
    of the uid, gid, umask, fmask, or dmask mount option is used. This means
    that probably many user will complain about "permission denied" errors. If
    you want full access to everybody by default then don't use any of these
    mount options. Otherwise you must configure them correctly.

    Florent Mertens wrote a very nice NTFS configuration utility. It makes
    user's life __much__ easier by providing simple ways to enable/disable
    write capability for all their devices, being either internal or external:

    The major changes in this release are

    * new: the driver is in release candinate status
    * new: warn if the deficient FUSE 2.6.2 kernel modul is used
    * fix: a bug in chkdsk could result the removal of valid files
    * fix: Mac OS X portability improvements
    * change: full file permission checking if any of the uid, gid, umask,
    fmask, or dmask mount option is used

    Contributors were Matthias Berndt, Michael Fritscher, Janos Takacs, Kurt
    Radwanski, Miklos Szeredi, Dominique L Bouix, Florent Mertens, Bigboss,
    Ashrack, Wagonfixin, AlexandreP, Yuval Fledel, and Alexey Marushchenko.

    The "last chance" release is available from

    Happy final testing,

    Michael Larabel