Stories
Slash Boxes
Comments

SoylentNews is people

posted by LaminatorX on Thursday November 06 2014, @01:54PM   Printer-friendly
from the native-support dept.

From the WinBeta subforum of reboot.pro:

I'm Pierre Schweitzer, one of the ReactOS developers. This is a free operating system that aims to re-implement Windows, but this time with an open source license.

ReactOS now supports reading files from NTFS volume. This was a long awaited feature people were asking for. And here it is.

You can see what I'm talking about on the three pictures [included in the fine article].

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Thursday November 06 2014, @09:25PM

    by Anonymous Coward on Thursday November 06 2014, @09:25PM (#113659)

    I'm no expert

    Hmmm.

    NTFS support on any non-Microsoft OS is partial, not full

    Linux has had stable read and write support for NTFS since early 2007. [google.com]
    What do you perceive as missing?
    ...besides, y'know, proper file permissions--which MICROS~1 has never had.

    dangerous to rely on for important data

    ...same as when using NTFS under a MICROS~1 OS--because NTFS is MICROS~1's homebrew technology.
    There are no surprises in your statement.
    ...and, if M$ would document their 4th-rate protocols fully, it would be duck soup to reimplement them.
    ...but that would break M$'s business model of obfuscation.

    .
    Regarding the AC above: [soylentnews.org]
    ReactOS [...] relies on wine

    ReactOS did do a major rewrite back in early 2010. [google.com]
    At that time, there was a serious cross-pollination between the 2 projects.

    -- gewg_

  • (Score: 2) by arashi no garou on Friday November 07 2014, @02:06PM

    by arashi no garou (2796) on Friday November 07 2014, @02:06PM (#113799)

    Linux has had stable read and write support for NTFS since early 2007.
    What do you perceive as missing?

    I've had issues with corrupted NTFS volumes after extensive read/write sessions under GNU/Linux (specifically Slackware with NTFS-3G and FUSE) for several years now. These days, I'll only write to an NTFS volume over a network share; I don't dare mount the volume natively in GNU/Linux. Maybe it's just Slackware; maybe it's just my hardware. But I've learned my lesson the hard way.

    The rest of your reply is blatantly biased against Microsoft (MICROS~1? Really? Grow up!) but I stand by what I wrote about the ReactOS team wanting to reverse-engineer NTFS instead of relying on NTFS-3G/FUSE, as I got it directly from their website. You can claim otherwise if you want, but you'd be calling them liars, not me.

  • (Score: 2) by monster on Friday November 07 2014, @05:44PM

    by monster (1260) on Friday November 07 2014, @05:44PM (#113884) Journal

    What do you perceive as missing?

    Some of the most egregious fuckups in the filesystem would land you in "Run chkdsk from Windows on this volume" (aka "I won't touch this shit even with a ten feet pole") territory.